cygwin32 update

	Message-Id:  <71E287AB0D94D111BBD600600849EC8185EDD9@POST>
	Subject:  [ID 19990602.003] perl5.005_03 (CORE) cygwin32 port

p4raw-id: //depot/perl@3582

1 files changed, 56 insertions, 44 deletions

diff --git a/cygwin32/build-instructions.steven-morlock b/cygwin32/build-instructions.steven-morlock
index 58d19936c3..70b7a55995 100644
--- a/cygwin32/build-instructions.steven-morlock
+++ b/cygwin32/build-instructions.steven-morlock
@@ -1,4 +1,9 @@
-From comp.lang.perl.misc. The included patch, perl5.005_02.patch, implements most of the suggestions below. My observations during the build process are commented within the body of Mr. Morlock's message, set off by ******CSW******
+This document is obsolete. Refer to README.cygwin32.
+
+From comp.lang.perl.misc. perl5.005_03-static-patch 
+implements most of the suggestions below. My observations during the 
+build process are commented within the body of Mr. Morlock's message, 
+set off by ******CSW******
 
 
 **************************************
@@ -12,7 +17,8 @@ Cygwin Win32 ports of the GNU development tools (Cygwin32) you might
 get something out of my experience of building it.
 
 An advantage of the versions Perl built with Cygwin32 is that Cygwin32
-has a POSIX compatible library including support for the fork() function.
+has a POSIX compatible library including support for the fork() 
+function.
 
 Steve
 
@@ -51,15 +57,16 @@ directory.  <INST> will refer to the perl target/install directory.
 
 * Pre-build checklist:
 
-  - I found that building Perl on a unmounted partition/drive other than the
-    root will fail.  It appears that the double forward slash that Cygwin32
-    uses to reference drives other than the root drive (typically C:) gets
-    converted to a single forward slash at several points in the build process.
-    I have not tried, but expect it would work, to mount the non-root drive.
-    This problem held true for both the drive where the perl source were and
-    the drive where the Cygwin32 binaries where located.  In the build
-    described in these notes the Perl source and Cygwin32 binaries were located
-    on the root drive.
+  - I found that building Perl on a unmounted partition/drive other 
+    than the root will fail.  It appears that the double forward slash 
+    that Cygwin32 uses to reference drives other than the root drive 
+    (typically C:) gets converted to a single forward slash at several
+    points in the build process. I have not tried, but expect it would
+    work, to mount the non-root drive. This problem held true for both
+    the drive where the perl source were and the drive where the
+    Cygwin32 binaries where located.  In the build described in these
+    notes the Perl source and Cygwin32 binaries were located on the
+    root drive.
 
   - Following the instructions in <PERL>/README.cygwin32:
 *******CSW********
@@ -82,13 +89,13 @@ the patch does this
           i_stdarg='define'
           i_varargs='undef'
 
-        This change allows us to pick up the right version of va_start().
-        Cygwin32 has both a signal and double parameter versions floating
-        around in their header files.
+        This change allows us to pick up the right version of 
+        va_start(). Cygwin32 has both a signal and double parameter
+        versions floating around in their header files.
 
-      + Remove support for dynamic linking.  I found that all DynaLoader'd
-        extensions crashed during the running of the test suite.  Add or edit
-        'usedl' entry to read:
+      + Remove support for dynamic linking.  I found that all 
+        DynaLoader'd extensions crashed during the running of the
+        test suite. Add or edit 'usedl' entry to read:
 *******CSW********
 the patch does this
 ******************
@@ -96,19 +103,20 @@ the patch does this
 
         If there is enough push I will try to sort out the problems with
         dynamic loading.  I have made several unsuccessful attempts at
-        modifying <PERL>/perlld to fix this problem.  If you are interested,
-        write me.
+        modifying <PERL>/perlld to fix this problem.  If you are 
+        interested, write me.
 
       + Change the path to the  Cygwin32 directories.  This includes the
-        entries for 'usrinc', 'libpth', 'lddlflags', 'libc' and 'usrinc'.
+        entries for 'usrinc', 'libpth', 'lddlflags', 'libc' and 
+        'usrinc'.
 *******CSW********
 the patch does this ^
 ******************
 
   - Edit makedepend.SH.  The original version of makedepend.SH produces
