| 1 | The following assumes you have the GNU-Win32 package, version b17.1 or |
| 2 | later, installed and configured on your system. See |
| 3 | http://www.cygnus.com/misc/gnu-win32/ for details on the GNU-Win32 |
| 4 | project and the Cygwin32 API. |
| 5 | |
| 6 | 1) Copy the contents of the cygwin32 directory to the Perl source |
| 7 | root directory. |
| 8 | |
| 9 | 2) Modify the ld2 script by making the PERLPATH variable contain the |
| 10 | Perl source root directory. For example, if you extracted perl to |
| 11 | "/perl5.004", change the script so it contains the line: |
| 12 | |
| 13 | PERLPATH=/perl5.004 |
| 14 | |
| 15 | 3) Copy the two scripts ld2 and gcc2 from the cygwin32 subdirectory to a |
| 16 | directory in your PATH environment variable. For example, copy to |
| 17 | /bin, assuming /bin is in your PATH. (These two scripts are 'wrapper' |
| 18 | scripts that encapsulate the multiple-pass dll building steps used by |
| 19 | GNU-Win32 ld/gcc.) |
| 20 | |
| 21 | 4) Run the perl Configuration script as stated in the perl README file: |
| 22 | |
| 23 | sh Configure |
| 24 | |
| 25 | When confronted with this prompt: |
| 26 | |
| 27 | First time through, eh? I have some defaults handy for the |
| 28 | following systems: |
| 29 | . |
| 30 | . |
| 31 | . |
| 32 | Which of these apply, if any? |
| 33 | |
| 34 | Select "cygwin32". |
| 35 | |
| 36 | The defaults should be OK for everything, except for the specific |
| 37 | pathnames for the cygwin32 libs, include files, installation dirs, |
| 38 | etc. on your system; answer those questions appropriately. |
| 39 | |
| 40 | NOTE: On windows 95, the configuration script only stops every other |
| 41 | time for responses from the command line. In this case you can manually |
| 42 | copy hints/cygwin32.sh to config.sh, edit config.sh for your paths, and |
| 43 | run Configure non-interactively using sh Configure -d. |
| 44 | |
| 45 | 5) Run "make" as stated in the perl README file. |
| 46 | |
| 47 | 6) Run "make test". Some tests will fail, but you should get around a |
| 48 | 83% success rate. (Most failures seem to be due to Unixisms that don't |
| 49 | apply to win32.) |
| 50 | |
| 51 | 7) Install. If you just run "perl installperl", it appears that perl |
| 52 | can't find itself when it forks because it changes to another directory |
| 53 | during the install process. You can get around this by invoking the |
| 54 | install script using a full pathname for perl, such as: |
| 55 | |
| 56 | /perl5.004/perl installperl |
| 57 | |
| 58 | This should complete the installation process. |
| 59 | |