=head1 SYNOPSIS\r
\r
These are instructions for building Perl under DOS (or w??), using\r
-DJGPP v2.01 or later. Under w95 long filenames are supported.\r
+DJGPP v2.03 or later. Under w95 long filenames are supported.\r
\r
=head1 DESCRIPTION\r
\r
is used to build extensions to perl). Therefore, you should be\r
able to build and install most extensions found in the CPAN sites.\r
\r
-=head2 Prerequisites\r
+Detailed instructions on how to build and install perl extension\r
+modules, including XS-type modules, is included. See 'BUILDING AND\r
+INSTALLING MODULES'.\r
+\r
+=head2 Prerequisites for Compiling Perl on DOS\r
\r
=over 4\r
\r
\r
You need the following files to build perl (or add new modules):\r
\r
- v2/djdev202.zip\r
- v2/bnu27b.zip\r
- v2gnu/gcc2721b.zip\r
- v2gnu/bsh1147b.zip\r
- v2gnu/mak3761b.zip\r
+ v2/djdev203.zip\r
+ v2/bnu2951b.zip\r
+ v2gnu/gcc2952b.zip\r
+ v2gnu/bsh204b.zip\r
+ v2gnu/mak3791b.zip\r
v2gnu/fil316b.zip\r
- v2gnu/sed118b.zip\r
- v2gnu/txt122b.zip\r
- v2gnu/dif271b.zip\r
- v2gnu/grep21b.zip\r
+ v2gnu/sed302b.zip\r
+ v2gnu/txt20b.zip\r
+ v2gnu/dif272b.zip\r
+ v2gnu/grep24b.zip\r
v2gnu/shl112b.zip\r
v2gnu/gawk303b.zip\r
- v2misc/csdpmi4b.zip \r
+ v2misc/csdpmi4b.zip\r
\r
or possibly any newer version.\r
\r
\r
=back\r
\r
-=head2 Building\r
+=head2 Building Perl on DOS\r
\r
=over 4\r
\r
tests, don't forget to use\r
\r
set LFN=y\r
- set FNCASE=y\r
+ set FNCASE=y\r
\r
before unpacking the archive.\r
\r
\r
ln -s bash.exe sh.exe\r
\r
+[If you have the recommended version of bash for DJGPP, this is already\r
+done for you.]\r
+\r
And make the C<SHELL> environment variable point to this F<sh.exe>:\r
\r
set SHELL=c:/djgpp/bin/sh.exe (use full path name!)\r
Copy or link F<gecho.exe> to F<echo.exe> if you don't have F<echo.exe>.\r
Copy or link F<gawk.exe> to F<awk.exe> if you don't have F<awk.exe>.\r
\r
+[If you have the recommended versions of djdev, shell utilities and\r
+gawk, all these are already done for you, and you will not need to do\r
+anything.]\r
+\r
=item *\r
\r
Chdir to the djgpp subdirectory of perl toplevel and type the following\r
-command:\r
+commands:\r
\r
+ set FNCASE=y\r
configure.bat\r
\r
This will do some preprocessing then run the Configure script for you.\r
-The Configure script is interactive, but in most cases you\r
-just need to press ENTER.\r
+The Configure script is interactive, but in most cases you just need to\r
+press ENTER. The "set" command ensures that DJGPP preserves the letter\r
+case of file names when reading directories. If you already issued this\r
+set command when unpacking the archive, and you are in the same DOS\r
+session as when you unpacked the archive, you don't have to issue the\r
+set command again. This command is necessary *before* you start to \r
+(re)configure or (re)build perl in order to ensure both that perl builds \r
+correctly and that building XS-type modules can succeed. See the DJGPP \r
+info entry for "_preserve_fncase" for more information:\r
+\r
+ info libc alphabetical _preserve_fncase\r
\r
If the script says that your package is incomplete, and asks whether\r
to continue, just answer with Y (this can only happen if you don't use\r
-long filenames).\r
+long filenames or forget to issue "set FNCASE=y" first).\r
\r
When Configure asks about the extensions, I suggest IO and Fcntl,\r
and if you want database handling then SDBM_File or GDBM_File\r
\r
=back\r
\r
-=head2 Testing\r
+=head2 Testing Perl on DOS\r
\r
Type:\r
\r
conditions (e.g. some subtests fail under linux/dosemu or plain dos\r
with short filenames only).\r
\r
-=head2 Installation\r
+=head2 Installation of Perl on DOS\r
\r
Type:\r
\r
and the library goes under C<($DJDIR)/lib/perl5>. The pod documentation\r
goes under C<($DJDIR)/lib/perl5/pod>.\r
\r
+=head1 BUILDING AND INSTALLING MODULES ON DOS\r
+\r
+=head2 Building Prerequisites for Perl on DOS\r
+\r
+For building and installing non-XS modules, all you need is a working\r
+perl under DJGPP. Non-XS modules do not require re-linking the perl\r
+binary, and so are simpler to build and install.\r
+\r
+XS-type modules do require re-linking the perl binary, because part of\r
+an XS module is written in "C", and has to be linked together with the\r
+perl binary to be executed. This is required because perl under DJGPP\r
+is built with the "static link" option, due to the lack of "dynamic\r
+linking" in the DJGPP environment.\r
+\r
+Because XS modules require re-linking of the perl binary, you need both\r
+the perl binary distribution and the perl source distribution to build\r
+an XS extension module. In addition, you will have to have built your\r
+perl binary from the source distribution so that all of the components\r
+of the perl binary are available for the required link step.\r
+\r
+=head2 Unpacking CPAN Modules on DOS\r
+\r
+First, download the module package from CPAN (e.g., the "Comma Separated\r
+Value" text package, Text-CSV-0.01.tar.gz). Then expand the contents of\r
+the package into some location on your disk. Most CPAN modules are\r
+built with an internal directory structure, so it is usually safe to\r
+expand it in the root of your DJGPP installation. Some people prefer to\r
+locate source trees under /usr/src (i.e., C<($DJDIR)/usr/src>), but you may\r
+put it wherever seems most logical to you, *EXCEPT* under the same\r
+directory as your perl source code. There are special rules that apply\r
+to modules which live in the perl source tree that do not apply to most\r
+of the modules in CPAN.\r
+\r
+Unlike other DJGPP packages, which are normal "zip" files, most CPAN\r
+module packages are "gzipped tarballs". Recent versions of WinZip will\r
+safely unpack and expand them, *UNLESS* they have zero-length files. It\r
+is a known WinZip bug (as of v7.0) that it will not extract zero-length\r
+files.\r
+\r
+From the command line, you can use the djtar utility provided with DJGPP\r
+to unpack and expand these files. For example:\r
+\r
+ C:\djgpp>djtarx -v Text-CSV-0.01.tar.gz\r
+\r
+This will create the new directory C<($DJDIR)/Text-CSV-0.01>, filling\r
+it with the source for this module.\r
+\r
+=head2 Building Non-XS Modules on DOS\r
+\r
+To build a non-XS module, you can use the standard module-building\r
+instructions distributed with perl modules.\r
+\r
+ perl Makefile.PL\r
+ make\r
+ make test\r
+ make install\r
+\r
+This is sufficient because non-XS modules install only ".pm" files and\r
+(sometimes) pod and/or man documentation. No re-linking of the perl\r
+binary is needed to build, install or use non-XS modules.\r
+\r
+=head2 Building XS Modules on DOS\r
+\r
+To build an XS module, you must use the standard module-building\r
+instructions distributed with perl modules *PLUS* three extra\r
+instructions specific to the DJGPP "static link" build environment.\r
+\r
+ set FNCASE=y\r
+ perl Makefile.PL\r
+ make\r
+ make perl\r
+ make test\r
+ make -f Makefile.aperl inst_perl MAP_TARGET=perl.exe\r
+ make install\r
+\r
+The first extra instruction sets DJGPP's FNCASE environment variable so\r
+that the new perl binary which you must build for an XS-type module will\r
+build correctly. The second extra instruction re-builds the perl binary\r
+in your module directory before you run "make test", so that you are\r
+testing with the new module code you built with "make". The third extra\r
+instruction installs the perl binary from your module directory into the\r
+standard DJGPP binary directory, C<($DJDIR)/bin>, replacing your\r
+previous perl binary.\r
+\r
+Note that the MAP_TARGET value *must* have the ".exe" extension or you\r
+will not create a "perl.exe" to replace the one in C<($DJDIR)/bin>.\r
+\r
+When you are done, the XS-module install process will have added information\r
+to yout "perllocal" information telling that the perl binary has been replaced,\r
+and what module was installed. you can view this information at any time\r
+by using the command:\r
+\r
+ perl -S perldoc perllocal\r
+\r
=head1 AUTHOR\r
\r
-Laszlo Molnar, F<laszlo.molnar@eth.ericsson.se>\r
+Laszlo Molnar, F<laszlo.molnar@eth.ericsson.se> [Installing/building perl]\r
+\r
+Peter J. Farley III F<pjfarley@banet.net> [Building/installing modules]\r
\r
=head1 SEE ALSO\r
\r