-    dependencies that include double backslashes.  This can not be processed
-    by Cygwin32's 'make'.  Apply the following modification to makedepend.SH
-    to correct these unfortunate filenames:
+    dependencies that include double backslashes.  This can not be 
+    processed by Cygwin32's 'make'.  Apply the following modification 
+    to makedepend.SH to correct these unfortunate filenames:
 *******CSW********
 and this, as well \/
 ******************
@@ -129,8 +137,9 @@ and this, as well \/
 
   - Edit config_h.SH. The original version of config_h.SH has an bogus
     #include that gets propagated into the dependency list in Makefile
-    create from the makedepend script.  The Apply the following modification
-    to config_h.SH to work around this unfortunate filename:
+    create from the makedepend script.  The Apply the following 
+    modification to config_h.SH to work around this unfortunate 
+    filename:
 *******CSW********
 the patch does this, too
 ******************
@@ -151,23 +160,24 @@ the patch does this, too
   #endif
 
     The real source of the problem appears that the 'make depend' in the
-    'x2p' directory has problems.  The following messages are generated by
-    that 'make depend':
+    'x2p' directory has problems.  The following messages are generated 
+    by that 'make depend':
 
       Finding dependencies for hash.o.
       gcc2: Can't open gcc2
       ... [similar messages to above]
-      You don't seem to have a proper C preprocessor.  Using grep instead.
+      You don't seem to have a proper C preprocessor.  Using grep 
+      instead.
       Updating GNUmakefile...
 
     So the grep is pulling the bogus #include from the file.  The patch
     turns the #include'd message into a comment.
 
-  - Run the Configure in the <PERL> directory as described in the document
-    <PERL>/README.cygwin32
+  - Run the Configure in the <PERL> directory as described in the 
+    document <PERL>/README.cygwin32
 
-    I receive the message "THIS PACKAGE SEEMS INCOMPLETE.".  This does not
-    appear to be a problem.
+    I receive the message "THIS PACKAGE SEEMS INCOMPLETE.".  This does 
+    not appear to be a problem.
 
     When presented with the list of handy defaults, select 'cygwin32'
 
@@ -181,11 +191,11 @@ the patch does this, too
 *******CSW********
 I didn't see this problem \/
 ******************
-  - I experience problems when building two files 'pp_sys.o' & 'doio.o'.  The
-    build process will crash with a Windows dialog during the build of these two
-    files.  The way I get by the problem is to control-C the make and issue
-    the build commands for the two files by hand.  In the Perl directory issue
-    the following commands:
+  - I experience problems when building two files 'pp_sys.o' & 
+    'doio.o'.  The build process will crash with a Windows dialog
+    during the build of these two files. The way I get by the problem
+    is to control-C the make and issue the build commands for the two
+    files by hand.  In the Perl directory issue the following commands:
 
       `sh  cflags libperl.a pp_sys.o` pp_sys.c
       `sh  cflags libperl.a doio.o` doio.c
@@ -198,9 +208,9 @@ I didn't see this problem \/
 * Testing:
 
   I found that the majority of the tests passed.  There were no errors
-  that I thought particularly scary.  There were several unexpected results
-  such as a couple 'A required .DLL file, CYGWIN1.DLL, was not found' dialogs
-  and 'Perl perform an illegal operation' dialogs.
+  that I thought particularly scary.  There were several unexpected 
+  results such as a couple 'A required .DLL file, CYGWIN1.DLL, was not
+  found' dialogs and 'Perl perform an illegal operation' dialogs.
 
 *******CSW********
 saw the "missing dll" during one test
@@ -210,7 +220,8 @@ saw the "missing dll" during one test
 
   - Renamed or delete the file <PERL>/t/lib/io_sock.t so it will not be
     executed.  This test hangs the system.  I have made no attempts to
-    fix the problem.  From the <PERL> directory issue the following command:
+    fix the problem.  From the <PERL> directory issue the following 
+    command:
 
 *******CSW********
 I didn't do this, and saw no problems.
@@ -223,11 +234,12 @@ I didn't do this, and saw no problems.
 
 * Installing:
 
-  The install seems to work okay.  There are problems when install the man
-  pages, but we don't need any stinkin' man pages, right?
+  The install seems to work okay.  There are problems when install the 
+  man pages, but we don't need any stinkin' man pages, right?
 
 *******CSW********
-the man pages that didn't install were those that had "::" in their filename.
+the man pages that didn't install were those that had "::" in their 
+filename.
 ******************
 
   - Issue the command 'make install' in the directory <PERL>.