X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/2c2d71f566f0a758d1486480f45158c0e70ea496..9393ace2f22338dd25b6a689e53031fa2599038f:/README.cygwin?ds=sidebyside diff --git a/README.cygwin b/README.cygwin index fb93ac5..796197a 100644 --- a/README.cygwin +++ b/README.cygwin @@ -4,502 +4,512 @@ specially designed to be readable as is. =head1 NAME -README.cygwin - notes about porting Perl to Cygwin +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 Cygwin +B 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 cygwin 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: -=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 are B 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 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 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 ('Bthers') will -never be allowed write access, but owner ('Bser') and Broup B -be allowed write access. Everybody (u, g, and o) Bbe allowed -read access. - -In any case, Corinna Vinschen's ntsec patches B 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 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... + http://www.cygwin.com/ -=back +A recent net or commercial release of Cygwin is required. -=item crypt library +At the time this document was last updated, Cygwin 1.3.9 was current. -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/ -=item hacks that should be revisited after the next cygwin release +=head2 Cygwin Configuration -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: +While building Perl some changes may be necessary to your Cygwin setup so +that Perl builds cleanly. These changes are B required for normal +Perl usage. -=over +B 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, I, binary/text mounts). +The only dependencies come from hard-coded pathnames like C. +However, your host system and Cygwin configuration will affect Perl's +runtime behavior (see L). -=item fix for pragma/locale +=over 4 -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. +=item * C -=item fix for lib/io_sock +Set the C 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. -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. +=item * I -=item fix for lib/filehand +If you do not have I (which is part of the I package), +Configure will B prompt you to install I pages. -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. +=item * Permissions -=item fix for environ +On WinNT with either the I or I C 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' on the entire Perl source tree. -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. +Also, it is a well known WinNT "feature" that files created by a login +that is a member of the I group will be owned by the +I 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 C setting, this is not an +issue because it "corrects" the ownership to what you would expect on +a UNIX system. -=item fix for lib/posix +=back -the following line was added to t/lib/posix.t to work around a Cygwin bug. +=head1 CONFIGURE PERL ON CYGWIN -=begin text +The default options gathered by Configure with the assistance of +F will build a Perl that supports dynamic loading +(which requires a shared F). -kill 'CONT', $$ if($^O =~ /cygwin/); # XXX: Cygwin bug INT signal gets stuck +This will run Configure and keep a record: -=end text + ./Configure 2>&1 | tee log.configure -=back +If you are willing to accept all the defaults run Configure with B<-de>. +However, several useful customizations are available. -=back +=head2 Stripping Perl Binaries on Cygwin -=head2 Configure +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, -Check hints/cygwin.sh for any system specific settings. In -particular change libpth to point to the correct location of -...../i586-cygwin32/lib. + 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 -run "sh Configure". +or you can edit F and uncomment the relevant variables +near the end of the file. -When confronted with this prompt: +=head2 Optional Libraries for Perl on Cygwin -=begin text +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. - First time through, eh? I have some defaults handy for the - following systems: - . - . - . - Which of these apply, if any? +=over 4 -=end text +=item * C<-lcrypt> -select "cygwin". +The crypt package distributed with Cygwin is a Linux compatible 56-bit +DES crypt port by Corinna Vinschen. -Do not use the malloc that comes with perl--using the perl malloc -collides with some cygwin startup routines. +Alternatively, the crypt libraries in GNU libc have been ported to Cygwin. -=head2 make +The DES based Ultra Fast Crypt port was done by Alexey Truhan: -Run "make". If you're really feeling adventurous, type -"make 2>&1 | tee make-log.txt". + ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/porters/Okhapkin_Sergey/cw32crypt-dist-0.tgz -=over +NOTE: There are various export restrictions on DES implementations, +see the glibc README for more details. -=item ld2 +The MD5 port was done by Andy Piper: -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. + ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/porters/Okhapkin_Sergey/libcrypt.tgz -This cannot be done prior to make, because ld2 is created during the -make process. +=item * C<-lgdbm> (C) -=back +GDBM is available for Cygwin. -=head2 make test +=item * C<-ldb> (C) -Run "make test" to see how stable your system is. I (csw) got the -following errors/warnings: +BerkeleyDB is available for Cygwin. Some details can be found in +F. -=over +NOTE: The BerkeleyDB library only completely works on NTFS partitions. -=item op/taint +=item * C<-lcygipc> (C) -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. +A port of SysV IPC is available for Cygwin. -=item lib/filehand +NOTE: This has B been extensively tested. In particular, +C is undefined because it fails a Configure test +and on Win9x the I functions seem to hang. It also creates +a compile time dependency because F includes F<> +and F<> (which will be required in the future when compiling +CPAN modules). -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. +=back -=item lib/io_sock +=head2 Configure-time Options for Perl on Cygwin -Got an "Application Error - memory could not be read" popup. Again, -just click OK and ignore it. +The F 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. -=back +=over 4 + +=item * C<-Uusedl> + +Undefining this symbol forces Perl to be compiled statically. + +=item * C<-Uusemymalloc> + +By default Perl uses the malloc() included with the Perl source. If you +want to force Perl to build with the system malloc() undefine this symbol. + +=item * C<-Uuseperlio> -=head2 perl harness +Undefining this symbol disables the PerlIO abstraction, which is now the +default. -Once you've run make test, then cd into the t/ subdirectory and -execute './perl harness'. I (csw) got the following results: +=item * C<-Dusemultiplicity> -=over +Multiplicity is required when embedding Perl in a C program and using +more than one interpreter instance. This works with the Cygwin port. -=item op/taint +=item * C<-Duse64bitint> -Got four "missing cygwin1.dll" warning popups. Click OK and -ignore. +By default Perl uses 32 bit integers. If you want to use larger 64 +bit integers, define this symbol. If there is trouble, check that +your Cygwin installation is up to date. -=item lib/filehand +=item * C<-Duselongdouble> -Got an "Application Error - memory could not be read" popup. Again, -click OK and ignore. +I 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 yet available with Cygwin. -=item lib/io_sock +=item * C<-Dusethreads> -Got an "Application Error - memory could not be read" popup. Again, -clock OK and ignore. +POSIX threads are B yet implemented in Cygwin completely. -=item final results +=item * C<-Duselargefiles> -After the ./perl harness, I got the following results summary. +Although Win32 supports large files, Cygwin currently uses 32-bit integers +for internal size and position calculations. - 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. +=item * C<-Dmksymlinks> + +Use this to build perl outside of the source tree. This works with Cygwin. +Details can be found in the F document. =back -=head2 make install +=head2 Suspicious Warnings on Cygwin -Finally, run "make install". In my case, the install process was unable -to copy the files from /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. +You may see some messages during Configure that seem suspicious. -=head1 BUGS +=over 4 -A lot of warnings about incompatible pointer types and comparison -lacking a cast. This is because of __declspec(dllimport). +=item * I -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. +I is needed to build dynamic libraries, but it does not exist +when dlsym() checking occurs (it is not created until `C' runs). +You will see the following message: -make clean does not remove library .def and .exe.core files. + Checking whether your 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. -ld2 script is installed with reference to source directory. You should -change this to /usr/local/bin (or whatever) after install. +Since the guess is correct, this is not a problem. -.bat wrappers for installed utility scripts are not made during installation. +=item * Win9x and C -=head1 AUTHOR +Win9x does not correctly report C with a non-blocking read on a +closed pipe. You will see the following messages: -alexander smishlajev + But it also returns -1 to signal EOF, so be careful! + WARNING: you can't distinguish between EOF and no data! -=head1 DISCLAIMER + *** WHOA THERE!!! *** + The recommended value for $d_eofnblk on this machine was "define"! + Keep the recommended value? [y] -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. +At least for consistency with WinNT, you should keep the recommended +value. -=head1 HISTORY +=item * Compiler/Preprocessor defines -=over +The following error occurs because of the Cygwin C<#define> of +C<_LONG_DOUBLE>: -=item Release 1.4.1: 28-May-1999 + Guessing which symbols your C compiler and preprocessor define... + try.c:: parse error -Charles Wilson - cwilson@ece.gatech.edu +This failure does not seem to cause any problems. - Configure minor fix for spaces in $PATH - documentation updates +=back -=item Release 1.4: 26-May-1999 +=head1 MAKE ON CYGWIN -Charles Wilson - cwilson@ece.gatech.edu +Simply run I and wait: - 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 + make 2>&1 | tee log.make -=item Release 1.3: 26-May-1999 +=head2 Warnings on Cygwin -Charles Wilson - cwilson@ece.gatech.edu +Warnings like these are normal: - 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!!! + warning: overriding commands for target + warning: ignoring old commands for target -=item Release 1.2: 25-May-1999 + dllwrap: no export definition file provided + dllwrap: creating one, but that may not be what you want -Charles Wilson - cwilson@ece.gatech.edu +=head2 ld2 on Cygwin - 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!!! +During `C', I will be created and installed in your $installbin +directory (where you said to put public executables). It does not +wait until the `C' process to install the I script, +this is because the remainder of the `C' refers to I without +fully specifying its path and does this from multiple subdirectories. +The assumption is that $installbin is in your current C. If this +is not the case `C' will fail at some point. If this happens, +just manually copy I from the source directory to somewhere in +your C. -=item Release 1.1: 21-May-1999 +=head1 TEST ON CYGWIN -Charles Wilson - cwilson@ece.gatech.edu +There are two steps to running the test suite: -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 + make test 2>&1 | tee log.make-test -=item Release 1.0: 16-May-1999 + cd t;./perl harness 2>&1 | tee ../log.harness -Charles Wilson - cwilson@ece.gatech.edu +The same tests are run both times, but more information is provided when +running as `C<./perl harness>'. -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 +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. -=item Pre-release 3: 12-May-1999 +=head2 File Permissions on Cygwin -Eric Fifer - efifer@sanwaint.com +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 C +setting, the additional mode bits are stored as extended file attributes. +On WinNT with the I C setting, permissions use the standard +WinNT security descriptors and access control lists. Without one of +these options, these tests will fail: -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. + 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) -=item Pre-release 2 (initial dynamic build): 17..25-apr-1999 +=head2 Script Portability on Cygwin -alexander smishlajev - als@turnher.com +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. -perl 5.005_03. cygwin b20.1 egcs 1.1.2. far 1.60. nescafe classic. +=over 4 -=item Pre-release 1 (static build): 5-Mar-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) or Universal +Naming Codes (F). DOS device names (F, F, F, +F, F, F) are invalid as base filenames. However, they +can be used in extensions (e.g., F). Names may contain all +printable characters except these: -Collected various patches that had been floating around the net, along -with build instructions. Original authorship credit for those patches -goes to: + : * ? " < > | - Steven Morlock - newspost@morlock.net - Sebastien Barre - Sebastien.Barre@utc.fr - Teun Burgers - burgers@ecn.nl +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). -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. +=item * Text/Binary -=back +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 open() is determined by the mode of the mount that underlies +the file. Perl provides a binmode() function to set binary mode on files +that otherwise would be treated as text. sysopen() with the C +flag sets text mode on files that otherwise would be treated as binary: -=head1 APPENDIX + sysopen(FOO, "bar", O_WRONLY|O_CREAT|O_TEXT) -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. +lseek(), tell() and sysseek() only work with files opened in binary mode. -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. +The text/binary issue is covered at length in the Cygwin documentation. -=over +=item * F<.exe> -=item text mounts, no 'ntea' +The Cygwin stat(), lstat() and readlink() functions make the F<.exe> +extension transparent by looking for F when you ask for F +(unless a F also exists). Cygwin does not require a F<.exe> +extension, but I adds it automatically when building a program. +However, when accessing an executable as a normal file (e.g., I +in a makefile) the F<.exe> is not transparent. The I included +with Cygwin automatically appends a F<.exe> when necessary. - 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 +=item * chown() -=item binary mounts, no 'ntea' +On WinNT chown() can change a file's user and group IDs. On Win9x chown() +is a no-op, although this is appropriate since there is no security model. - 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 +=item * Miscellaneous -=item binary mounts, 'ntea' +File locking using the C command to fcntl() is a stub that +returns C. - 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 +Win9x can not rename() an open file (although WinNT can). -=item binary mounts, ntea (csw build) +The Cygwin chroot() implementation has holes (it can not restrict file +access by native Win32 programs). - Failed Test Status Wstat Total Fail Failed List of failed - ------------------------------------------------------------------------------- - op/taint.t 149 3 2.01% 1, 3, 31 +=back + +=head1 INSTALL PERL ON CYGWIN + +This will install Perl, including I pages. + + make install 2>&1 | tee log.make-install + +NOTE: If C is redirected `C' will B prompt +you to install I into F. + +You may need to be I to run `C'. 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 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. + +=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 pod/buildtoc.PL 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) + +=item Compiled Perl Source + + EXTERN.h - __declspec(dllimport) + XSUB.h - __declspec(dllexport) + cygwin/cygwin.c - os_extras (getcwd, spawn) + 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 + +When I starts, it warns about overriding commands for F. + +Support for swapping real and effective user and group IDs is incomplete. +On WinNT Cygwin provides setuid(), seteuid(), setgid() and setegid(). +However, additional Cygwin calls for manipulating WinNT access tokens +and security contexts are required. + +=head1 AUTHORS + +Charles Wilson , +Eric Fifer , +alexander smishlajev , +Steven Morlock , +Sebastien Barre , +Teun Burgers , +Gerrit Haase . + +=head1 HISTORY + +Last updated: 2002-02-27