X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/270085805fa918837f9a23b71589ce94ac7477d6..ce3ac4b622fa47e8694929bdb9f342a59186d677:/README.cygwin diff --git a/README.cygwin b/README.cygwin index b1406c3..8940ca6 100644 --- a/README.cygwin +++ b/README.cygwin @@ -31,7 +31,7 @@ about this project can be found at: A recent net or commercial release of Cygwin is required. -At the time this document was last updated, Cygwin 1.3.12 was current. +At the time this document was last updated, Cygwin 1.5.2 was current. =head2 Cygwin Configuration @@ -64,8 +64,8 @@ Configure will B prompt you to install I pages. 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. +creates directories and files, to be safe you may want to run a +C 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 group will be owned by the @@ -137,10 +137,11 @@ The MD5 port was done by Andy Piper: GDBM is available for Cygwin. +NOTE: The GDBM library only works on NTFS partitions. + =item * C<-ldb> (C) -BerkeleyDB is available for Cygwin. Some details can be found in -F. +BerkeleyDB is available for Cygwin. NOTE: The BerkeleyDB library only completely works on NTFS partitions. @@ -153,7 +154,7 @@ 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). NO LONGER SUPPORTED! +CPAN modules). CURRENTLY NOT SUPPORTED! =item * C<-lutil> @@ -177,13 +178,13 @@ 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. +By default Perl uses the C included with the Perl source. If you +want to force Perl to build with the system C undefine this symbol. =item * C<-Uuseperlio> -Undefining this symbol disables the PerlIO abstraction, which is now the -default. +Undefining this symbol disables the PerlIO abstraction. PerlIO is now the +default; it is not recommended to disable PerlIO. =item * C<-Dusemultiplicity> @@ -193,8 +194,7 @@ more than one interpreter instance. This works with the Cygwin port. =item * C<-Duse64bitint> 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. +bit integers, define this symbol. =item * C<-Duselongdouble> @@ -207,18 +207,18 @@ These are B yet available with Cygwin. =item * C<-Dusethreads> POSIX threads are implemented in Cygwin, define this symbol if you want -a threaded perl. If there is trouble, check that your Cygwin installation -is up to date. +a threaded perl. =item * C<-Duselargefiles> -Although Win32 supports large files, Cygwin currently uses 32-bit integers -for internal size and position calculations. +Cygwin uses 64-bit integers for internal size and position calculations, +this will be correctly detected and defined by Configure. =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. +Details can be found in the F document. This is the recommended +way to build perl from sources. =back @@ -231,10 +231,10 @@ You may see some messages during Configure that seem suspicious. =item * I I is needed to build dynamic libraries, but it does not exist -when dlsym() checking occurs (it is not created until `C' runs). +when C checking occurs (it is not created until C runs). You will see the following message: - Checking whether your dlsym() needs a leading underscore ... + Checking whether your C 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. @@ -276,18 +276,10 @@ Simply run I and wait: make 2>&1 | tee log.make -=head2 Warnings on Cygwin +=head2 Errors on Cygwin -Warnings like these are normal: +Errors like these are normal: - perl.c: In function `S_parse_body': - perl.c:1468: warning: implicit declaration of function `init_os_extras' - ... - pp_sys.c:289: warning: `S_emulate_eaccess' defined but not used - ... - perlio.c: In function `perlsio_binmode': - perlio.c:98: warning: implicit declaration of function `setmode' - perlio.c:98: warning: passing arg 1 of `Perl_PerlIO_fileno' from incompatible pointer type ... make: [extra.pods] Error 1 (ignored) ... @@ -295,13 +287,13 @@ Warnings like these are normal: =head2 ld2 on Cygwin -During `C', I will be created and installed in your $installbin +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 +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, +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. @@ -314,7 +306,7 @@ There are two steps to running the test suite: cd t;./perl harness 2>&1 | tee ../log.harness The same tests are run both times, but more information is provided when -running as `C<./perl harness>'. +running as C<./perl harness>. Test results vary depending on your host system and your Cygwin configuration. If a test can pass in some Cygwin setup, it is always @@ -367,9 +359,9 @@ NDBM_File and ODBM_File being built. With NTFS (and CYGWIN=ntsec), there should be no problems even if perl was built on FAT. -=head2 fork() failures in io_* tests +=head2 C failures in io_* tests -A fork() failure may result in the following tests failing: +A C failure may result in the following tests failing: ext/IO/lib/IO/t/io_multihomed.t ext/IO/lib/IO/t/io_sock.t @@ -377,6 +369,8 @@ A fork() failure may result in the following tests failing: See comment on fork in L below. +=head1 Specific features of the Cygwin port + =head2 Script Portability on Cygwin Cygwin does an outstanding job of providing UNIX-like semantics on top of @@ -405,20 +399,38 @@ to the translations applied to POSIX style pathnames). 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 +mode for an C is determined by the mode of the mount that underlies +the file. Perl provides a C function to set binary mode on files +that otherwise would be treated as text. C with the C flag sets text mode on files that otherwise would be treated as binary: sysopen(FOO, "bar", O_WRONLY|O_CREAT|O_TEXT) -lseek(), tell() and sysseek() only work with files opened in binary mode. +C, C and C only work with files opened in binary +mode. The text/binary issue is covered at length in the Cygwin documentation. +=item * PerlIO + +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 call like this: + + open(FH, ">:crlf", "out.txt"); + +which will do conversion from LF to CR/LF on the output, or in the +environment settings (add this to your .bashrc): + + export PERLIO=crlf + +which will pull in the crlf PerlIO layer which does LF -> CRLF conversion +on every output generated by perl. + =item * F<.exe> -The Cygwin stat(), lstat() and readlink() functions make the F<.exe> +The Cygwin C, C and C 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. @@ -426,27 +438,36 @@ 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. -=item * chown() +=item * cygwin vs. windows process ids + +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, which is not +the winpid. Use C and C +to translate between them. + +=item * C -On WinNT chown() can change a file's user and group IDs. On Win9x chown() +On WinNT C can change a file's user and group IDs. On Win9x C is a no-op, although this is appropriate since there is no security model. =item * Miscellaneous -File locking using the C command to fcntl() is a stub that +File locking using the C command to C is a stub that returns C. -Win9x can not rename() an open file (although WinNT can). +Win9x can not C an open file (although WinNT can). -The Cygwin chroot() implementation has holes (it can not restrict file +The Cygwin C implementation has holes (it can not restrict file access by native Win32 programs). Inplace editing C of files doesn't work without doing a backup of the file being edited C because of windowish restrictions, -therefore Perl adds the C<.bak> automatically if you use C +therefore Perl adds the suffix C<.bak> automatically if you use C without specifying a backup extension. -Using fork() after loading multiple dlls may fail with an internal cygwin +Using C after loading multiple dlls may fail with an internal cygwin error like the following: 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 @@ -456,7 +477,26 @@ error like the following: Use the rebase utility to resolve the conflicting dll addresses. The rebase package is included in the Cygwin netrelease. Use setup.exe from -F to install it. +F to install it and run rebaseall. + +=back + +=head2 Prebuilt methods: + +=over 4 + +=item C + +Returns current working directory. + +=item C + +Translates a cygwin pid to the corresponding Windows pid (which may or +may not be the same). + +=item C + +Translates a Windows pid to the corresponding cygwin pid (if any). =back @@ -466,10 +506,10 @@ This will install Perl, including I pages. make install 2>&1 | tee log.make-install -NOTE: If C is redirected `C' will B prompt +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 +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 @@ -490,7 +530,7 @@ be kept as clean as possible (listing not updated yet). 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 + pod/perlhist.pod pod/perlmodlib.pod perl/buildtoc pod/perltoc.pod =item Build, Configure, Make, Install @@ -518,12 +558,14 @@ be kept as clean as possible (listing not updated yet). 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/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 @@ -556,7 +598,7 @@ be kept as clean as possible (listing not updated yet). =head1 BUGS ON CYGWIN Support for swapping real and effective user and group IDs is incomplete. -On WinNT Cygwin provides setuid(), seteuid(), setgid() and setegid(). +On WinNT Cygwin provides C, C, C and C. However, additional Cygwin calls for manipulating WinNT access tokens and security contexts are required. @@ -572,4 +614,4 @@ Gerrit P. Haase . =head1 HISTORY -Last updated: 2003-03-20 +Last updated: 2005-02-11