Before you start, you should glance through the README filefound in the top-level directory where the Perl distributionwas extracted. Make sure you read and understand the terms underwhich this software is being distributed.

This port currently supports MakeMaker (the set of modules thatis used to build extensions to perl). Therefore, you should beable to build and install most extensions found in the CPAN sites.

Detailed instructions on how to build and install perl extensionmodules, including XS-type modules, is included. See 'BUILDING ANDINSTALLING MODULES'.

Prerequisites for Compiling Perl on DOS

DJGPP
DJGPP is a port of GNU C/C++ compiler and development tools to 32-bit,protected-mode environment on Intel 32-bit CPUs running MS-DOS and compatibleoperating systems, by DJ Delorie <[email protected]> and friends.
For more details (FAQ), check out the home of DJGPP at:
```
 http://www.delorie.com/djgpp/
 
```
If you have questions about DJGPP, try posting to the DJGPP newsgroup:comp.os.msdos.djgpp, or use the email gateway [email protected].
You can find the full DJGPP distribution on any of the mirrors listed here:
```
 http://www.delorie.com/djgpp/getting.html
 
```
You need the following files to build perl (or add new modules):
```
 v2/djdev203.zip
  v2gnu/bnu2112b.zip
  v2gnu/gcc2953b.zip
  v2gnu/bsh204b.zip
  v2gnu/mak3791b.zip
  v2gnu/fil40b.zip
  v2gnu/sed3028b.zip
  v2gnu/txt20b.zip
  v2gnu/dif272b.zip
  v2gnu/grep24b.zip
  v2gnu/shl20jb.zip
  v2gnu/gwk306b.zip
  v2misc/csdpmi5b.zip
 
```
or possibly any newer version.
Pthreads
Thread support is not tested in this version of the djgpp perl.

Shortcomings of Perl under DOS

Perl under DOS lacks some features of perl under UNIX because ofdeficiencies in the UNIX-emulation, most notably:

fork() and pipe()
some features of the UNIX filesystem regarding link count and file dates
in-place operation is a little bit broken with short filenames
sockets

Building Perl on DOS

