Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Podify the remaining README.platform files;

merge README.plan9 and plan9/perlplan9.pod;
delete plan9/perlplan9.* (the perlplan.doc needs to
be regenerated in Plan 9); make the =head1 and =head2
in the README.platform to be a little more verbose
(skipped README.os2 not to anger Ilya) so that they
look better in the toc; regen toc.

p4raw-id: //depot/perl@10461
  • Loading branch information...
commit a83b6f466440987720492416f8091f2530a9ab41 1 parent 899e16d
@jhi jhi authored
View
2  MANIFEST
@@ -1298,8 +1298,6 @@ plan9/fndvers Plan9 port: update Perl version in config.plan9
plan9/genconfig.pl Plan9 port: generate config.sh
plan9/mkfile Plan9 port: Mk driver for build
plan9/myconfig.plan9 Plan9 port: script to print config summary
-plan9/perlplan9.doc Plan9 port: Plan9-specific formatted documentation
-plan9/perlplan9.pod Plan9 port: Plan9-specific pod documentation
plan9/plan9.c Plan9 port: Plan9-specific C routines
plan9/plan9ish.h Plan9 port: Plan9-specific C header file
plan9/setup.rc Plan9 port: script for easy build+install
View
24 README.amiga
@@ -51,7 +51,7 @@ Contents
=head1 DESCRIPTION
-=head2 Prerequisites
+=head2 Prerequisites for Compiling Perl on AmigaOS
=over 6
@@ -131,7 +131,7 @@ For installation of the Unix emulation, read the appropriate docs.
=head1 Accessing documentation
-=head2 Manpages
+=head2 Manpages for Perl on AmigaOS
If you have C<man> installed on your system, and you installed perl
manpages, use something like this:
@@ -153,7 +153,7 @@ for packages, and as usual, sometimes you need to give the section - C<3>
above - to avoid shadowing by the I<less(1) manpage>.
-=head2 B<HTML>
+=head2 Perl HTML Documentation on AmigaOS
If you have some WWW browser available, you can build B<HTML> docs.
Cd to directory with F<.pod> files, and do like this
@@ -166,26 +166,26 @@ directory, and go ahead with reading docs.
Alternatively you may be able to get these docs prebuilt from C<CPAN>.
-=head2 B<GNU> C<info> files
+=head2 Perl GNU Info Files on AmigaOS
Users of C<Emacs> would appreciate it very much, especially with
C<CPerl> mode loaded. You need to get latest C<pod2info> from C<CPAN>,
or, alternately, prebuilt info pages.
-=head2 C<LaTeX> docs
+=head2 Perl LaTeX Documentation on AmigaOS
-can be constructed using C<pod2latex>.
+Can be constructed using C<pod2latex>.
-=head1 BUILD
+=head1 BUILDING PERL ON AMIGAOS
Here we discuss how to build Perl under AmigaOS.
-=head2 Build Prerequisites
+=head2 Build Prerequisites for Perl on AmigaOS
You need to have the latest B<ixemul> (Unix emulation for Amiga)
from Aminet.
-=head2 Getting the perl source
+=head2 Getting the Perl Source for AmigaOS
You can either get the latest perl-for-amiga source from Ninemoons
and extract it with:
@@ -204,7 +204,7 @@ You will see a message about errors while extracting F<Configure>. This
is normal and expected. (There is a conflict with a similarly-named file
F<configure>, but it causes no harm.)
-=head2 Making
+=head2 Making Perl on AmigaOS
Remember to use a hefty wad of stack (I use 2000000)
@@ -218,7 +218,7 @@ Now!
make
-=head2 Testing
+=head2 Testing Perl on AmigaOS
Now run
@@ -229,7 +229,7 @@ Some tests will be skipped because they need the fork() function:
F<io/pipe.t>, F<op/fork.t>, F<lib/filehand.t>, F<lib/open2.t>, F<lib/open3.t>,
F<lib/io_pipe.t>, F<lib/io_sock.t>
-=head2 Installing the built perl
+=head2 Installing the built Perl on AmigaOS
Run
View
12 README.apollo
@@ -1,3 +1,13 @@
+If you read this file _as_is_, just ignore the funny characters you see.
+It is written in the POD format (see pod/perlpod.pod) which is specially
+designed to be readable as is.
+
+=head1 NAME
+
+README.apollo - Perl version 5 on Apollo DomainOS
+
+=head1 DESCRIPTION
+
The following tests are known to fail as of Perl 5.005_03:
comp/decl..........FAILED at test 0
@@ -8,4 +18,6 @@ lib/findbin........stat(/ressel/ABT/USER/vta/jk/proj.local/perl/perl5.005_03-MAI
stat(/ressel/ABT/USER/vta/jk/proj.local/perl/perl5.005_03-MAINT_TRIAL_5/t/lib/): No such file or directory at ../lib/FindBin.pm line 163
FAILED at test 1
+=head1 AUTHOR
+
Johann Klasek <jk@auto.tuwien.ac.at>
View
56 README.beos
@@ -1,39 +1,55 @@
-Notes on building perl under BeOS:
+If you read this file _as_is_, just ignore the funny characters you see.
+It is written in the POD format (see pod/perlpod.pod) which is specially
+designed to be readable as is.
-GENERAL ISSUES
---------------
-how to compile perl:
+=head1 NAME
+
+README.beos - Perl version 5 on BeOS
+
+=head1 DESCRIPTION
+
+Notes for building Perl under BeOS.
+
+=head2 General Issues with Perl on BeOS
To compile perl under BeOS R4 x86:
-`./Configure -d` and hit ^C when it asks you if you want to make changes
-to config.sh;
+ ./Configure -d
+and hit ^C when it asks you if you want to make changes to config.sh;
edit config.sh and do the following:
change d_socket='define' to ='undef';
remove SDBM, Errno, and Socket from dynamic_ext= and nonxs_ext=;
-
add '#define bool short' to x2p/a2p.h;
-../Configure -S; make; make install
+ ../Configure -S; make; make install
+
+ cd ~/config/lib; ln -s 5.00502/BeOS-BePC/CORE/libperl.so .
-cd ~/config/lib; ln -s 5.00502/BeOS-BePC/CORE/libperl.so .
(substitute 5.00502 with the appropriate filename)
-OS RELEASE-SPECIFIC NOTES
--------------------------
-R4 x86 - dynamic loading finally works! Yay! This means you can compile
-your own modules into perl. However, Sockets and Errno still don't work.
+=head2 BeOS Release-specific Notes
+
+=over 4
+
+=item R4 x86
+
+Dynamic loading finally works! Yay! This means you can compile your
+own modules into perl. However, Sockets and Errno still don't work.
(Hopefully, sockets will at least work by R5, if not sooner.)
-R4 PPC - I have not tested this. I rather severely doubt that dynamic
-loading will work. (My BeBox is in pieces right now, following a nasty
-disk crash.) You may have to disable dynamic loading to get the thing
-to compile at all. (use `./Configure` without -d, and say 'no' to
-'Build a shared libperl.so'.)
+=item R4 PPC
+
+I have not tested this. I rather severely doubt that dynamic loading
+will work. (My BeBox is in pieces right now, following a nasty disk
+crash.) You may have to disable dynamic loading to get the thing to
+compile at all. (use `./Configure` without -d, and say 'no' to 'Build
+a shared libperl.so'.)
+
+=back
+
+=head2 Contact Information
-CONTACT INFORMATION
--------------------
If you have comments, problem reports, or even patches or bugfixes (gasp!)
please email me.
View
16 README.bs2000
@@ -20,12 +20,12 @@ and testing it with 3.1A and are currently using Version V4.0A.
You may need the following GNU programs in order to install perl:
-=head2 gzip
+=head2 gzip on BS2000
We used version 1.2.4, which could be installed out of the box with
one failure during 'make check'.
-=head2 bison
+=head2 bison on BS2000
The yacc coming with BS2000 POSIX didn't work for us. So we had to
use bison. We had to make a few changes to perl in order to use the
@@ -33,7 +33,7 @@ pure (reentrant) parser of bison. We used version 1.25, but we had to
add a few changes due to EBCDIC. See below for more details
concerning yacc.
-=head2 Unpacking
+=head2 Unpacking Perl Distribution on BS2000
To extract an ASCII tar archive on BS2000 POSIX you need an ASCII
filesystem (we used the mountpoint /usr/local/ascii for this). Now
@@ -55,7 +55,7 @@ cd /usr/local/src
IO_CONVERSION=YES
cp -r /usr/local/ascii/perl5.005_02 ./
-=head2 Compiling
+=head2 Compiling Perl on BS2000
There is a "hints" file for BS2000 called hints.posix-bc (because
posix-bc is the OS name given by `uname`) that specifies the correct
@@ -102,7 +102,7 @@ ln -s /usr/bin/yacc /usr/local/bin/byacc
We build perl using GNU make. We tried the native make once and it
worked too.
-=head2 Testing
+=head2 Testing Perl on BS2000
We still got a few errors during C<make test>. Some of them are the
result of using bison. Bison prints I<parser error> instead of I<syntax
@@ -120,13 +120,13 @@ lib/complex.........FAILED tests 267, 487
lib/dumper..........FAILED tests 43, 45
Failed 11/231 test scripts, 95.24% okay. 57/10595 subtests failed, 99.46% okay.
-=head2 Install
+=head2 Installing Perl on BS2000
We have no nroff on BS2000 POSIX (yet), so we ignored any errors while
installing the documentation.
-=head2 Using Perl in the Posix-Shell
+=head2 Using Perl in the Posix-Shell of BS2000
BS2000 POSIX doesn't support the shebang notation
(C<#!/usr/local/bin/perl>), so you have to use the following lines
@@ -158,7 +158,7 @@ checkfiles.pl %*.c>). Read your C/C++ manual for additional
possibilities of the commandline prompt (look for
PARAMETER-PROMPTING).
-=head2 Floating point anomalies
+=head2 Floating point anomalies on BS2000
There appears to be a bug in the floating point implementation on BS2000 POSIX
systems such that calling int() on the product of a number and a small
View
38 README.cygwin
@@ -18,7 +18,7 @@ customize the configuration, consider using one of these packages:
http://cygutils.netpedia.net/
-=head1 PREREQUISITES
+=head1 PREREQUISITES FOR COMPILING PERL ON CYGWIN
=head2 Cygwin = GNU+Cygnus+Windows (Don't leave UNIX without it)
@@ -84,7 +84,7 @@ a UNIX system.
=back
-=head1 CONFIGURE
+=head1 CONFIGURE PERL ON CYGWIN
The default options gathered by Configure with the assistance of
F<hints/cygwin.sh> will build a Perl that supports dynamic loading
@@ -97,7 +97,7 @@ This will run Configure and keep a record:
If you are willing to accept all the defaults run Configure with B<-de>.
However, several useful customizations are available.
-=head2 Strip Binaries
+=head2 Stripping Perl Binaries on Cygwin
It is possible to strip the EXEs and DLLs created by the build process.
The resulting binaries will be significantly smaller. If you want the
@@ -112,7 +112,7 @@ prompts you,
or you can edit F<hints/cygwin.sh> and uncomment the relevant variables
near the end of the file.
-=head2 Optional Libraries
+=head2 Optional Libraries for Perl on Cygwin
Several Perl functions and modules depend on the existence of
some optional libraries. Configure will find them if they are
@@ -168,7 +168,7 @@ CPAN modules).
=back
-=head2 Configure-time Options
+=head2 Configure-time Options for Perl on Cygwin
The F<INSTALL> document describes several Configure-time options. Some of
these will work with Cygwin, others are not yet possible. Also, some of
@@ -219,7 +219,7 @@ for internal size and position calculations.
=back
-=head2 Suspicious Warnings
+=head2 Suspicious Warnings on Cygwin
You may see some messages during Configure that seem suspicious.
@@ -265,13 +265,13 @@ This failure does not seem to cause any problems.
=back
-=head1 MAKE
+=head1 MAKE ON CYGWIN
Simply run I<make> and wait:
make 2>&1 | tee log.make
-=head2 Warnings
+=head2 Warnings on Cygwin
Warnings like these are normal:
@@ -281,7 +281,7 @@ Warnings like these are normal:
dllwrap: no export definition file provided
dllwrap: creating one, but that may not be what you want
-=head2 ld2
+=head2 ld2 on Cygwin
During `C<make>', I<ld2> will be created and installed in your $installbin
directory (where you said to put public executables). It does not
@@ -293,7 +293,7 @@ is not the case `C<make>' will fail at some point. If this happens,
just manually copy I<ld2> from the source directory to somewhere in
your C<PATH>.
-=head1 TEST
+=head1 TEST ON CYGWIN
There are two steps to running the test suite:
@@ -310,7 +310,7 @@ attempted and explainable test failures are documented. It is possible
for Perl to pass all the tests, but it is more likely that some tests
will fail for one of the reasons listed below.
-=head2 File Permissions
+=head2 File Permissions on Cygwin
UNIX file permissions are based on sets of mode bits for
{read,write,execute} for each {user,group,other}. By default Cygwin
@@ -336,7 +336,7 @@ these options, these tests will fail:
lib/sdbm.t 2
op/stat.t 9, 20 (.tmp not an executable extension)
-=head2 Hard Links
+=head2 Hard Links on Cygwin
FAT partitions do not support hard links (whereas NTFS does), in which
case Cygwin implements link() by copying the file. On remote (network)
@@ -349,7 +349,7 @@ these tests will fail:
io/fs.t 4
op/stat.t 3
-=head2 Filetime Granularity
+=head2 Filetime Granularity on Cygwin
On FAT partitions the filetime granularity is 2 seconds. The following
test will fail:
@@ -358,7 +358,7 @@ test will fail:
------------------------------------
io/fs.t 18
-=head2 Tainting Checks
+=head2 Tainting Checks on Cygwin
When Perl is running in taint mode, C<$ENV{PATH}> is considered tainted
and not used, so DLLs not in the default system directories will not
@@ -390,7 +390,7 @@ tests run:
or one of the Windows system directories (although, this is B<not>
recommended).
-=head2 /etc/group
+=head2 /etc/group on Cygwin
Cygwin does not require F</etc/group>, in which case the F<op/grent.t>
test will be skipped. The check performed by F<op/grent.t> expects to
@@ -400,7 +400,7 @@ see entries that use the members field, otherwise this test will fail:
------------------------------------
op/grent.t 1
-=head2 Script Portability
+=head2 Script Portability on Cygwin
Cygwin does an outstanding job of providing UNIX-like semantics on top of
Win32 systems. However, in addition to the items noted above, there are
@@ -466,7 +466,7 @@ access by native Win32 programs).
=back
-=head1 INSTALL
+=head1 INSTALL PERL ON CYGWIN
This will install Perl, including I<man> pages.
@@ -481,7 +481,7 @@ are not, you must have write access to the directories in question.
Information on installing the Perl documentation in HTML format can be
found in the F<INSTALL> document.
-=head1 MANIFEST
+=head1 MANIFEST ON CYGWIN
These are the files in the Perl release that contain references to Cygwin.
These very brief notes attempt to explain the reason for all conditional
@@ -559,7 +559,7 @@ be kept as clean as possible.
=back
-=head1 BUGS
+=head1 BUGS ON CYGWIN
When I<make> starts, it warns about overriding commands for F<perlmain.o>.
View
10 README.dgux
@@ -39,14 +39,14 @@ Contents
Perl 5.7/8.x for DG/UX ix86 R4.20MU0x
-=head1 BUILD
+=head1 BUILDING PERL ON DG/UX
-=head2 Non-threaded Case
+=head2 Non-threaded Perl on DG/UX
Just run ./Configure script from the top directory.
Then give "make" to compile.
-=head2 Threaded Case
+=head2 Threaded Perl on DG/UX
If you are using as compiler GCC-2.95.x rev(DG/UX)
an easy solution for configuring perl in your DG/UX
@@ -77,7 +77,7 @@ that comes with the DG/UX OS does NOT know the -pthread
switch. So your build will fail if you choose the defaults.
After configuration is done correctly give "make" to compile.
-=head2 Testing
+=head2 Testing Perl on DG/UX
Issuing a "make test" will run all the tests.
If the test lib/ftmp-security gives you as a result
@@ -95,7 +95,7 @@ chmod +t /tmp (=set the sticky bit to /tmp).
Then rerun the tests. This time all must be OK.
-=head2 Installing the built perl
+=head2 Installing the built perl on DG/UX
Run the command "make install"
View
665 README.dos
@@ -1,333 +1,332 @@
-If you read this file _as_is_, just ignore the funny characters you
-see. It is written in the POD format (see perlpod manpage) which is
-specially designed to be readable as is.
-
-=head1 NAME
-
-perldos - Perl under DOS, W31, W95.
-
-=head1 SYNOPSIS
-
-These are instructions for building Perl under DOS (or w??), using
-DJGPP v2.03 or later. Under w95 long filenames are supported.
-
-=head1 DESCRIPTION
-
-Before you start, you should glance through the README file
-found in the top-level directory where the Perl distribution
-was extracted. Make sure you read and understand the terms under
-which this software is being distributed.
-
-This port currently supports MakeMaker (the set of modules that
-is used to build extensions to perl). Therefore, you should be
-able to build and install most extensions found in the CPAN sites.
-
-Detailed instructions on how to build and install perl extension
-modules, including XS-type modules, is included. See 'BUILDING AND
-INSTALLING MODULES'.
-
-=head2 Prerequisites
-
-=over 4
-
-=item 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 compatible
-operating systems, by DJ Delorie <dj@delorie.com> 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 djgpp@delorie.com.
-
-You can find the full DJGPP distribution on any SimTel.Net mirror all over
-the world. Like:
-
- ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2*
-
-You need the following files to build perl (or add new modules):
-
- v2/djdev203.zip
- v2/bnu2951b.zip
- v2gnu/gcc2952b.zip
- v2gnu/bsh204b.zip
- v2gnu/mak3791b.zip
- v2gnu/fil316b.zip
- v2gnu/sed302b.zip
- v2gnu/txt20b.zip
- v2gnu/dif272b.zip
- v2gnu/grep24b.zip
- v2gnu/shl112b.zip
- v2gnu/gawk303b.zip
- v2misc/csdpmi4b.zip
-
-or possibly any newer version.
-
-=item Pthreads
-
-Thread support is not tested in this version of the djgpp perl.
-
-=back
-
-=head2 Shortcomings of Perl under DOS
-
-Perl under DOS lacks some features of perl under UNIX because of
-deficiencies in the UNIX-emulation, most notably:
-
-=over 4
-
-=item *
-
-fork() and pipe()
-
-=item *
-
-some features of the UNIX filesystem regarding link count and file dates
-
-=item *
-
-in-place operation is a little bit broken with short filenames
-
-=item *
-
-sockets
-
-=back
-
-=head2 Building
-
-=over 4
-
-=item *
-
-Unpack the source package F<perl5.6*.tar.gz> with djtarx. If you want
-to use long file names under w95 and also to get Perl to pass all its
-tests, don't forget to use
-
- set LFN=y
- set FNCASE=y
-
-before unpacking the archive.
-
-=item *
-
-Create a "symlink" or copy your bash.exe to sh.exe in your C<($DJDIR)/bin>
-directory.
-
- ln -s bash.exe sh.exe
-
-[If you have the recommended version of bash for DJGPP, this is already
-done for you.]
-
-And make the C<SHELL> environment variable point to this F<sh.exe>:
-
- set SHELL=c:/djgpp/bin/sh.exe (use full path name!)
-
-You can do this in F<djgpp.env> too. Add this line BEFORE any section
-definition:
-
- +SHELL=%DJDIR%/bin/sh.exe
-
-=item *
-
-If you have F<split.exe> and F<gsplit.exe> in your path, then rename
-F<split.exe> to F<djsplit.exe>, and F<gsplit.exe> to F<split.exe>.
-Copy or link F<gecho.exe> to F<echo.exe> if you don't have F<echo.exe>.
-Copy or link F<gawk.exe> to F<awk.exe> if you don't have F<awk.exe>.
-
-[If you have the recommended versions of djdev, shell utilities and
-gawk, all these are already done for you, and you will not need to do
-anything.]
-
-=item *
-
-Chdir to the djgpp subdirectory of perl toplevel and type the following
-commands:
-
- 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 to
-press ENTER. The "set" command ensures that DJGPP preserves the letter
-case of file names when reading directories. If you already issued this
-set command when unpacking the archive, and you are in the same DOS
-session as when you unpacked the archive, you don't have to issue the
-set 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 whether
-to continue, just answer with Y (this can only happen if you don't use
-long 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 the
-POSIX extension (this is the default), make sure that the stack
-size of your F<cc1.exe> is at least 512kbyte (you can check this
-with: C<stubedit cc1.exe>).
-
-You can use the Configure script in non-interactive mode too.
-When I built my F<perl.exe>, I used something like this:
-
- configure.bat -des
-
-You can find more info about Configure's command line switches in
-the F<INSTALL> file.
-
-When the script ends, and you want to change some values in the
-generated F<config.sh> file, then run
-
- sh Configure -S
-
-after you made your modifications.
-
-IMPORTANT: if you use this C<-S> switch, be sure to delete the CONFIG
-environment variable before running the script:
-
- set CONFIG=
-
-=item *
-
-Now you can compile Perl. Type:
-
- make
-
-=back
-
-=head2 Testing
-
-Type:
-
- make test
-
-If you're lucky you should see "All tests successful". But there can be
-a few failed subtests (less than 5 hopefully) depending on some external
-conditions (e.g. some subtests fail under linux/dosemu or plain dos
-with short filenames only).
-
-=head2 Installation
-
-Type:
-
- make install
-
-This will copy the newly compiled perl and libraries into your DJGPP
-directory structure. Perl.exe and the utilities go into C<($DJDIR)/bin>,
-and the library goes under C<($DJDIR)/lib/perl5>. The pod documentation
-goes under C<($DJDIR)/lib/perl5/pod>.
-
-=head1 BUILDING AND INSTALLING MODULES
-
-
-=head2 Building Prerequisites
-
-For building and installing non-XS modules, all you need is a working
-perl under DJGPP. Non-XS modules do not require re-linking the perl
-binary, and so are simpler to build and install.
-
-XS-type modules do require re-linking the perl binary, because part of
-an XS module is written in "C", and has to be linked together with the
-perl binary to be executed. This is required because perl under DJGPP
-is built with the "static link" option, due to the lack of "dynamic
-linking" in the DJGPP environment.
-
-Because XS modules require re-linking of the perl binary, you need both
-the perl binary distribution and the perl source distribution to build
-an XS extension module. In addition, you will have to have built your
-perl binary from the source distribution so that all of the components
-of the perl binary are available for the required link step.
-
-=head2 Unpacking CPAN Modules
-
-First, download the module package from CPAN (e.g., the "Comma Separated
-Value" text package, Text-CSV-0.01.tar.gz). Then expand the contents of
-the package into some location on your disk. Most CPAN modules are
-built with an internal directory structure, so it is usually safe to
-expand it in the root of your DJGPP installation. Some people prefer to
-locate source trees under /usr/src (i.e., C<($DJDIR)/usr/src>), but you may
-put it wherever seems most logical to you, *EXCEPT* under the same
-directory as your perl source code. There are special rules that apply
-to modules which live in the perl source tree that do not apply to most
-of the modules in CPAN.
-
-Unlike other DJGPP packages, which are normal "zip" files, most CPAN
-module packages are "gzipped tarballs". Recent versions of WinZip will
-safely unpack and expand them, *UNLESS* they have zero-length files. It
-is a known WinZip bug (as of v7.0) that it will not extract zero-length
-files.
-
-From the command line, you can use the djtar utility provided with DJGPP
-to unpack and expand these files. For example:
-
- C:\djgpp>djtarx -v Text-CSV-0.01.tar.gz
-
-This will create the new directory C<($DJDIR)/Text-CSV-0.01>, filling
-it with the source for this module.
-
-=head2 Building Non-XS Modules
-
-To build a non-XS module, you can use the standard module-building
-instructions 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 perl
-binary is needed to build, install or use non-XS modules.
-
-=head2 Building XS Modules
-
-To build an XS module, you must use the standard module-building
-instructions distributed with perl modules *PLUS* three extra
-instructions 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 so
-that the new perl binary which you must build for an XS-type module will
-build correctly. The second extra instruction re-builds the perl binary
-in your module directory before you run "make test", so that you are
-testing with the new module code you built with "make". The third extra
-instruction installs the perl binary from your module directory into the
-standard DJGPP binary directory, C<($DJDIR)/bin>, replacing your
-previous perl binary.
-
-Note that the MAP_TARGET value *must* have the ".exe" extension or you
-will not create a "perl.exe" to replace the one in C<($DJDIR)/bin>.
-
-When you are done, the XS-module install process will have added information
-to yout "perllocal" information telling that the perl binary has been replaced,
-and what module was installed. you can view this information at any time
-by using the command:
-
- perl -S perldoc perllocal
-
-=head1 AUTHOR
-
-Laszlo Molnar, F<laszlo.molnar@eth.ericsson.se> [Installing/building perl]
-
-Peter J. Farley III F<pjfarley@banet.net> [Building/installing modules]
-
-=head1 SEE ALSO
-
-perl(1).
-
-=cut
-
+If you read this file _as_is_, just ignore the funny characters you
+see. It is written in the POD format (see perlpod manpage) which is
+specially designed to be readable as is.
+
+=head1 NAME
+
+perldos - Perl under DOS, W31, W95.
+
+=head1 SYNOPSIS
+
+These are instructions for building Perl under DOS (or w??), using
+DJGPP v2.03 or later. Under w95 long filenames are supported.
+
+=head1 DESCRIPTION
+
+Before you start, you should glance through the README file
+found in the top-level directory where the Perl distribution
+was extracted. Make sure you read and understand the terms under
+which this software is being distributed.
+
+This port currently supports MakeMaker (the set of modules that
+is used to build extensions to perl). Therefore, you should be
+able to build and install most extensions found in the CPAN sites.
+
+Detailed instructions on how to build and install perl extension
+modules, including XS-type modules, is included. See 'BUILDING AND
+INSTALLING MODULES'.
+
+=head2 Prerequisites for Compiling Perl on DOS
+
+=over 4
+
+=item 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 compatible
+operating systems, by DJ Delorie <dj@delorie.com> 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 djgpp@delorie.com.
+
+You can find the full DJGPP distribution on any SimTel.Net mirror all over
+the world. Like:
+
+ ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2*
+
+You need the following files to build perl (or add new modules):
+
+ v2/djdev203.zip
+ v2/bnu2951b.zip
+ v2gnu/gcc2952b.zip
+ v2gnu/bsh204b.zip
+ v2gnu/mak3791b.zip
+ v2gnu/fil316b.zip
+ v2gnu/sed302b.zip
+ v2gnu/txt20b.zip
+ v2gnu/dif272b.zip
+ v2gnu/grep24b.zip
+ v2gnu/shl112b.zip
+ v2gnu/gawk303b.zip
+ v2misc/csdpmi4b.zip
+
+or possibly any newer version.
+
+=item Pthreads
+
+Thread support is not tested in this version of the djgpp perl.
+
+=back
+
+=head2 Shortcomings of Perl under DOS
+
+Perl under DOS lacks some features of perl under UNIX because of
+deficiencies in the UNIX-emulation, most notably:
+
+=over 4
+
+=item *
+
+fork() and pipe()
+
+=item *
+
+some features of the UNIX filesystem regarding link count and file dates
+
+=item *
+
+in-place operation is a little bit broken with short filenames
+
+=item *
+
+sockets
+
+=back
+
+=head2 Building Perl on DOS
+
+=over 4
+
+=item *
+
+Unpack the source package F<perl5.6*.tar.gz> with djtarx. If you want
+to use long file names under w95 and also to get Perl to pass all its
+tests, don't forget to use
+
+ set LFN=y
+ set FNCASE=y
+
+before unpacking the archive.
+
+=item *
+
+Create a "symlink" or copy your bash.exe to sh.exe in your C<($DJDIR)/bin>
+directory.
+
+ ln -s bash.exe sh.exe
+
+[If you have the recommended version of bash for DJGPP, this is already
+done for you.]
+
+And make the C<SHELL> environment variable point to this F<sh.exe>:
+
+ set SHELL=c:/djgpp/bin/sh.exe (use full path name!)
+
+You can do this in F<djgpp.env> too. Add this line BEFORE any section
+definition:
+
+ +SHELL=%DJDIR%/bin/sh.exe
+
+=item *
+
+If you have F<split.exe> and F<gsplit.exe> in your path, then rename
+F<split.exe> to F<djsplit.exe>, and F<gsplit.exe> to F<split.exe>.
+Copy or link F<gecho.exe> to F<echo.exe> if you don't have F<echo.exe>.
+Copy or link F<gawk.exe> to F<awk.exe> if you don't have F<awk.exe>.
+
+[If you have the recommended versions of djdev, shell utilities and
+gawk, all these are already done for you, and you will not need to do
+anything.]
+
+=item *
+
+Chdir to the djgpp subdirectory of perl toplevel and type the following
+commands:
+
+ 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 to
+press ENTER. The "set" command ensures that DJGPP preserves the letter
+case of file names when reading directories. If you already issued this
+set command when unpacking the archive, and you are in the same DOS
+session as when you unpacked the archive, you don't have to issue the
+set 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 whether
+to continue, just answer with Y (this can only happen if you don't use
+long 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 the
+POSIX extension (this is the default), make sure that the stack
+size of your F<cc1.exe> is at least 512kbyte (you can check this
+with: C<stubedit cc1.exe>).
+
+You can use the Configure script in non-interactive mode too.
+When I built my F<perl.exe>, I used something like this:
+
+ configure.bat -des
+
+You can find more info about Configure's command line switches in
+the F<INSTALL> file.
+
+When the script ends, and you want to change some values in the
+generated F<config.sh> file, then run
+
+ sh Configure -S
+
+after you made your modifications.
+
+IMPORTANT: if you use this C<-S> switch, be sure to delete the CONFIG
+environment variable before running the script:
+
+ set CONFIG=
+
+=item *
+
+Now you can compile Perl. Type:
+
+ make
+
+=back
+
+=head2 Testing Perl on DOS
+
+Type:
+
+ make test
+
+If you're lucky you should see "All tests successful". But there can be
+a few failed subtests (less than 5 hopefully) depending on some external
+conditions (e.g. some subtests fail under linux/dosemu or plain dos
+with short filenames only).
+
+=head2 Installation of Perl on DOS
+
+Type:
+
+ make install
+
+This will copy the newly compiled perl and libraries into your DJGPP
+directory structure. Perl.exe and the utilities go into C<($DJDIR)/bin>,
+and the library goes under C<($DJDIR)/lib/perl5>. The pod documentation
+goes under C<($DJDIR)/lib/perl5/pod>.
+
+=head1 BUILDING AND INSTALLING MODULES ON DOS
+
+=head2 Building Prerequisites for Perl on DOS
+
+For building and installing non-XS modules, all you need is a working
+perl under DJGPP. Non-XS modules do not require re-linking the perl
+binary, and so are simpler to build and install.
+
+XS-type modules do require re-linking the perl binary, because part of
+an XS module is written in "C", and has to be linked together with the
+perl binary to be executed. This is required because perl under DJGPP
+is built with the "static link" option, due to the lack of "dynamic
+linking" in the DJGPP environment.
+
+Because XS modules require re-linking of the perl binary, you need both
+the perl binary distribution and the perl source distribution to build
+an XS extension module. In addition, you will have to have built your
+perl binary from the source distribution so that all of the components
+of the perl binary are available for the required link step.
+
+=head2 Unpacking CPAN Modules on DOS
+
+First, download the module package from CPAN (e.g., the "Comma Separated
+Value" text package, Text-CSV-0.01.tar.gz). Then expand the contents of
+the package into some location on your disk. Most CPAN modules are
+built with an internal directory structure, so it is usually safe to
+expand it in the root of your DJGPP installation. Some people prefer to
+locate source trees under /usr/src (i.e., C<($DJDIR)/usr/src>), but you may
+put it wherever seems most logical to you, *EXCEPT* under the same
+directory as your perl source code. There are special rules that apply
+to modules which live in the perl source tree that do not apply to most
+of the modules in CPAN.
+
+Unlike other DJGPP packages, which are normal "zip" files, most CPAN
+module packages are "gzipped tarballs". Recent versions of WinZip will
+safely unpack and expand them, *UNLESS* they have zero-length files. It
+is a known WinZip bug (as of v7.0) that it will not extract zero-length
+files.
+
+From the command line, you can use the djtar utility provided with DJGPP
+to unpack and expand these files. For example:
+
+ C:\djgpp>djtarx -v Text-CSV-0.01.tar.gz
+
+This will create the new directory C<($DJDIR)/Text-CSV-0.01>, filling
+it with the source for this module.
+
+=head2 Building Non-XS Modules on DOS
+
+To build a non-XS module, you can use the standard module-building
+instructions 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 perl
+binary is needed to build, install or use non-XS modules.
+
+=head2 Building XS Modules on DOS
+
+To build an XS module, you must use the standard module-building
+instructions distributed with perl modules *PLUS* three extra
+instructions 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 so
+that the new perl binary which you must build for an XS-type module will
+build correctly. The second extra instruction re-builds the perl binary
+in your module directory before you run "make test", so that you are
+testing with the new module code you built with "make". The third extra
+instruction installs the perl binary from your module directory into the
+standard DJGPP binary directory, C<($DJDIR)/bin>, replacing your
+previous perl binary.
+
+Note that the MAP_TARGET value *must* have the ".exe" extension or you
+will not create a "perl.exe" to replace the one in C<($DJDIR)/bin>.
+
+When you are done, the XS-module install process will have added information
+to yout "perllocal" information telling that the perl binary has been replaced,
+and what module was installed. you can view this information at any time
+by using the command:
+
+ perl -S perldoc perllocal
+
+=head1 AUTHOR
+
+Laszlo Molnar, F<laszlo.molnar@eth.ericsson.se> [Installing/building perl]
+
+Peter J. Farley III F<pjfarley@banet.net> [Building/installing modules]
+
+=head1 SEE ALSO
+
+perl(1).
+
+=cut
+
View
12 README.epoc
@@ -73,7 +73,7 @@ redirection. You will have to reboot the PDA!
=head1 USING PERL ON EPOC
-=head2 I/O Redirection
+=head2 I/O Redirection on Epoc
You can redirect the output with the UNIX bourne shell syntax (this is
built into perl rather then eshell) For instance the following command
@@ -85,7 +85,7 @@ perl test.pl >stdout_file <stdin_file 2>stderr_file
Alternatively you can use 2>&1 in order to add the standard error
output to stdout.
-=head2 PATH Names
+=head2 PATH Names on Epoc
ESHELL looks for executables in ?:/System/Programs. The SIS file
installs perl in this special folder directory. The default drive and
@@ -107,16 +107,16 @@ internally in perl, so please use slashes for redirects.
perl.exe C:/test.pl >C:/output.txt
-=head2 Editors
+=head2 Editors on Epoc
A suitable text editor can be downloaded from symbian
http://developer.epocworld.com/downloads/progs/Editor.zip
-=head2 Features
+=head2 Features of Perl on Epoc
The built-in function EPOC::getcwd returns the current directory.
-=head2 Restrictions
+=head2 Restrictions of Perl on Epoc
Features are left out, because of restrictions of the POSIX support in
EPOC:
@@ -214,7 +214,7 @@ Start again from scratch
=back
-=head1 SUPPORT STATUS
+=head1 SUPPORT STATUS OF PERL ON EPOC
I'm offering this port "as is". You can ask me questions, but I can't
guarantee I'll be able to answer them.
View
16 README.hpux
@@ -98,7 +98,7 @@ the PA-RISC 1.1 or 2.0 platforms. The command-line flags are accepted,
but the resulting executable will not run when transferred to a PA-RISC
1.0 system.
-=head2 Itanium Processor Family
+=head2 Itanium Processor Family and HP-UX
HP-UX also runs on the new Itanium processor. This requires the use
of a different version of HP-UX (currently 11.20), and with the exception
@@ -213,7 +213,7 @@ flag -Aa is added to the cpprun and cppstdin variables in the config.sh
file (though see the section on 64-bit perl below). If you are using a
recent version of the Perl distribution, these flags are set automatically.
-=head2 Using Large Files with Perl
+=head2 Using Large Files with Perl on HP-UX
Beginning with HP-UX version 10.20, files larger than 2GB (2^31 bytes)
may be created and manipulated. Three separate methods of doing this
@@ -248,7 +248,7 @@ Configure. If you do not do this, but later answer the question about
large files when Configure asks you, you may get a configuration that
cannot be compiled, or that does not function as expected.
-=head2 Threaded Perl
+=head2 Threaded Perl on HP-UX
It is possible to compile a version of threaded Perl on any version of
HP-UX before 10.30, but it is strongly suggested that you be running on
@@ -268,7 +268,7 @@ April 1999 (B3920-13941)" or the Freely available PTH package, available
though worldwide HP-UX mirrors of precompiled packages
(e.g. http://hpux.tn.tudelft.nl/hppd/hpux/alpha.html)
-=head2 64-bit Perl
+=head2 64-bit Perl on HP-UX
Beginning with HP-UX 11.00, programs compiled under HP-UX can take
advantage of the LP64 programming environment (LP64 means Longs and
@@ -299,20 +299,20 @@ expected.
compiler. If you want to compile Perl using gcc, you will have to get a
version of the compiler that support 64-bit operations.)
-=head2 GDBM and Threads
+=head2 GDBM and Threads on HP-UX
If you attempt to compile Perl with threads on an 11.X system and also
link in the GDBM library, then Perl will immediately core dump when it
starts up. The only workaround at this point is to relink the GDBM
library under 11.X, then relink it into Perl.
-=head2 NFS filesystems and utime(2)
+=head2 NFS filesystems and utime(2) on HP-UX
If you are compiling Perl on a remotely-mounted NFS filesystem, the test
io/fs.t may fail on test #18. This appears to be a bug in HP-UX and no
fix is currently available.
-=head2 perl -P and //
+=head2 perl -P and // and HP-UX
In HP-UX Perl is compiled with flags that will cause problems if the
-P flag of Perl (preprocess Perl code with the C preprocessor before
@@ -331,7 +331,7 @@ like for example C<"!">:
s!foo!!;
-=head2 Kernel parameters (maxdsiz)
+=head2 HP-UX Kernel Parameters (maxdsiz) for Compiling Perl
By default, HP-UX comes configured with a maximum data segment size of
64MB. This is too small to correctly compile Perl with the maximum
View
34 README.hurd
@@ -1,13 +1,19 @@
-Notes on Perl on the Hurd
-Last Updated: Fri, 29 Oct 1999 22:50:30 +0200
-Written by: Mark Kettenis <kettenis@gnu.org>
+If you read this file _as_is_, just ignore the funny characters you see.
+It is written in the POD format (see pod/perlpod.pod) which is specially
+designed to be readable as is.
+
+=head1 NAME
+
+README.hurd - Perl version 5 on Hurd
+
+=head1 DESCRIPTION
If you want to use Perl on the Hurd, I recommend using the Debian
GNU/Hurd distribution (see http://www.debian.org), even if an
official, stable release has not yet been made. The old `gnu-0.2'
binary distribution will most certainly have additional problems.
-* Known Problems
+=head2 Known Problems with Perl on Hurd
The Perl test suite may still report some errors on the Hurd. The
`lib/anydbm' and `pragma/warnings' tests will almost certainly fail.
@@ -21,12 +27,13 @@ information.
Here are the statistics for Perl 5.005_62 on my system:
-Failed Test Status Wstat Total Fail Failed List of failed
--------------------------------------------------------------------------------
-lib/anydbm.t 12 1 8.33% 12
-pragma/warnings 333 1 0.30% 215
-8 tests and 24 subtests skipped.
-Failed 2/229 test scripts, 99.13% okay. 2/10850 subtests failed, 99.98% okay.
+ Failed Test Status Wstat Total Fail Failed List of failed
+ -------------------------------------------------------------------------
+ lib/anydbm.t 12 1 8.33% 12
+ pragma/warnings 333 1 0.30% 215
+
+ 8 tests and 24 subtests skipped.
+ Failed 2/229 test scripts, 99.13% okay. 2/10850 subtests failed, 99.98% okay.
There are quite a few systems out there that do worse!
@@ -38,3 +45,10 @@ encounter more failures. Likely candidates are: `op/stat', `lib/io_pipe',
In any way, if you're seeing failures beyond those mentioned in this
document, please consider upgrading to the latest Hurd before reporting
the failure as a bug.
+
+=head1 AUTHOR
+
+Mark Kettenis <kettenis@gnu.org>
+
+Last Updated: Fri, 29 Oct 1999 22:50:30 +0200
+
View
4 README.machten
@@ -31,7 +31,7 @@ system before running the C<make> command.
For much more information on building perl -- for example, on how to
change the default installation directory -- see F<INSTALL>.
-=head2 Failures during C<make test>
+=head2 Failures during C<make test> on MachTen
=over 4
@@ -57,7 +57,7 @@ and limited in its effect on practical Perl programs.
=back
-=head2 Building external modules
+=head2 Building external modules on MachTen
To add an external module to perl, build in the normal way, which
is documented in L<ExtUtils::MakeMaker>, or which can be driven
View
2  README.macos
@@ -45,14 +45,12 @@ for all things having to do with MacPerl development.
MacPerl 5.2.0r4 is available on the CPAN and on SourceForge. It
is based on perl 5.004.
-
=head1 AUTHOR
perl was ported to Mac OS by Matthias Neeracher
E<lt>neeracher@mac.comE<gt>. It is currently maintained by Chris
Nandor E<lt>pudge@pobox.comE<gt>.
-
=head1 DATE
Last modified 2001.04.05.
View
8 README.micro
@@ -4,6 +4,12 @@ on the other hand this means that interfaces between Perl and your
operating system are left very -- minimal.
All this is experimental. If you don't know what to do with microperl
-you probably shouldn't.
+you probably shouldn't. Do not report bugs in microperl; fix the bugs.
+
+If you are still reading this and you are itching to try out microperl:
+
+ make -f Makefile.micro
+
+
View
24 README.mint
@@ -1,6 +1,12 @@
-##########################################################################
-# *** README.mint
-##########################################################################
+If you read this file _as_is_, just ignore the funny characters you see.
+It is written in the POD format (see pod/perlpod.pod) which is specially
+designed to be readable as is.
+
+=head1 NAME
+
+README.mint - Perl version 5 on Atari MiNT
+
+=head1 DESCRIPTION
If you want to build perl yourself on MiNT (or maybe on an Atari without
MiNT) you may want to accept some advice from somebody who already did it...
@@ -23,8 +29,7 @@ provided that the user has a Eunuchs-like environment (i.e. the
standard envariables like $PATH, $HOME, ... are set, there is a
POSIX compliant shell in /bin/sh, and...)
-Known problems
-==============
+=head1 Known problems with Perl on MiNT
The problems you may encounter when building perl on your machine
are most probably due to deficiencies in MiNT resp. the Atari
@@ -210,7 +215,10 @@ OK, this was my motto while working on Perl for MiNT, especially rule (1)...
Have fun with Perl!
+=head1 AUTHOR
+
Guido Flohr
---
-mailto:gufl0000@stud.uni-sb.de
-http://stud.uni-sb.de/~gufl0000
+
+ mailto:gufl0000@stud.uni-sb.de
+ http://stud.uni-sb.de/~gufl0000
+
View
16 README.mpeix
@@ -17,7 +17,7 @@ README.mpeix - Perl/iX for HP e3000 MPE
This is a podified version of the above-mentioned web page,
podified by Jarkko Hietaniemi 2001-Jan-01.
-=head1 What's New
+=head1 What's New in Perl ffor MPE/iX
June 1, 2000
@@ -105,7 +105,7 @@ Migrated from cccd.edu to bixby.org.
=back
-=head1 Welcome
+=head1 Welcome to Perl/iX
This is the official home page for the HP e3000 MPE/iX
(http://www.businessservers.hp.com/) port of the Perl scripting
@@ -135,7 +135,7 @@ IMPORTANT NOTICE: Yes, I do work for the HP CSY R&D lab, but ALL of
the software you download from bixby.org is my personal freeware that
is NOT supported by HP.
-=head1 System Requirements
+=head1 System Requirements for Perl/iX
=over 4
@@ -271,7 +271,7 @@ machines because the 6.0 or later update process does it for you.
=back
-=head1 Distribution Contents Highlights
+=head1 Perl/iX Distribution Contents Highlights
=over 4
@@ -436,11 +436,11 @@ GETPRIVMODE() solution similar to bind().
=back
-=head1 Known Bugs Under Investigation
+=head1 Known Perl/iX Bugs Under Investigation
None.
-=head1 To-Do List
+=head1 Perl/iX To-Do List
=over 4
@@ -463,7 +463,7 @@ MPE functions like GETPRIVMODE(), GETUSERMODE(), and sfcntl().
=back
-=head1 Change History
+=head1 Perl/iX Change History
May 6, 1999
@@ -669,7 +669,7 @@ Porting begins.
=back
-=head1 Author
+=head1 AUTHOR
Mark Bixby, mark@bixby.org
View
30 README.os390
@@ -1,9 +1,7 @@
-
This document is written in pod format hence there are punctuation
-characters in odd places. Do not worry, you've apparently got
-the ASCII->EBCDIC translation worked out correctly. You can read
-more about pod in pod/perlpod.pod or the short summary in the
-INSTALL file.
+characters in odd places. Do not worry, you've apparently got the
+ASCII->EBCDIC translation worked out correctly. You can read more
+about pod in pod/perlpod.pod or the short summary in the INSTALL file.
=head1 NAME
@@ -23,7 +21,7 @@ the ones we've tested it on.
You may need to carry out some system configuration tasks before
running the Configure script for Perl.
-=head2 Unpacking
+=head2 Unpacking Perl distribution on OS/390
Gunzip/gzip for OS/390 is discussed at:
@@ -33,7 +31,7 @@ to extract an ASCII tar archive on OS/390, try this:
pax -o to=IBM-1047,from=ISO8859-1 -r < latest.tar
-=head2 Setup and utilities
+=head2 Setup and utilities for Perl on OS/390
Be sure that your yacc installation is in place including any necessary
parser template files. If you have not already done so then be sure to:
@@ -87,7 +85,7 @@ to build its "Socket" extension.
For successful testing you may need to turn on the sticky bit for your
world readable /tmp directory if you have not already done so (see man chmod).
-=head2 Configure
+=head2 Configure Perl on OS/390
Once you've unpacked the distribution, run "sh Configure" (see INSTALL
for a full discussion of the Configure options). There is a "hints" file
@@ -156,7 +154,7 @@ properly set up your /etc networking files.
=back
-=head2 Build, test, install
+=head2 Build, Test, Install Perl on OS/390
Simply put:
@@ -172,7 +170,7 @@ this last step may or may not require UID=0 privileges depending
on how you answered the questions that Configure asked and whether
or not you have write access to the directories you specified.
-=head2 build anomalies
+=head2 Build Anomalies with Perl on OS/390
"Out of memory!" messages during the build of Perl are most often fixed
by re building the GNU make utility for OS/390 from a source code kit.
@@ -196,7 +194,7 @@ If the c89 compiler complains of syntax errors during the build of the
Socket extension then be sure to fix the syntax error in the system
header /usr/include/sys/socket.h.
-=head2 testing anomalies
+=head2 Testing Anomalies with Perl on OS/390
The `make test` step runs a Perl Verification Procedure, usually before
installation. You might encounter STDERR messages even during a successful
@@ -279,13 +277,13 @@ is needed to get through the test suite.
=back
-=head2 installation anomalies
+=head2 Installation Anomalies with Perl on OS/390
The installman script will try to run on OS/390. There will be fewer errors
if you have a roff utility installed. You can obtain GNU groff from the
Redbook SG24-5944-00 ftp site.
-=head2 Usage Hints
+=head2 Usage Hints for Perl on OS/390
When using perl on OS/390 please keep in mind that the EBCDIC and ASCII
character sets are different. See perlebcdic.pod for more on such character
@@ -307,7 +305,7 @@ If you are having trouble with square brackets then consider switching your
rlogin or telnet client. Try to avoid older 3270 emulators and ISHELL for
working with Perl on USS.
-=head2 Floating point anomalies
+=head2 Floating Point Anomalies with Perl on OS/390
There appears to be a bug in the floating point implementation on S/390
systems such that calling int() on the product of a number and a small
@@ -341,7 +339,7 @@ The problem can be further examined in a roughly equivalent C program:
/* y is 0.000000e+00 and z is 1.000000e+05 (with c89) */
}
-=head2 Modules and Extensions
+=head2 Modules and Extensions for Perl on OS/390
Pure pure (that is non xs) modules may be installed via the usual:
@@ -402,7 +400,7 @@ L<INSTALL>, L<perlport>, L<perlebcdic>, L<ExtUtils::MakeMaker>.
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/CBCUG030/
-=head2 Mailing list
+=head2 Mailing list for Perl on OS/390
The Perl Institute (http://www.perl.org/) maintains a perl-mvs
mailing list of interest to all folks building and/or
View
153 README.plan9
@@ -1,27 +1,146 @@
+If you read this file _as_is_, just ignore the funny characters you see.
+It is written in the POD format (see pod/perlpod.pod) which is specially
+designed to be readable as is.
+
+=head1 NAME
+
+perlplan9 - Plan 9-specific documentation for Perl
+
+=head1 DESCRIPTION
+
+These are a few notes describing features peculiar to
+Plan 9 Perl. As such, it is not intended to be a replacement
+for the rest of the Perl 5 documentation (which is both
+copious and excellent). If you have any questions to
+which you can't find answers in these man pages, contact
+Luther Huffman at lutherh@stratcom.com and we'll try to
+answer them.
+
+=head2 Invoking Perl
+
+Perl is invoked from the command line as described in
+L<perl>. Most perl scripts, however, do have a first line
+such as "#!/usr/local/bin/perl". This is known as a shebang
+(shell-bang) statement and tells the OS shell where to find
+the perl interpreter. In Plan 9 Perl this statement should be
+"#!/bin/perl" if you wish to be able to directly invoke the
+script by its name.
+ Alternatively, you may invoke perl with the command "Perl"
+instead of "perl". This will produce Acme-friendly error
+messages of the form "filename:18".
+
+Some scripts, usually identified with a *.PL extension, are
+self-configuring and are able to correctly create their own
+shebang path from config information located in Plan 9
+Perl. These you won't need to be worried about.
+
+=head2 What's in Plan 9 Perl
+
+Although Plan 9 Perl currently only provides static
+loading, it is built with a number of useful extensions.
+These include Opcode, FileHandle, Fcntl, and POSIX. Expect
+to see others (and DynaLoading!) in the future.
+
+=head2 What's not in Plan 9 Perl
+
+As mentioned previously, dynamic loading isn't currently
+available nor is MakeMaker. Both are high-priority items.
+
+=head2 Perl5 Functions not currently supported in Plan 9 Perl
+
+Some, such as C<chown> and C<umask> aren't provided
+because the concept does not exist within Plan 9. Others,
+such as some of the socket-related functions, simply
+haven't been written yet. Many in the latter category
+may be supported in the future.
+
+The functions not currently implemented include:
+
+ chown, chroot, dbmclose, dbmopen, getsockopt,
+ setsockopt, recvmsg, sendmsg, getnetbyname,
+ getnetbyaddr, getnetent, getprotoent, getservent,
+ sethostent, setnetent, setprotoent, setservent,
+ endservent, endnetent, endprotoent, umask
+
+There may be several other functions that have undefined
+behavior so this list shouldn't be considered complete.
+
+=head2 Signals in Plan 9 Perl
+
+For compatibility with perl scripts written for the Unix
+environment, Plan 9 Perl uses the POSIX signal emulation
+provided in Plan 9's ANSI POSIX Environment (APE). Signal stacking
+isn't supported. The signals provided are:
+
+ SIGHUP, SIGINT, SIGQUIT, SIGILL, SIGABRT,
+ SIGFPE, SIGKILL, SIGSEGV, SIGPIPE, SIGPIPE, SIGALRM,
+ SIGTERM, SIGUSR1, SIGUSR2, SIGCHLD, SIGCONT,
+ SIGSTOP, SIGTSTP, SIGTTIN, SIGTTOU
+
+=head1 COMPILING AND INSTALLING PERL ON PLAN 9
+
WELCOME to Plan 9 Perl, brave soul!
- This is a preliminary alpha version of Plan 9 Perl. Still to be implemented are MakeMaker and DynaLoader. Many perl commands are missing or currently behave in an inscrutable manner. These gaps will, with perserverance and a modicum of luck, be remedied in the near future.To install this software:
- 1. Create the source directories and libraries for perl by running the plan9/setup.rc command (i.e., located in the plan9 subdirectory). Note: the setup routine assumes that you haven't dearchived these files into /sys/src/cmd/perl. After running setup.rc you may delete the copy of the source you originally detarred, as source code has now been installed in /sys/src/cmd/perl. If you plan on installing perl binaries for all architectures, run "setup.rc -a".
-After
- 2. Making sure that you have adequate privileges to build system software, from /sys/src/cmd/perl/5.00301 run:
-mk install
- If you wish to install perl versions for all architectures (68020, mips, sparc and 386) run:
-mk installall
+ This is a preliminary alpha version of Plan 9 Perl. Still to be
+implemented are MakeMaker and DynaLoader. Many perl commands are
+missing or currently behave in an inscrutable manner. These gaps will,
+with perserverance and a modicum of luck, be remedied in the near
+future.To install this software:
+
+1. Create the source directories and libraries for perl by running the
+plan9/setup.rc command (i.e., located in the plan9 subdirectory).
+Note: the setup routine assumes that you haven't dearchived these
+files into /sys/src/cmd/perl. After running setup.rc you may delete
+the copy of the source you originally detarred, as source code has now
+been installed in /sys/src/cmd/perl. If you plan on installing perl
+binaries for all architectures, run "setup.rc -a".
+
+2. After making sure that you have adequate privileges to build system
+software, from /sys/src/cmd/perl/5.00301 (adjust version
+appropriately) run:
+
+ mk install
+
+If you wish to install perl versions for all architectures (68020,
+mips, sparc and 386) run:
+
+ mk installall
+
+3. Wait. The build process will take a *long* time because perl
+bootstraps itself. A 75MHz Pentium, 16MB RAM machine takes roughly 30
+minutes to build the distribution from scratch.
- 3. Wait. The build process will take a *long* time because perl bootstraps itself. A 75MHz Pentium, 16MB RAM machine takes roughly 30 minutes to build the distribution from scratch.
+=head2 Installing Perl Documentation on Plan 9
+
+This perl distribution comes with a tremendous amount of
+documentation. To add these to the built-in manuals that come with
+Plan 9, from /sys/src/cmd/perl/5.00301 (adjust version appropriately)
+run:
+
+ mk man
-INSTALLING DOCUMENTATION
-This perl distribution comes with a tremendous amount of documentation. To add these to the built-in manuals that come with Plan 9, from /sys/src/cmd/perl/5.00301 run:
-mk man
To begin your reading, start with:
-man perl
-This is a good introduction and will direct you towards other man pages that may interest you. For information specific to Plan 9 Perl, try:
-man perlplan9
+
+ man perl
+
+This is a good introduction and will direct you towards other man
+pages that may interest you.
(Note: "mk man" may produce some extraneous noise. Fear not.)
-Direct questions, comments, and the unlikely bug report (ahem) direct comments toward:
-lutherh@stratcom.com
+=head1 BUGS
+
+"As many as there are grains of sand on all the beaches of the
+world . . ." - Carl Sagan
+
+=head1 Revision date
+
+This document was revised 09-October-1996 for Perl 5.003_7.
+
+=head1 AUTHOR
+
+Direct questions, comments, and the unlikely bug report (ahem) direct
+comments toward:
-Luther Huffman
+Luther Huffman, lutherh@stratcom.com,
Strategic Computer Solutions, Inc.
View
100 README.qnx
@@ -1,22 +1,96 @@
-README.qnx
+If you read this file _as_is_, just ignore the funny characters you see.
+It is written in the POD format (see pod/perlpod.pod) which is specially
+designed to be readable as is.
-Please see hints/qnx.sh for more detailed information about compiling
-perl under QNX4.
+=head1 NAME
+
+README.qnx - Perl version 5 on QNX
+
+=head1 DESCRIPTION
+
+As of perl5.004_04, all tests pass under:
+
+ QNX 4.23A
+ Watcom 10.6 with Beta/970211.wcc.update.tar.F
+ socket3r.lib Nov21 1996.
+
+Update June 2001: Perl 5.6.1 most probably also works just fine in QNX.
+
+=head2 Required Software for Compiling Perl on QNX
+
+As with many unix ports, this one depends on a few "standard"
+unix utilities which are not necessarily standard for QNX.
+
+=over 4
+
+=item /bin/sh
+
+This is used heavily by Configure and then by
+perl itself. QNX's version is fine, but Configure
+will choke on the 16-bit version, so if you are
+running QNX 4.22, link /bin/sh to /bin32/ksh
+
+=item ar
+
+This is the standard unix library builder.
+We use wlib. With Watcom 10.6, when wlib is
+linked as "ar", it behaves like ar and all is
+fine. Under 9.5, a cover is required. One is
+included in ../qnx
+
+=item nm
+
+This is used (optionally) by configure to list
+the contents of libraries. I will generate
+a cover function on the fly in the UU directory.
+
+=item cpp
+
+Configure and perl need a way to invoke a C
+preprocessor. I have created a simple cover
+for cc which does the right thing. Without this,
+Configure will create it's own wrapper which works,
+but it doesn't handle some of the command line arguments
+that perl will throw at it.
+
+=item make
+
+You really need GNU make to compile this. GNU make
+ships by default with QNX 4.23, but you can get it
+from quics for earlier versions.
+
+=back
+
+=head2 Outstanding Issues with Perl on QNX
+
+There is currently no support for dynamically linked libraries.
+
+=head2 QNX auxiliary files
The files in the "qnx" directory are:
- * "qnx/ar" is a script that emulates the standard unix archive (aka
- library) utility. Under Watcom 10.6, ar is linked to wlib and
- provides the expected interface. With Watcom 9.5, a cover function
- is required. This one is fairly crude but has proved adequate for
- compiling perl. A more thorough version is available at:
+=over 4
+
+=item qnx/ar
+
+A script that emulates the standard unix archive (aka library)
+utility. Under Watcom 10.6, ar is linked to wlib and provides the
+expected interface. With Watcom 9.5, a cover function is
+required. This one is fairly crude but has proved adequate for
+compiling perl. A more thorough version is available at:
http://www.fdma.com/pub/qnx/porting/ar
- * "qnx/cpp" is a script that provides C preprocessing functionality.
- Configure can generate a similar cover, but it doesn't handle all
- the command-line options that perl throws at it. This might be
- reasonably placed in /usr/local/bin.
+=item qnx/cpp
+
+A script that provides C preprocessing functionality. Configure can
+generate a similar cover, but it doesn't handle all the command-line
+options that perl throws at it. This might be reasonably placed in
+/usr/local/bin.
+
+=back
+
+=head1 AUTHOR
---
Norton T. Allen (allen@huarp.harvard.edu)
+
View
26 README.solaris
@@ -73,7 +73,7 @@ All Solaris documentation is available on-line at L<http://docs.sun.com>.
=head1 SETTING UP
-=head2 File Extraction Problems.
+=head2 File Extraction Problems on Solaris.
Be sure to use a tar program compiled under Solaris (not SunOS 4.x)
to extract the perl-5.x.x.tar.gz file. Do not use GNU tar compiled
@@ -85,7 +85,7 @@ If you found this advice it too late and used a SunOS4-compiled tar
anyway, you must find the incorrectly renamed file and move it back
to lib/locale.pm.
-=head2 Compiler and Related Tools.
+=head2 Compiler and Related Tools on Solaris.
You must use an ANSI C compiler to build perl. Perl can be compiled
with either Sun's add-on C compiler or with gcc. The C compiler that
@@ -197,7 +197,7 @@ Normally this is not a problem since the solaris hints file prevents
Configure from even looking in /usr/ucblib for libraries, and also
explicitly omits -lucb.
-=head2 Environment
+=head2 Environment for Compiling Perl on Solaris
=head3 PATH
@@ -234,7 +234,7 @@ See the INSTALL file for general information regarding Configure.
Only Solaris-specific issues are discussed here. Usually, the
defaults should be fine.
-=head2 64-bit Issues.
+=head2 64-bit Issues with Perl on Solaris.
See the INSTALL file for general information regarding 64-bit compiles.
In general, the defaults should be fine for most people.
@@ -362,7 +362,7 @@ requested.
As of 5.6.0, long doubles are not working.
-=head2 Threads.
+=head2 Threads in Perl on Solaris.
It is possible to build a threaded version of perl on Solaris. The entire
perl thread implementation is still experimental, however, so beware.
@@ -370,7 +370,7 @@ Perl uses the sched_yield(3RT) function. In versions of Solaris up
to 2.6, that function is in -lposix4. Starting with Solaris 7, it is
in -lrt. The hints file should handle adding this automatically.
-=head2 Malloc Issues.
+=head2 Malloc Issues with Perl on Solaris.
Starting from Perl 5.7.1 Perl uses the Solaris malloc, since the perl
malloc breaks when dealing with more than 2GB of memory, and the Solaris
@@ -431,14 +431,14 @@ directory.
=head1 MAKE TEST
-=head2 op/stat.t test 4
+=head2 op/stat.t test 4 in Solaris
op/stat.t test 4 may fail if you are on a tmpfs of some sort.
Building in /tmp sometimes shows this behavior. The
test suite detects if you are building in /tmp, but it may not be able
to catch all tmpfs situations.
-=head1 PREBUILT BINARIES.
+=head1 PREBUILT BINARIES OF PERL FOR SOLARIS.
You can pick up prebuilt binaries for Solaris from
L<http://www.sunfreeware.com/>, ActiveState L<http://www.activestate.com/>,
@@ -446,9 +446,9 @@ and L<http://www.perl.com/> under the Binaries list at the top of the page.
There are probably other sources as well. Please note that these sites
are under the control of their respective owners, not the perl developers.
-=head1 RUNTIME ISSUES.
+=head1 RUNTIME ISSUES FOR PERL ON SOLARIS.
-=head2 Limits on Numbers of Open Files.
+=head2 Limits on Numbers of Open Files on Solaris.
The stdio(3C) manpage notes that only 255 files may be opened using
fopen(), and only file descriptors 0 through 255 can be used in a
@@ -463,7 +463,7 @@ L<http://www.cpan.org/modules/by-module/Solaris/>.
=head1 SOLARIS-SPECIFIC PROBLEMS WITH MODULES.
-=head2 Proc::ProcessTable
+=head2 Proc::ProcessTable on Solaris
Proc::ProcessTable does not compile on Solaris with perl5.6.0 and higher
if you have LARGEFILES defined. Since largefile support is the
@@ -483,13 +483,13 @@ under the correct environment. Everything should then be OK as long as
Proc::ProcessTable doesn't try to share off_t's with the rest of perl,
or if it does they should be explicitly specified as off64_t.
-=head2 BSD::Resource
+=head2 BSD::Resource on Solairs
BSD::Resource versions earlier than 1.09 do not compile on Solaris
with perl 5.6.0 and higher, for the same reasons as Proc::ProcessTable.
BSD::Resource versions starting from 1.09 have a workaround for the problem.
-=head2 Net::SSLeay
+=head2 Net::SSLeay on Soalris
Net::SSLeay requires a /dev/urandom to be present. This device is not
part of Solaris. You can either get the package SUNWski (packaged with
View
21 README.vmesa
@@ -26,20 +26,20 @@ the source code below /usr/local (though that is where it will be
installed by default). You may need to worry about the networking
configuration files discussed in the last bullet below.
-=head2 Unpacking
+=head2 Unpacking Perl Distribution on VM/ESA
To extract an ASCII tar archive on VM/ESA, try this:
pax -o to=IBM-1047,from=ISO8859-1 -r < latest.tar
-=head2 Setup and utilities
+=head2 Setup Perl and utilities on VM/ESA
GNU make for VM/ESA, which may be required for the build of perl,
is available from:
http://pucc.princeton.edu/~neale/vmoe.html
-=head2 Configure
+=head2 Configure Perl on VM/ESA
Once you've unpacked the distribution, run Configure (see INSTALL for
full discussion of the Configure options), and then run make, then
@@ -79,7 +79,7 @@ statements in the preprocessor output (.i) file.
=back
-=head2 testing anomalies
+=head2 Testing Anomalies of Perl on VM/ESA
The `make test` step runs a Perl Verification Procedure, usually before
installation. As the 5.6.1 kit was was being assembled
@@ -89,7 +89,7 @@ your results may differ:
[the list of failures being compiled]
-=head2 Usage Hints
+=head2 Usage Hints for Perl on VM/ESA
When using perl on VM/ESA please keep in mind that the EBCDIC and ASCII
character sets are different. Perl builtin functions that may behave
@@ -112,12 +112,13 @@ Neale Ferguson.
L<INSTALL>, L<perlport>, L<perlebcdic>.
-=head2 Mailing list
+=head2 Mailing list for Perl on VM/ESA
-If you are interested in the VM and OS/390 ports of perl then see the
-perl-mvs mailing list: The Perl Institute (http://www.perl.org/)
-maintains a mailing list of interest to all folks building and/or
-using perl on EBCDIC platforms. To subscribe, send a message of:
+If you are interested in the VM/ESA, z/OS (formerly known as OS/390)
+and POSIX-BC (BS2000) ports of Perl then see the perl-mvs mailing list:
+The Perl Institute (http://www.perl.org/) maintains a mailing list of
+interest to all folks building and/or using perl on EBCDIC platforms.
+To subscribe, send a message of:
subscribe perl-mvs
View
24 README.vms
@@ -36,7 +36,7 @@ but the media charges might prohibit an upgrade), consider getting Gnu C
instead.
-=head2 Introduction
+=head2 Introduction to Perl on VMS
The VMS port of Perl is as functionally complete as any other Perl port
(and as complete as the ports on some Unix systems). The Perl binaries
@@ -59,7 +59,7 @@ There are issues with various versions of DEC C, so if you're not running a
relatively modern version, check the "DEC C issues" section later on in this
document.
-=head2 Other required software
+=head2 Other required software for Compiling Perl on VMS
In addition to VMS and DCL you will need two things:
@@ -79,7 +79,7 @@ go ahead and use that.
=back
-=head2 Additional software that is optional
+=head2 Additional software that is optional for Perl on VMS
You may also want to have on hand:
@@ -207,7 +207,7 @@ then be sure to also follow the advice in the "Cleaning up and starting
fresh (optional)" and the checklist of items in the "CAVEATS" sections
below.
-=head2 Changing compile-time options (optional)
+=head2 Changing compile-time options (optional) for Perl on VMS
Most of the user definable features of Perl are enabled or disabled in
[.VMS]CONFIG.VMS. There is code in there to Do The Right Thing, but that
@@ -224,7 +224,7 @@ The one exception is the various *DIR install locations. Changing those
requires changes in genconfig.pl as well. Be really careful if you need to
change these, as they can cause some fairly subtle problems.
-=head2 Socket Support (optional)
+=head2 Socket Support (optional) for Perl on VMS
Perl includes a number of functions for IP sockets, which are available if
you choose to compile Perl with socket support. Since IP networking is an
@@ -322,7 +322,7 @@ with DEC C, "gcc --version" with GNU CC). To obtain the version of MMS or
MMK you are running try "MMS/ident" or "MMK /ident". The GNU make version
can be identified with "make --version".
-=head2 Cleaning up and starting fresh (optional)
+=head2 Cleaning up and starting fresh (optional) installing Perl on VMS
If you need to recompile from scratch, you have to make sure you clean up
first. There is a procedure to do it--enter the *exact* MMS line you used
@@ -408,7 +408,7 @@ is to simply copy it into the system shareable library directory with:
See also the "INSTALLing images (optional)" section.
-=head2 Installing Perl into DCLTABLES (optional)
+=head2 Installing Perl into DCLTABLES (optional) on VMS
Execute the following command file to define PERL as a DCL command.
You'll need CMKRNL privilege to install the new dcltables.exe.
@@ -426,7 +426,7 @@ You'll need CMKRNL privilege to install the new dcltables.exe.
$ install replace sys$common:[syslib]dcltables.exe
$ exit
-=head2 INSTALLing images (optional)
+=head2 INSTALLing Perl images (optional) on VMS
On systems that are using perl quite a bit, and particularly those with
minimal RAM, you can boost the performance of perl by INSTALLing it as
@@ -494,7 +494,7 @@ A final thing that causes trouble is leftover pieces from a failed
build. If things go wrong make sure you do a "(MMK|MMS|make) realclean"
before you rebuild.
-=head2 DEC C issues
+=head2 DEC C issues with Perl on VMS
Note to DEC C users: Some early versions (pre-5.2, some pre-4. If you're DEC
C 5.x or higher, with current patches if any, you're fine) of the DECCRTL
@@ -531,7 +531,7 @@ See also:
Please note that in later versions "DEC C" may also be known as
"Compaq C".
-=head2 GNU issues
+=head2 GNU issues with Perl on VMS
It has been a while since the GNU utilities such as GCC or GNU make
were used to build perl on VMS. Hence they may require a great deal
@@ -555,11 +555,11 @@ to all subscribers of the list. There is a searchable archive of the list
on the web at:
http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/
-
+
To unsubscribe from VMSPERL send a message to VMSPERL-UNSUBSCRIBE@PERL.ORG.
Be sure to do so from the subscribed account that you are canceling.
-=head2 Web sites
+=head2 Web sites for Perl on VMS
Vmsperl pages on the web include:
View
4 README.vos
@@ -172,7 +172,7 @@ to see the order in which Perl searches these directories.
=head1 USING PERL IN VOS
-=head2 Unimplemented Features
+=head2 Unimplemented Features of Perl on VOS
If perl is built with the alpha version of VOS POSIX.1 support
and if it attempts to call an unimplemented VOS POSIX.1
@@ -182,7 +182,7 @@ a list of the unimplemented POSIX.1 functions. To see what
functions are unimplemented and what the error message looks
like, compile and execute "test_vos_dummies.c".
-=head2 Restrictions
+=head2 Restrictions of Perl on VOS
This port of Perl version 5 to VOS prefers Unix-style,
slash-separated pathnames over VOS-style greater-than-separated
View
1,432 README.win32
@@ -1,716 +1,716 @@
-If you read this file _as_is_, just ignore the funny characters you
-see. It is written in the POD format (see pod/perlpod.pod) which is
-specially designed to be readable as is.
-
-=head1 NAME
-
-perlwin32 - Perl under Win32
-
-=head1 SYNOPSIS
-
-These are instructions for building Perl under Windows (9x, NT and
-2000).
-
-=head1 DESCRIPTION
-
-Before you start, you should glance through the README file
-found in the top-level directory to which the Perl distribution
-was extracted. Make sure you read and understand the terms under
-which this software is being distributed.
-
-Also make sure you read L<BUGS AND CAVEATS> below for the
-known limitations of this port.
-
-The INSTALL file in the perl top-level has much information that is
-only relevant to people building Perl on Unix-like systems. In
-particular, you can safely ignore any information that talks about
-"Configure".
-
-You may also want to look at two other options for building
-a perl that will work on Windows NT: the README.cygwin and
-README.os2 files, each of which give a different set of rules to
-build a Perl that will work on Win32 platforms. Those two methods
-will probably enable you to build a more Unix-compatible perl, but
-you will also need to download and use various other build-time and
-run-time support software described in those files.
-
-This set of instructions is meant to describe a so-called "native"
-port of Perl to Win32 platforms. The resulting Perl requires no
-additional software to run (other than what came with your operating
-system). Currently, this port is capable of using one of the
-following compilers:
-
- Borland C++ version 5.02 or later
- Microsoft Visual C++ version 4.2 or later
- Mingw32 with GCC version 2.95.2 or better
-
-The last of these is a high quality freeware compiler. Support
-for it is still experimental. (Older versions of GCC are known
-not to work.)
-
-This port currently supports MakeMaker (the set of modules that
-is used to build extensions to perl). Therefore, you should be
-able to build and install most extensions found in the CPAN sites.
-See L<Usage Hints> below for general hints about this.
-
-=head2 Setting Up
-
-=over 4
-
-=item Make
-
-You need a "make" program to build the sources. If you are using
-Visual C++ under Windows NT or 2000, nmake will work. All other
-builds need dmake.
-
-dmake is a freely available make that has very nice macro features
-and parallelability.
-
-A port of dmake for Windows is available from:
-
- http://www.cpan.org/authors/id/GSAR/dmake-4.1pl1-win32.zip
-
-(This is a fixed version of the original dmake sources obtained from
-http://www.wticorp.com/dmake/. As of version 4.1PL1, the original
-sources did not build as shipped and had various other problems.
-A patch is included in the above fixed version.)
-
-Fetch and install dmake somewhere on your path (follow the instructions
-in the README.NOW file).
-
-There exists a minor coexistence problem with dmake and Borland C++
-compilers. Namely, if a distribution has C files named with mixed
-case letters, they will be compiled into appropriate .obj-files named
-with all lowercase letters, and every time dmake is invoked
-to bring files up to date, it will try to recompile such files again.
-For example, Tk distribution has a lot of such files, resulting in
-needless recompiles everytime dmake is invoked. To avoid this, you
-may use the script "sncfnmcs.pl" after a successful build. It is
-available in the win32 subdirectory of the Perl source distribution.
-
-=item Command Shell
-
-Use the default "cmd" shell that comes with NT. Some versions of the
-popular 4DOS/NT shell have incompatibilities that may cause you trouble.
-If the build fails under that shell, try building again with the cmd
-shell.
-
-The nmake Makefile also has known incompatibilities with the
-"command.com" shell that comes with Windows 9x. You will need to
-use dmake and makefile.mk to build under Windows 9x.
-
-The surest way to build it is on Windows NT, using the cmd shell.
-
-Make sure the path to the build directory does not contain spaces. The
-build usually works in this circumstance, but some tests will fail.
-
-=item Borland C++
-
-If you are using the Borland compiler, you will need dmake.
-(The make that Borland supplies is seriously crippled and will not
-work for MakeMaker builds.)
-
-See L</"Make"> above.
-
-=item Microsoft Visual C++
-
-The nmake that comes with Visual C++ will suffice for building.
-You will need to run the VCVARS32.BAT file, usually found somewhere
-like C:\MSDEV4.2\BIN. This will set your build environment.
-
-You can also use dmake to build using Visual C++; provided, however,
-you set OSRELEASE to "microsft" (or whatever the directory name
-under which the Visual C dmake configuration lives) in your environment
-and edit win32/config.vc to change "make=nmake" into "make=dmake". The
-latter step is only essential if you want to use dmake as your default
-make for building extensions using MakeMaker.
-
-=item Mingw32 with GCC
-
-GCC-2.95.2 binaries can be downloaded from:
-
- ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/
-
-You also need dmake. See L</"Make"> above on how to get it.
-
-The GCC-2.95.2 bundle comes with Mingw32 libraries and headers.
-
-Make sure you install the binaries that work with MSVCRT.DLL as indicated
-in the README for the GCC bundle. You may need to set up a few environment
-variables (usually ran from a batch file).
-
-There are a couple of problems with the version of gcc-2.95.2-msvcrt.exe
-released 7 November 1999:
-
-=over
-
-=item *
-
-It left out a fix for certain command line quotes. To fix this, be sure
-to download and install the file fixes/quote-fix-msvcrt.exe from the above
-ftp location.
-
-=item *
-
-The definition of the fpos_t type in stdio.h may be wrong. If your
-stdio.h has this problem, you will see an exception when running the
-test t/lib/io_xs.t. To fix this, change the typedef for fpos_t from
-"long" to "long long" in the file i386-mingw32msvc/include/stdio.h,
-and rebuild.
-
-=back
-
-A potentially simpler to install (but probably soon-to-be-outdated) bundle
-of the above package with the mentioned fixes already applied is available
-here:
-
- http://downloads.ActiveState.com/pub/staff/gsar/gcc-2.95.2-msvcrt.zip
- ftp://ftp.ActiveState.com/pub/staff/gsar/gcc-2.95.2-msvcrt.zip
-
-=back
-
-=head2 Building
-
-=over 4
-
-=item *
-
-Make sure you are in the "win32" subdirectory under the perl toplevel.
-This directory contains a "Makefile" that will work with
-versions of nmake that come with Visual C++, and a dmake "makefile.mk"
-that will work for all supported compilers. The defaults in the dmake
-makefile are setup to build using the GCC compiler.
-
-=item *
-
-Edit the makefile.mk (or Makefile, if you're using nmake) and change
-the values of INST_DRV and INST_TOP. You can also enable various
-build flags. These are explained in the makefiles.
-
-You will have to make sure that CCTYPE is set correctly and that
-CCHOME points to wherever you installed your compiler.
-
-The default value for CCHOME in the makefiles for Visual C++
-may not be correct for some versions. Make sure the default exists
-and is valid.
-
-If you have either the source or a library that contains des_fcrypt(),
-enable the appropriate option in the makefile. des_fcrypt() is not
-bundled with the distribution due to US Government restrictions
-on the export of cryptographic software. Nevertheless, this routine
-is part of the "libdes" library (written by Eric Young) which is widely
-available worldwide, usually along with SSLeay (for example,
-"ftp://fractal.mta.ca/pub/crypto/SSLeay/DES/"). Set CRYPT_SRC to the
-name of the file that implements des_fcrypt(). Alternatively, if
-you have built a library that contains des_fcrypt(), you can set
-CRYPT_LIB to point to the library name. The location above contains
-many versions of the "libdes" library, all with slightly different
-implementations of des_fcrypt(). Older versions have a single,