From e3988807e3c94bd893c5421244becf656ac37f0b Mon Sep 17 00:00:00 2001 From: "Jerry D. Hedden" Date: Mon, 24 Sep 2007 16:58:00 -0400 Subject: [PATCH] README.cygwin update From: "Jerry D. Hedden" Message-ID: <1ff86f510709241758o4027c237w7387e7ab86680d55@mail.gmail.com> p4raw-id: //depot/perl@31958 --- README.cygwin | 41 ++++++----------------------------------- 1 file changed, 6 insertions(+), 35 deletions(-) diff --git a/README.cygwin b/README.cygwin index 3bccc3e..e9e4eff 100644 --- a/README.cygwin +++ b/README.cygwin @@ -229,19 +229,6 @@ You may see some messages during Configure that seem suspicious. =over 4 -=item * I - -I is needed to build dynamic libraries, but it does not exist -when C checking occurs (it is not created until C runs). -You will see the following message: - - 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. - -Since the guess is correct, this is not a problem. - =item * Win9x and C Win9x does not correctly report C with a non-blocking read on a @@ -277,27 +264,6 @@ Simply run I and wait: make 2>&1 | tee log.make -=head2 Errors on Cygwin - -Errors like these are normal: - - ... - make: [extra.pods] Error 1 (ignored) - ... - make: [extras.make] Error 1 (ignored) - -=head2 ld2 on Cygwin - -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 I<$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. - =head1 TEST ON CYGWIN There are two steps to running the test suite: @@ -448,7 +414,7 @@ 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 * cygwin vs. windows process ids +=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 @@ -457,6 +423,11 @@ winpid. E.g. C<$$> is the cygwin pid of F, which is not the winpid. Use C and C to translate between them. +=item * Cygwin vs. Windows errors + +Under Cygwin, $^E is the same as $!. When using L, +use C to get the last Windows error. + =item * C On WinNT C can change a file's user and group IDs. On Win9x C -- 2.7.4