Unpack the source package perl5.8*.tar.gz with djtarx. If you wantto use long file names under w95 and also to get Perl to pass all itstests, don't forget to use
```
 set LFN=y
  set FNCASE=y
 
```
before unpacking the archive.
Create a "symlink" or copy your bash.exe to sh.exe in your ($DJDIR)/bindirectory.
```
 ln -s bash.exe sh.exe
 
```
[If you have the recommended version of bash for DJGPP, this is alreadydone for you.]
And make the SHELL environment variable point to this sh.exe:
```
 set SHELL=c:/djgpp/bin/sh.exe (use full path name!)
 
```
You can do this in djgpp.env too. Add this line BEFORE any sectiondefinition:
```
 +SHELL=%DJDIR%/bin/sh.exe
 
```
If you have split.exe and gsplit.exe in your path, then rename split.exe to djsplit.exe, and gsplit.exe to split.exe.Copy or link gecho.exe to echo.exe if you don't have echo.exe.Copy or link gawk.exe to awk.exe if you don't have awk.exe.
[If you have the recommended versions of djdev, shell utilities andgawk, all these are already done for you, and you will not need to doanything.]
Chdir to the djgpp subdirectory of perl toplevel and type the followingcommands:
```
 set FNCASE=y
  configure.bat
 
```
This will do some preprocessing then run the Configure script for you.The Configure script is interactive, but in most cases you just need topress ENTER. The "set" command ensures that DJGPP preserves the lettercase of file names when reading directories. If you already issued thisset command when unpacking the archive, and you are in the same DOSsession as when you unpacked the archive, you don't have to issue theset command again. This command is necessary *before* you start to (re)configure or (re)build perl in order to ensure both that perl builds correctly and that building XS-type modules can succeed. See the DJGPP info entry for "_preserve_fncase" for more information:
```
 info libc alphabetical _preserve_fncase
 
```
If the script says that your package is incomplete, and asks whetherto continue, just answer with Y (this can only happen if you don't uselong filenames or forget to issue "set FNCASE=y" first).
When Configure asks about the extensions, I suggest IO and Fcntl,and if you want database handling then SDBM_File or GDBM_File(you need to install gdbm for this one). If you want to use thePOSIX extension (this is the default), make sure that the stacksize of your cc1.exe is at least 512kbyte (you can check thiswith: stubedit cc1.exe).
You can use the Configure script in non-interactive mode too.When I built my perl.exe, I used something like this:
```
 configure.bat -des
 
```
You can find more info about Configure's command line switches inthe INSTALL file.
When the script ends, and you want to change some values in thegenerated config.sh file, then run
```
 sh Configure -S
 
```
after you made your modifications.
IMPORTANT: if you use this -S switch, be sure to delete the CONFIGenvironment variable before running the script:
```
 set CONFIG=
 
```
Now you can compile Perl. Type:
```
 make
 
```

Testing Perl on DOS

Type:

 make test

If you're lucky you should see "All tests successful". But there can bea few failed subtests (less than 5 hopefully) depending on some externalconditions (e.g. some subtests fail under linux/dosemu or plain doswith short filenames only).

Installation of Perl on DOS

Type:

 make install

This will copy the newly compiled perl and libraries into your DJGPPdirectory structure. Perl.exe and the utilities go into ($DJDIR)/bin,and the library goes under ($DJDIR)/lib/perl5. The pod documentationgoes under ($DJDIR)/lib/perl5/pod.

BUILDING AND INSTALLING MODULES ON DOS

Building Prerequisites for Perl on DOS

For building and installing non-XS modules, all you need is a workingperl under DJGPP. Non-XS modules do not require re-linking the perlbinary, and so are simpler to build and install.

XS-type modules do require re-linking the perl binary, because part ofan XS module is written in "C", and has to be linked together with theperl binary to be executed. This is required because perl under DJGPPis built with the "static link" option, due to the lack of "dynamiclinking" in the DJGPP environment.

Because XS modules require re-linking of the perl binary, you need boththe perl binary distribution and the perl source distribution to buildan XS extension module. In addition, you will have to have built yourperl binary from the source distribution so that all of the componentsof the perl binary are available for the required link step.

Unpacking CPAN Modules on DOS

First, download the module package from CPAN (e.g., the "Comma SeparatedValue" text package, Text-CSV-0.01.tar.gz). Then expand the contents ofthe package into some location on your disk. Most CPAN modules arebuilt with an internal directory structure, so it is usually safe toexpand it in the root of your DJGPP installation. Some people prefer tolocate source trees under /usr/src (i.e., ($DJDIR)/usr/src), but you mayput it wherever seems most logical to you, *EXCEPT* under the samedirectory as your perl source code. There are special rules that applyto modules which live in the perl source tree that do not apply to mostof the modules in CPAN.

Unlike other DJGPP packages, which are normal "zip" files, most CPANmodule packages are "gzipped tarballs". Recent versions of WinZip willsafely unpack and expand them, *UNLESS* they have zero-length files. Itis a known WinZip bug (as of v7.0) that it will not extract zero-lengthfiles.

From the command line, you can use the djtar utility provided with DJGPPto unpack and expand these files. For example:

 C:\djgpp>djtarx -v Text-CSV-0.01.tar.gz

This will create the new directory ($DJDIR)/Text-CSV-0.01, fillingit with the source for this module.

Building Non-XS Modules on DOS

To build a non-XS module, you can use the standard module-buildinginstructions distributed with perl modules.

 perl Makefile.PL
  make
  make test
  make install

This is sufficient because non-XS modules install only ".pm" files and(sometimes) pod and/or man documentation. No re-linking of the perlbinary is needed to build, install or use non-XS modules.

Building XS Modules on DOS

To build an XS module, you must use the standard module-buildinginstructions distributed with perl modules *PLUS* three extrainstructions specific to the DJGPP "static link" build environment.

 set FNCASE=y
  perl Makefile.PL
  make
  make perl
  make test
  make -f Makefile.aperl inst_perl MAP_TARGET=perl.exe
  make install

The first extra instruction sets DJGPP's FNCASE environment variable sothat the new perl binary which you must build for an XS-type module willbuild correctly. The second extra instruction re-builds the perl binaryin your module directory before you run "make test", so that you aretesting with the new module code you built with "make". The third extrainstruction installs the perl binary from your module directory into thestandard DJGPP binary directory, ($DJDIR)/bin, replacing yourprevious perl binary.

Note that the MAP_TARGET value *must* have the ".exe" extension or youwill not create a "perl.exe" to replace the one in ($DJDIR)/bin.

When you are done, the XS-module install process will have added informationto your "perllocal" information telling that the perl binary has been replaced,and what module was installed. You can view this information at any timeby using the command:

 perl -S perldoc perllocal

AUTHOR

Laszlo Molnar, [email protected] [Installing/building perl]

Peter J. Farley III [email protected] [Building/installing modules]

Perl under DOS, W31, W95.

Daftar Isi

NAME

SYNOPSIS

DESCRIPTION