Re: looking for cygnus compatible perl

["Earnie Boyd" <earnie_boyd@hotmail.com>]

I compiled the Perl package without much ado.  When the compiler 
complained I either #ifdef'ed or #define'd the problems.  Be sure to 
look at the configure --help and make a determination about switches.  I 
did not compile the utilites just perl.

-        \\||//
---o0O0--Earnie--0O0o----
-earnie_boyd@hotmail.com-
------ooo0O--O0ooo-------

>From: "Jon S. Jaques" <sysadmin@almus.com>
>To: "B. Elizabeth Trojan" <lizt@synopsys.com>
>Cc: <gnu-win32@cygnus.com>
>Subject: Re: looking for cygnus compatible perl
>Date: Thu, 18 Dec 1997 13:55:43 -0500
>
>>Is there a version of Perl available for win32
>that is Cygnus
>>compatible? By Cygnus compatible I mean accepts
>UNC paths and
>>knows about cygnus mounts.
>
>
>That would be "the" Perl; ie that is v5.004_04,
>the very same that is compiled under Unix/Linux.
>( http://www.perl.org/CPAN/src/latest.tar.gz )
>
>Is it easy? Supposedly, although I've not yet
>gotten it to work, but haven't given up.
>
>Assuming that you've installed "cdk.exe" into the
>default location, there're two updates you need:
>1.) The new cygwin.dll, and 2.) Chris Faylor's
>Perl patch which is specific to Cygwin32
>installation/compilation. (The cygwin.dll seems to
>be distributed from a users' site, along with a
>new Bash.exe, among other things, and I can't tell
>if their presence, or lack thereof, affects the
>perl install/compile.)
>
>These are the steps that were advised to me:
>
>>>Here is what I would try:
>>>
>>> mkdir /usr/src/perl
>>> mount -b c:\usr\src\perl /perlsrc
>>> bash
>>> cd /perlsrc
>>> tar xzf /wherever/perl5.004_04.tar.gz
>>> mv perl5.004_04/* .
>>> tar xzf /whereever/cygperl5.004_04.pat.tar.gz
>>> /bin/sh cygperlpat5.004_04
>>> patch -p1 -N < cygperlpat5.004_04
>>> sh Configure
>
>And then, when it didn't work, we went here:
>
>>It is a prerequisite that you are able to compile
>programs.  Does your
>>gcc work?  Can you successfully build a simple
>"hello world" program?
>>
>>Also, the patched README file *does not* say to
>copy files anywhere.
>
>Note this last, which IS different from the
>original Perl README. If you've already followed
>those instructions, then I'd reccomend deleting
>the files "gcc2" and "ld2" which you theoretically
>already copied into your path.
>
>Personally, I can compile a simple file,
>program1.cpp ("hello world") with *g++* but NOT
>gcc (a friend suggested that the file was a
>"plus-plus" and that gcc is not, but I don't
>really know much about either... my primary reason
>for this thing is just to get the new Perl
>compiled on my system to open up some options in
>my Perl programming... one language at a time, ple
>ase! <grin>)
>
>Please, if you have no luck, then lets' continue
>this dialogue-- I'd really like to get this
>resolved.
>
>-
>For help on using this list (especially unsubscribing), send a message 
to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>



______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".