http://cygutils.netpedia.net/
-=head1 PREREQUISITES
+=head1 PREREQUISITES FOR COMPILING PERL ON CYGWIN
=head2 Cygwin = GNU+Cygnus+Windows (Don't leave UNIX without it)
=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
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
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
=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
=back
-=head2 Suspicious Warnings
+=head2 Suspicious Warnings on Cygwin
You may see some messages during Configure that seem suspicious.
=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:
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
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:
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
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)
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:
------------------------------------
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
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
------------------------------------
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
=back
-=head1 INSTALL
+=head1 INSTALL PERL ON CYGWIN
This will install Perl, including I<man> pages.
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
=back
-=head1 BUGS
+=head1 BUGS ON CYGWIN
When I<make> starts, it warns about overriding commands for F<perlmain.o>.
projects / p5sagit/p5-mst-13.2.git / blobdiff