=head1 NAME
-README.cygwin32 - notes about porting Perl to Cygwin32
+README.cygwin - Perl for Cygwin
=head1 SYNOPSIS
-=over
+This document will help you configure, make, test and install Perl
+on Cygwin. This document also describes features of Cygwin that will
+affect how Perl behaves at runtime.
-=item Cygwin32
+B<NOTE:> There are pre-built Perl packages available for Cygwin and a
+version of Perl is provided in the normal Cygwin install. If you do
+not need to customize the configuration, consider using one of those
+packages.
-The Cygwin tools are ports of the popular GNU development tools for
-Windows NT, 95, and 98. They run thanks to the Cygwin library which
-provides the UNIX system calls and environment these programs expect.
-More info about this project can be found at its home page
-http://sourceware.cygnus.com/cygwin/
-=item libperl.dll
+=head1 PREREQUISITES FOR COMPILING PERL ON CYGWIN
-These instructions and the default cygwin32 hints build a shared
-libperl.dll Perl library and enables dynamically loaded extensions.
+=head2 Cygwin = GNU+Cygnus+Windows (Don't leave UNIX without it)
-=back
+The Cygwin tools are ports of the popular GNU development tools for Win32
+platforms. They run thanks to the Cygwin library which provides the UNIX
+system calls and environment these programs expect. More information
+about this project can be found at:
+
+ http://www.cygwin.com/
+
+A recent net or commercial release of Cygwin is required.
+
+At the time this document was last updated, Cygwin 1.5.2 was current.
+
+
+=head2 Cygwin Configuration
+
+While building Perl some changes may be necessary to your Cygwin setup so
+that Perl builds cleanly. These changes are B<not> required for normal
+Perl usage.
+
+B<NOTE:> The binaries that are built will run on all Win32 versions.
+They do not depend on your host system (Win9x/WinME, WinNT/Win2K)
+or your Cygwin configuration (I<ntea>, I<ntsec>, binary/text mounts).
+The only dependencies come from hard-coded pathnames like C</usr/local>.
+However, your host system and Cygwin configuration will affect Perl's
+runtime behavior (see L</"TEST">).
+
+=over 4
+
+=item * C<PATH>
+
+Set the C<PATH> environment variable so that Configure finds the Cygwin
+versions of programs. Any Windows directories should be removed or
+moved to the end of your C<PATH>.
+
+=item * I<nroff>
+
+If you do not have I<nroff> (which is part of the I<groff> package),
+Configure will B<not> prompt you to install I<man> pages.
+
+=item * Permissions
-=head1 BUILDING
-
-=head2 Prerequisites
-
-=over
-
-=item Cygwin b20.1
-
-The latest stable Cygwin suite is beta20.1. It may be
-downloaded from ftp://go.cygnus.com/pub/sourceware.cygnus.com/cygwin/latest/
-or many mirror sites around the world.
-
-=item egcs-1.1.2
-
-This port was built with egcs-1.1.2 downloaded from
-ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/egcs-1.1.2/
-
-=item install executable
-
-To make life easier, you should download
-ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin/porters/Humblet_Pierre_A/install-cygwin-b20.sh,
-and use it as your install "executable." Just follow the instructions
-that are embedded as comments in the .sh file.
-
-=item Windows NT notes
-
-You should execute a 'chmod -R +w *' on the entire perl source directory.
-The configuration process creates new files (and thus needs write access
-to the directory) and sometimes, especially if you make repeated builds
-in the same directory, overwrites old files. If you do not enable write
-access, you're just asking for trouble. Reminder for B20.1: unless 'ntea'
-is included in the CYGWIN environment variable settings, chmod has no
-effect. See "environment," below.
-
-It is best if you build, test, and install as a normal user, not as
-Administrator or as any member of the Administrators group. There is
-a well-known NT-ism that affects Cygwin: all files that are created
-by any member of the Administrators B<group> are B<NOT> owned by
-that member. The ownership of those files is assigned to the
-Administrators group, instead. If the default access mode for new files
-is -rw-r--r--, then the original creator of the file cannot overwrite
-it: he no longer owns the file, no B<user> does. It is owned by the
-group, but group members don't have write access to it. This causes
-any number of problems, including make test / perl harness failures,
-installation failures, etc.
-
-In some cases, however, it is necessary to install as Administrator. For
-instance, if normal users are not allowed write access to the install
-directory. My solution, in this case, was to transfer ownership of the
-install directory tree (/usr/local) to a single, normal user, and
-set permissions to -rw-r--r-- (drwxr-xr-x for directories, of course).
-If you read the preceeding paragraph carefully, you might suspect that
-changing the permissions on the entire tree to -rw-rw-r--, but allowing
-the Administrators group to keep ownership should solve the problem.
-However, newly created directories (and the perl install creates a lot
-of them) will not allow group write access. Setting umask will not
-fix this problem, because umask is a B<negation> operator; it only
-specifies the types of accesses that will NOT be allowed on new files.
-For instance, umask u=rwx,g=rwx,o=rx means that world ('B<o>thers') will
-never be allowed write access, but owner ('B<u>ser') and B<g>roup B<might>
-be allowed write access. Everybody (u, g, and o) B<might>be allowed
-read access.
-
-In any case, Corinna Vinschen's ntsec patches B<may> eventually
-alleviate this whole mess, and are included in the development
-snapshots as of 24 May 1999. You will need to include 'ntsec' as
-one of the items in the CYGWIN variable setting. However, initial
-tests indicate some incompatibility the 0524 snapshot and this perl
-build.
-
-=item environment
-
-I (csw) found the following steps necessary for a successful build:
-
-=over
-
-=item path
-
-I set my path so that none of the windows directories showed up -
-otherwise Configure found the wrong executables (find, grep, etc).
-It is, however, important that '.' be in the path, because otherwise
-the build process can't execute the ld2 script that is created.
-
-=item mounts
-
-I had to unmount my f: drive. I have cygwin installed under
-F:\cygnus\cygwin-b20\, which is mounted as \. I also ordinarily
-have F:\ mounted as /f (i.e. mounted onto the empty directory
-F:\cygnus\cygwin-b20\f\ ). However, this causes Configure to
-"locate" the awk, tr, sed, etc. programs at
-/f/cygnus/cygwin-b20/usr/bin instead of /usr/bin.
-This ended up causing problems.
-
-I built and tested perl using all binary mounts. However, Eric Fifer
-has built and tested it using text mounts, but reported more failures
-during make test and perl harness. Based on his findings, and experiments
-performed by Sebastien Barre with the static build of perl, I can
-report that these test failures are B<not> due to any differences in
-the perl executable. Most of the failures encountered during a make test
-on text mounts can be eliminated by remounting as binary, and re-running
-the tests using the same executable. These test failures are due to
-problems in the test scripts, not the executable. See Appendix.
-
-One observation from experience with the static build of perl is that
-it's a bad idea to a mix a perl executable that was compiled using binary
-mounts with modules compiled using text mounts, and vice versa. Make
-sure your mount environment matches. This observation has not been
-confirmed with respect to the dynamically linked build of perl.
-
-=item environment variables
-
-For NT users, the CYGWIN variable should include the 'ntea' setting.
-However, if you have FAT drives on your system, as opposed to NTFS,
-please read the Cygwin FAQ concerning ntea before including it in
-your system settings. If you do not use ntea, you will encounter a
-few extra make test and/or perl harness failures. These are not
-indicative of a faulty perl executable, but only that your system
-settings do not allow the types of file access and ownership checking
-that the test scripts are attempting to verify. See Appendix.
-
-I unset INCLUDE and LIB (these two variables are set by MSVC5, and
-inherited from my Windows environment by cygwin). I'm not sure this made
-a difference, but it has caused problems in the past...
+On WinNT with either the I<ntea> or I<ntsec> C<CYGWIN> settings, directory
+and file permissions may not be set correctly. Since the build process
+creates directories and files, to be safe you may want to run a
+C<chmod -R +w *> on the entire Perl source tree.
+
+Also, it is a well known WinNT "feature" that files created by a login
+that is a member of the I<Administrators> group will be owned by the
+I<Administrators> group. Depending on your umask, you may find that you
+can not write to files that you just created (because you are no longer
+the owner). When using the I<ntsec> C<CYGWIN> setting, this is not an
+issue because it "corrects" the ownership to what you would expect on
+a UNIX system.
=back
-=item crypt library
+=head1 CONFIGURE PERL ON CYGWIN
-http://miracle.geol.msu.ru/sos/ points to two different crypt
-libraries ported to cygwin. This has been tested with the libcrypt.tgz
-by Andy Piper. His home page can be found at
-http://www.xemacs.freeserve.co.uk/
+The default options gathered by Configure with the assistance of
+F<hints/cygwin.sh> will build a Perl that supports dynamic loading
+(which requires a shared F<libperl.dll>).
-=item hacks that should be revisited after the next cygwin release
+This will run Configure and keep a record:
-Some of the failures we encountered when running make test and/or perl harness
-are due to bugs in the cygwin b20.1 distribution. We sometimes found it
-necessary to use dirty little hacks to persuade make test and perl harness
-to play nicely. Since cygwin is in active development, many of these hacks
-may not be necessary in the future. These include:
+ ./Configure 2>&1 | tee log.configure
-=over
+If you are willing to accept all the defaults run Configure with B<-de>.
+However, several useful customizations are available.
-=item fix for pragma/locale
+=head2 Stripping Perl Binaries on Cygwin
-the line '#undef MB_CUR_MAX' was added to ex/POSIX/POSIX.xs. This fixes
-a failure in the pragma/locale.t test, which before this fix resulted in a
-coredump. It appears that MB_CUR_MAX is #defined __mb_cur_max, and __mb_cur_max
-is declared 'extern' in Cygwin b20.1's stdlib.c, but is never defined. Thus,
-the error.
+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
+binaries to be stripped, you can either add a B<-s> option when Configure
+prompts you,
-=item fix for lib/io_sock
+ Any additional ld flags (NOT including libraries)? [none] -s
+ Any special flags to pass to gcc to use dynamic linking? [none] -s
+ Any special flags to pass to ld2 to create a dynamically loaded library?
+ [none] -s
-there is a rather extensive patch to t/lib/io_sock.t which works around
-a failure related to fork() in the cygwin environment. Cygwin b20.1 does not
-properly remap manually loaded DLLs in the child after a fork.
+or you can edit F<hints/cygwin.sh> and uncomment the relevant variables
+near the end of the file.
-=item fix for lib/filehand
+=head2 Optional Libraries for Perl on Cygwin
-during the make test/perl harness steps, a win32 popup complains about
-a "perl.exe Application Error - illegal memory access." This is due to to
-a test in t/lib/filehand.t, and is related to the fork + dll problem.
+Several Perl functions and modules depend on the existence of
+some optional libraries. Configure will find them if they are
+installed in one of the directories listed as being used for library
+searches. Pre-built packages for most of these are available from
+the Cygwin installer.
-=item fix for environ
+=over 4
-there are a number of changes to miniperlmain.c, util.c, and mg.c that
-are there to work around a Cygwin problem relating to environ.
+=item * C<-lcrypt>
-=item fix for lib/posix
+The crypt package distributed with Cygwin is a Linux compatible 56-bit
+DES crypt port by Corinna Vinschen.
-the following line was added to t/lib/posix.t to work around a Cygwin bug.
+Alternatively, the crypt libraries in GNU libc have been ported to Cygwin.
-=begin text
+The DES based Ultra Fast Crypt port was done by Alexey Truhan:
-kill 'CONT', $$ if($^O =~ /cygwin/); # XXX: Cygwin bug INT signal gets stuck
+ ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/porters/Okhapkin_Sergey/cw32crypt-dist-0.tgz
-=end text
+NOTE: There are various export restrictions on DES implementations,
+see the glibc README for more details.
-=back
+The MD5 port was done by Andy Piper:
+
+ ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/porters/Okhapkin_Sergey/libcrypt.tgz
+
+=item * C<-lgdbm> (C<use GDBM_File>)
+
+GDBM is available for Cygwin.
+
+NOTE: The GDBM library only works on NTFS partitions.
+
+=item * C<-ldb> (C<use DB_File>)
+
+BerkeleyDB is available for Cygwin.
+
+NOTE: The BerkeleyDB library only completely works on NTFS partitions.
+
+=item * C<-lcygipc> (C<use IPC::SysV>)
+
+A port of SysV IPC is available for Cygwin.
+
+NOTE: This has B<not> been extensively tested. In particular,
+C<d_semctl_semun> is undefined because it fails a Configure test
+and on Win9x the I<shm*()> functions seem to hang. It also creates
+a compile time dependency because F<perl.h> includes F<<sys/ipc.h>>
+and F<<sys/sem.h>> (which will be required in the future when compiling
+CPAN modules). CURRENTLY NOT SUPPORTED!
+
+=item * C<-lutil>
+
+Included with the standard Cygwin netrelease is the inetutils package
+which includes libutil.a.
=back
-=head2 Configure
+=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
+these are experimental. You can either select an option when Configure
+prompts you or you can define (undefine) symbols on the command line.
+
+=over 4
+
+=item * C<-Uusedl>
+
+Undefining this symbol forces Perl to be compiled statically.
+
+=item * C<-Uusemymalloc>
+
+By default Perl uses the C<malloc()> included with the Perl source. If you
+want to force Perl to build with the system C<malloc()> undefine this symbol.
-Check hints/cygwin32.sh for any system specific settings. In
-particular change libpth to point to the correct location of
-...../i586-cygwin32/lib.
+=item * C<-Uuseperlio>
-run "sh Configure".
+Undefining this symbol disables the PerlIO abstraction. PerlIO is now the
+default; it is not recommended to disable PerlIO.
-When confronted with this prompt:
+=item * C<-Dusemultiplicity>
-=begin text
+Multiplicity is required when embedding Perl in a C program and using
+more than one interpreter instance. This works with the Cygwin port.
- First time through, eh? I have some defaults handy for the
- following systems:
- .
- .
- .
- Which of these apply, if any?
+=item * C<-Duse64bitint>
-=end text
+By default Perl uses 32 bit integers. If you want to use larger 64
+bit integers, define this symbol.
-select "cygwin32".
+=item * C<-Duselongdouble>
-Do not use the malloc that comes with perl--using the perl malloc
-collides with some cygwin startup routines.
+I<gcc> supports long doubles (12 bytes). However, several additional
+long double math functions are necessary to use them within Perl
+(I<{atan2, cos, exp, floor, fmod, frexp, isnan, log, modf, pow, sin, sqrt}l,
+strtold>).
+These are B<not> yet available with Cygwin.
-=head2 make
+=item * C<-Dusethreads>
-Run "make". If you're really feeling adventurous, type
-"make 2>&1 | tee make-log.txt".
+POSIX threads are implemented in Cygwin, define this symbol if you want
+a threaded perl.
-=over
+=item * C<-Duselargefiles>
-=item ld2
+Cygwin uses 64-bit integers for internal size and position calculations,
+this will be correctly detected and defined by Configure.
-The make script will install ld2 into your $installbin directory (i.e.
-wherever you said to put the perl.exe) during the *make* process. It
-does not wait until the *make install* process to install the ld2 script.
-This is because the remainder of the make refers to ld2 without fully
-specifying its path, and does this from multiple subdirectories (so ./ld2
-won't work.) The assumption here is that $installbin is in your current
-$PATH. If this is not the case, or if you do not have an install
-executable, the make will fail at some point. Don't panic. Just manually
-copy ld2 from the source directory to someplace in your path.
+=item * C<-Dmksymlinks>
-This cannot be done prior to make, because ld2 is created during the
-make process.
+Use this to build perl outside of the source tree. This works with Cygwin.
+Details can be found in the F<INSTALL> document. This is the recommended
+way to build perl from sources.
=back
-=head2 make test
+=head2 Suspicious Warnings on Cygwin
+
+You may see some messages during Configure that seem suspicious.
+
+=over 4
+
+=item * I<dlsym()>
+
+I<ld2> is needed to build dynamic libraries, but it does not exist
+when C<dlsym()> checking occurs (it is not created until C<make> runs).
+You will see the following message:
+
+ Checking whether your C<dlsym()> needs a leading underscore ...
+ ld2: not found
+ I can't compile and run the test program.
+ I'm guessing that dlsym doesn't need a leading underscore.
+
+Since the guess is correct, this is not a problem.
+
+=item * Win9x and C<d_eofnblk>
-Run "make test" to see how stable your system is. I (csw) got the
-following errors/warnings:
+Win9x does not correctly report C<EOF> with a non-blocking read on a
+closed pipe. You will see the following messages:
-=over
+ But it also returns -1 to signal EOF, so be careful!
+ WARNING: you can't distinguish between EOF and no data!
-=item op/taint
+ *** WHOA THERE!!! ***
+ The recommended value for $d_eofnblk on this machine was "define"!
+ Keep the recommended value? [y]
-Got two "missing cygwin1.dll" warning popups. This is because
-op/taint wants cygwin1.dll to be somewhere in the system path
-(\WINDOWS\SYSTEM, etc) or in the build directory. Can be ignored.
+At least for consistency with WinNT, you should keep the recommended
+value.
-=item lib/filehand
+=item * Compiler/Preprocessor defines
-Got an "Application Error - memory could not be read" popup. While
-this looks alarming, it can be ignored - just click OK. It is
-because Cygwin B20.1 doesn't properly remap manually loaded DLLs
-in the child after a fork.
+The following error occurs because of the Cygwin C<#define> of
+C<_LONG_DOUBLE>:
-=item lib/io_sock
+ Guessing which symbols your C compiler and preprocessor define...
+ try.c:<line#>: missing binary operator
-Got an "Application Error - memory could not be read" popup. Again,
-just click OK and ignore it.
+This failure does not seem to cause any problems. With older gcc
+versions, "parse error" is reported instead of "missing binary
+operator".
=back
-=head2 perl harness
+=head1 MAKE ON CYGWIN
-Once you've run make test, then cd into the t/ subdirectory and
-execute './perl harness'. I (csw) got the following results:
+Simply run I<make> and wait:
-=over
+ make 2>&1 | tee log.make
-=item op/taint
+=head2 Errors on Cygwin
-Got four "missing cygwin1.dll" warning popups. Click OK and
-ignore.
+Errors like these are normal:
-=item lib/filehand
+ ...
+ make: [extra.pods] Error 1 (ignored)
+ ...
+ make: [extras.make] Error 1 (ignored)
-Got an "Application Error - memory could not be read" popup. Again,
-click OK and ignore.
+=head2 ld2 on Cygwin
-=item lib/io_sock
+During C<make>, I<ld2> will be created and installed in your $installbin
+directory (where you said to put public executables). It does not
+wait until the C<make install> process to install the I<ld2> script,
+this is because the remainder of the C<make> refers to I<ld2> without
+fully specifying its path and does this from multiple subdirectories.
+The assumption is that $installbin is in your current C<PATH>. If this
+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>.
-Got an "Application Error - memory could not be read" popup. Again,
-clock OK and ignore.
+=head1 TEST ON CYGWIN
-=item final results
+There are two steps to running the test suite:
-After the ./perl harness, I got the following results summary.
+ make test 2>&1 | tee log.make-test
- Failed Test Status Wstat Total Fail Failed List of failed
- -------------------------------------------------------------------------------
- op/taint.t 149 3 2.01% 1, 3, 31
- 9 tests skipped, plus 35 subtests skipped.
- Failed 1/190 test scripts, 99.47% okay. 3/6452 subtests failed, 99.95% okay.
+ cd t;./perl harness 2>&1 | tee ../log.harness
-=back
+The same tests are run both times, but more information is provided when
+running as C<./perl harness>.
-=head2 make install
+Test results vary depending on your host system and your Cygwin
+configuration. If a test can pass in some Cygwin setup, it is always
+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.
-Finally, run "make install". In my case, the install process was unable
-to copy the files from <SRCDIR>/pod/* to /usr/local/lib/perl5/5.00503/pod/.
-I (csw) just copied them by hand after the install finished. I believe
-this is because I'm using Sergey Okhapkin's coolview version of the
-cygwin1.dll, which provides case sensitivity. The directory is created
-as "/usr/local/lib/perl5/5.00503/Pod" but the copy is done into
-"/usr/local/lib/perl5/5.00503/pod". This fails -- but probably won't
-fail if you're using the default cygwin1.dll.
+=head2 File Permissions on Cygwin
-=head1 BUGS
+UNIX file permissions are based on sets of mode bits for
+{read,write,execute} for each {user,group,other}. By default Cygwin
+only tracks the Win32 read-only attribute represented as the UNIX file
+user write bit (files are always readable, files are executable if they
+have a F<.{com,bat,exe}> extension or begin with C<#!>, directories are
+always readable and executable). On WinNT with the I<ntea> C<CYGWIN>
+setting, the additional mode bits are stored as extended file attributes.
+On WinNT with the I<ntsec> C<CYGWIN> setting, permissions use the standard
+WinNT security descriptors and access control lists. Without one of
+these options, these tests will fail (listing not updated yet):
-A lot of warnings about incompatible pointer types and comparison
-lacking a cast. This is because of __declspec(dllimport).
+ Failed Test List of failed
+ ------------------------------------
+ io/fs.t 5, 7, 9-10
+ lib/anydbm.t 2
+ lib/db-btree.t 20
+ lib/db-hash.t 16
+ lib/db-recno.t 18
+ lib/gdbm.t 2
+ lib/ndbm.t 2
+ lib/odbm.t 2
+ lib/sdbm.t 2
+ op/stat.t 9, 20 (.tmp not an executable extension)
-Upon each start, make warns that a rule for perlmain.o is overrided.
-Yes, it is. In order to use libperl.dll, perlmain needs to import
-symbols from there. According to alex smishlajev, there seems to be
-no better solution than adding an explicit define to the rule.
+=head2 NDBM_File and ODBM_File do not work on FAT filesystems
-make clean does not remove library .def and .exe.core files.
+Do not use NDBM_File or ODBM_File on FAT filesystem. They can be
+built on a FAT filesystem, but many tests will fail:
-ld2 script is installed with reference to source directory. You should
-change this to /usr/local/bin (or whatever) after install.
+ ../ext/NDBM_File/ndbm.t 13 3328 71 59 83.10% 1-2 4 16-71
+ ../ext/ODBM_File/odbm.t 255 65280 ?? ?? % ??
+ ../lib/AnyDBM_File.t 2 512 12 2 16.67% 1 4
+ ../lib/Memoize/t/errors.t 0 139 11 5 45.45% 7-11
+ ../lib/Memoize/t/tie_ndbm.t 13 3328 4 4 100.00% 1-4
+ run/fresh_perl.t 97 1 1.03% 91
-.bat wrappers for installed utility scripts are not made during installation.
+If you intend to run only on FAT (or if using AnyDBM_File on FAT),
+run Configure with the -Ui_ndbm and -Ui_dbm options to prevent
+NDBM_File and ODBM_File being built.
-=head1 AUTHOR
+With NTFS (and CYGWIN=ntsec), there should be no problems even if
+perl was built on FAT.
-alexander smishlajev <als@turnhere.com>
+=head2 C<fork()> failures in io_* tests
-=head1 DISCLAIMER
+A C<fork()> failure may result in the following tests failing:
-I (alex) am not going to maintain this document or this port. I only wanted
-to make perl porting a bit easier. If failed, I can't be helpful for you.
-Contact one of the others listed in the history section.
+ ext/IO/lib/IO/t/io_multihomed.t
+ ext/IO/lib/IO/t/io_sock.t
+ ext/IO/lib/IO/t/io_unix.t
-=head1 HISTORY
+See comment on fork in L<Miscellaneous> below.
-=over
+=head1 Specific features of the Cygwin port
-=item Release 1.4.1: 28-May-1999
+=head2 Script Portability on Cygwin
-Charles Wilson - cwilson@ece.gatech.edu
+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
+some differences that you should know about. This is a very brief guide
+to portability, more information can be found in the Cygwin documentation.
- Configure minor fix for spaces in $PATH
- documentation updates
+=over 4
-=item Release 1.4: 26-May-1999
+=item * Pathnames
-Charles Wilson - cwilson@ece.gatech.edu
+Cygwin pathnames can be separated by forward (F</>) or backward (F<\\>)
+slashes. They may also begin with drive letters (F<C:>) or Universal
+Naming Codes (F<//UNC>). DOS device names (F<aux>, F<con>, F<prn>,
+F<com*>, F<lpt?>, F<nul>) are invalid as base filenames. However, they
+can be used in extensions (e.g., F<hello.aux>). Names may contain all
+printable characters except these:
- From Eric Fifer:
- hints/cygwin32.sh -L. and --export-dynamic not needed
- cygwin32/Makefile.SHs no value needed for -DUSEIMPORTLIB
- t/lib/io_sock.t -I../lib so "make test" works
- t/lib/posix.t workaround a Cygwin bug so test works
- doio.c/perl.h cleanup gcc warning "doio.c:789: warning:
- pointer/integer type mismatch in
- conditional expression"
- From Charles Wilson:
- Configure changes to findhdr script
- documentation updates
- built binary kit for release
+ : * ? " < > |
-=item Release 1.3: 26-May-1999
+File names are case insensitive, but case preserving. A pathname that
+contains a backslash or drive letter is a Win32 pathname (and not subject
+to the translations applied to POSIX style pathnames).
-Charles Wilson - cwilson@ece.gatech.edu
+=item * Text/Binary
- Changes to Cwd.pm to correct lib/findbin.t test failure from Eric Fifer
- Changes to t/op/magic.t to correct a test failure from Eric Fifer
- Changes to miniperlmain.c, util.c, and mg.c to correct t/op/magic.t #29
- test failure, from Eric Fifer
- more documentatino updates, patch merging, and a change to
- cygwin/Makefile.SHs -- cw.
- 99.95% okay!!!
+When a file is opened it is in either text or binary mode. In text mode
+a file is subject to CR/LF/Ctrl-Z translations. With Cygwin, the default
+mode for an C<open()> is determined by the mode of the mount that underlies
+the file. Perl provides a C<binmode()> function to set binary mode on files
+that otherwise would be treated as text. C<sysopen()> with the C<O_TEXT>
+flag sets text mode on files that otherwise would be treated as binary:
-=item Release 1.2: 25-May-1999
+ sysopen(FOO, "bar", O_WRONLY|O_CREAT|O_TEXT)
-Charles Wilson - cwilson@ece.gatech.edu
+C<lseek()>, C<tell()> and C<sysseek()> only work with files opened in binary
+mode.
- fixes for lib/io_sock and pragma/locale from Eric Fifer
- fixes for Configure, Makefile.SH, and cygwin32/Makefile.SHs from
- alex smishlajev
- documentation updates, and other fixes to the fixes from cw.
- 99.91% okay!!!
+The text/binary issue is covered at length in the Cygwin documentation.
-=item Release 1.1: 21-May-1999
+=item * PerlIO
-Charles Wilson - cwilson@ece.gatech.edu
+PerlIO overrides the default Cygwin Text/Binary behaviour. A file will
+always treated as binary, regardless which mode of the mount it lives on,
+just like it is in UNIX. So CR/LF translation needs to be requested in
+either the C<open()> call like this:
-minor change to Configure script, reversed a few changes made by
-alexander's patch (made DOSISH #undefined again) and moved code
-by alexander from dosish.h to perl.h. Reversed a change in
-pp_hot.c
+ open(FH, ">:crlf", "out.txt");
-=item Release 1.0: 16-May-1999
+which will do conversion from LF to CR/LF on the output, or in the
+environment settings (add this to your .bashrc):
-Charles Wilson - cwilson@ece.gatech.edu
+ export PERLIO=crlf
-Merged alexander's patch and Eric's patch into a single
-monolithic patch. Minor cleanup. Built binary for distribution.
-perl5.005_03-dynamic-patch-v1.0
+which will pull in the crlf PerlIO layer which does LF -> CRLF conversion
+on every output generated by perl.
-=item Pre-release 3: 12-May-1999
+=item * F<.exe>
-Eric Fifer - efifer@sanwaint.com
+The Cygwin C<stat()>, C<lstat()> and C<readlink()> functions make the F<.exe>
+extension transparent by looking for F<foo.exe> when you ask for F<foo>
+(unless a F<foo> also exists). Cygwin does not require a F<.exe>
+extension, but I<gcc> adds it automatically when building a program.
+However, when accessing an executable as a normal file (e.g., I<cp>
+in a makefile) the F<.exe> is not transparent. The I<install> included
+with Cygwin automatically appends a F<.exe> when necessary.
-Removed all references to the impure_ptr hack since it is no longer
-needed. Some minor cleanup of alexander smishlajev's work and a few
-bug fixes.
+=item * cygwin vs. windows process ids
-=item Pre-release 2 (initial dynamic build): 17..25-apr-1999
+Cygwin processes have their own pid, which is different from the
+underlying windows pid. Most posix compliant Proc functions expect
+the cygwin pid, but several Win32::Process functions expect the
+winpid. E.g. C<$$> is the cygwin pid of F</usr/bin/perl>, which is not
+the winpid. Use C<Cygwin::winpid_to_pid()> and C<Cygwin::winpid_to_pid()>
+to translate between them.
-alexander smishlajev - als@turnher.com
+=item * C<chown()>
-perl 5.005_03. cygwin b20.1 egcs 1.1.2. far 1.60. nescafe classic.
+On WinNT C<chown()> can change a file's user and group IDs. On Win9x C<chown()>
+is a no-op, although this is appropriate since there is no security model.
-=item Pre-release 1 (static build): 5-Mar-1999
+=item * Miscellaneous
-Charles Wilson - cwilson@ece.gatech.edu
+File locking using the C<F_GETLK> command to C<fcntl()> is a stub that
+returns C<ENOSYS>.
-Collected various patches that had been floating around the net, along
-with build instructions. Original authorship credit for those patches
-goes to:
+Win9x can not C<rename()> an open file (although WinNT can).
- Steven Morlock - newspost@morlock.net
- Sebastien Barre - Sebastien.Barre@utc.fr
- Teun Burgers - burgers@ecn.nl
+The Cygwin C<chroot()> implementation has holes (it can not restrict file
+access by native Win32 programs).
-Created a monolithic patchkit (perl5.005_03-static-patch) and build
-instructions for cygwin (beta 20.1). Also created a binary distribution
-of the resulting static perl build.
+Inplace editing C<perl -i> of files doesn't work without doing a backup
+of the file being edited C<perl -i.bak> because of windowish restrictions,
+therefore Perl adds the suffix C<.bak> automatically if you use C<perl -i>
+without specifying a backup extension.
-=back
+Using C<fork()> after loading multiple dlls may fail with an internal cygwin
+error like the following:
-=head1 APPENDIX
+ C:\CYGWIN\BIN\PERL.EXE: *** couldn't allocate memory 0x10000(4128768) for 'C:\CYGWIN\LIB\PERL5\5.6.1\CYGWIN-MULTI\AUTO\SOCKET\SOCKET.DLL' alignment, Win32 error 8
-Perl harness results from Eric Fifer, under various environments. The same
-executable was used in all cases. The last item is a different executable
-on a different machine, built by Charles Wilson.
+ 200 [main] perl 377147 sync_with_child: child -395691(0xB8) died before initialization with status code 0x1
+ 1370 [main] perl 377147 sync_with_child: *** child state child loading dlls
-There are a number of very good questions one could ask about anomalies
-in the test results presented below. "Why do the last two show different
-results?" "Why did op/stat.t #18 pass in the first two tests and fail in
-the third?" Short answer: I don't know. Long answer: I really have no
-idea.
+Use the rebase utility to resolve the conflicting dll addresses. The
+rebase package is included in the Cygwin netrelease. Use setup.exe from
+F<http://www.cygwin.com/setup.exe> to install it and run rebaseall.
-=over
+=back
-=item text mounts, no 'ntea'
+=head2 Prebuilt methods:
- Failed Test Status Wstat Total Fail Failed List of failed
- ------------------------------------------------------------
- lib/anydbm.t 2 512 12 8 66.67% 5-12
- lib/sdbm.t 2 512 18 15 83.33% 2, 5-18
- op/split.t 25 1 4.00% 11
- op/stat.t 58 3 5.17% 9, 19, 26
- op/taint.t 149 3 2.01% 1, 3, 31
+=over 4
-=item binary mounts, no 'ntea'
+=item C<Cwd::cwd>
- Failed Test Status Wstat Total Fail Failed List of failed
- ------------------------------------------------------------
- lib/sdbm.t 18 1 5.56% 2
- op/stat.t 58 3 5.17% 9, 19, 26
- op/taint.t 149 3 2.01% 1, 3, 31
+Returns current working directory.
-=item binary mounts, 'ntea'
+=item C<Cygwin::pid_to_winpid>
- Failed Test Status Wstat Total Fail Failed List of failed
- ------------------------------------------------------------
- op/stat.t 58 3 5.17% 18-19, 26
- op/taint.t 149 3 2.01% 1, 3, 31
+Translates a cygwin pid to the corresponding Windows pid (which may or
+may not be the same).
-=item binary mounts, ntea (csw build)
+=item C<Cygwin::winpid_to_pid>
+
+Translates a Windows pid to the corresponding cygwin pid (if any).
+
+=back
- Failed Test Status Wstat Total Fail Failed List of failed
- -------------------------------------------------------------------------------
- op/taint.t 149 3 2.01% 1, 3, 31
+=head1 INSTALL PERL ON CYGWIN
+
+This will install Perl, including I<man> pages.
+
+ make install 2>&1 | tee log.make-install
+
+NOTE: If C<STDERR> is redirected C<make install> will B<not> prompt
+you to install I<perl> into F</usr/bin>.
+
+You may need to be I<Administrator> to run C<make install>. If you
+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 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
+code. Hopefully, keeping this up to date will allow the Cygwin port to
+be kept as clean as possible (listing not updated yet).
+
+=over 4
+
+=item Documentation
+
+ INSTALL README.cygwin README.win32 MANIFEST
+ Changes Changes5.005 Changes5.004 Changes5.6
+ pod/perl.pod pod/perlport.pod pod/perlfaq3.pod
+ pod/perldelta.pod pod/perl5004delta.pod pod/perl56delta.pod
+ pod/perlhist.pod pod/perlmodlib.pod perl/buildtoc pod/perltoc.pod
+
+=item Build, Configure, Make, Install
+
+ cygwin/Makefile.SHs
+ cygwin/ld2.in
+ cygwin/perlld.in
+ ext/IPC/SysV/hints/cygwin.pl
+ ext/NDBM_File/hints/cygwin.pl
+ ext/ODBM_File/hints/cygwin.pl
+ hints/cygwin.sh
+ Configure - help finding hints from uname,
+ shared libperl required for dynamic loading
+ Makefile.SH - linklibperl
+ Porting/patchls - cygwin in port list
+ installman - man pages with :: translated to .
+ installperl - install dll/ld2/perlld, install to pods
+ makedepend.SH - uwinfix
+
+=item Tests
+
+ t/io/tell.t - binmode
+ t/lib/b.t - ignore Cwd from os_extras
+ t/lib/glob-basic.t - Win32 directory list access differs from read mode
+ t/op/magic.t - $^X/symlink WORKAROUND, s/.exe//
+ t/op/stat.t - no /dev, skip Win32 ftCreationTime quirk
+ (cache manager sometimes preserves ctime of file
+ previously created and deleted), no -u (setuid)
+ t/lib/cygwin.t - builtin cygwin function tests
+
+=item Compiled Perl Source
+
+ EXTERN.h - __declspec(dllimport)
+ XSUB.h - __declspec(dllexport)
+ cygwin/cygwin.c - os_extras (getcwd, spawn, Cygwin::winpid_to_pid,
+ Cygwin::pid_to_winpid)
+ perl.c - os_extras
+ perl.h - binmode
+ doio.c - win9x can not rename a file when it is open
+ pp_sys.c - do not define h_errno, pp_system with spawn
+ util.c - use setenv
+
+=item Compiled Module Source
+
+ ext/POSIX/POSIX.xs - tzname defined externally
+ ext/SDBM_File/sdbm/pair.c
+ - EXTCONST needs to be redefined from EXTERN.h
+ ext/SDBM_File/sdbm/sdbm.c
+ - binary open
+
+=item Perl Modules/Scripts
+
+ lib/Cwd.pm - hook to internal Cwd::cwd
+ lib/ExtUtils/MakeMaker.pm
+ - require MM_Cygwin.pm
+ lib/ExtUtils/MM_Cygwin.pm
+ - canonpath, cflags, manifypods, perl_archive
+ lib/File/Find.pm - on remote drives stat() always sets st_nlink to 1
+ lib/File/Spec/Unix.pm - preserve //unc
+ lib/File/Temp.pm - no directory sticky bit
+ lib/perl5db.pl - use stdin not /dev/tty
+ utils/perldoc.PL - version comment
=back
-=cut
+=head1 BUGS ON CYGWIN
+
+Support for swapping real and effective user and group IDs is incomplete.
+On WinNT Cygwin provides C<setuid()>, C<seteuid()>, C<setgid()> and C<setegid()>.
+However, additional Cygwin calls for manipulating WinNT access tokens
+and security contexts are required.
+
+=head1 AUTHORS
+
+Charles Wilson <cwilson@ece.gatech.edu>,
+Eric Fifer <egf7@columbia.edu>,
+alexander smishlajev <als@turnhere.com>,
+Steven Morlock <newspost@morlock.net>,
+Sebastien Barre <Sebastien.Barre@utc.fr>,
+Teun Burgers <burgers@ecn.nl>,
+Gerrit P. Haase <gp@familiehaase.de>.
+
+=head1 HISTORY
+
+Last updated: 2005-02-11