Compiling Perl under b20.1

Compiling Perl under b20.1

[Allan Peda]

Has there been much success with this?  I've done it with MSVC + nmake,
but I'd get more of a thrill using cygwin.

I searched at www.qub.com, but it doesn't look too active.  The
directory entry in the distribution with cygwin instructions didn't work
well for me last time I tried.

Allan

A


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

How can I get off of this list?

[Ed Peddycoart]

I have tried at least a half dozen times to unsubscribe from this list by
sending a message to cygwin-unsubscribe@sourceware.cygnus.com.  I have
placed unsubscribe as the subject and in the body, just as the subject, just
as the body etc. but have not been able to unsubscribe.  Am I doing
something wrong?
Ed


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Sebastien Barre]

At 22:04 04/03/99 -0500, Allan Peda wrote:

>Has there been much success with this?  I've done it with MSVC + nmake,
>but I'd get more of a thrill using cygwin.

I did (5.005_002  static build, 91.4% successfull test).

As many people from this list helped me, I'd glad to offer the same. 

Basically, 

*) Read the README.cywin32

*) Edit the hints/cygwin32.sh file to reflect your paths.

Here are also a couple of settings I found useful when performing automatic
build (copy hints/cygwin32.sh to config.sh, and do sh Configure -d)

usedl='n'
i_stdarg='define'
i_varargs='undef'
osname='cygwin_nt-4.0'
osvers='20.1'
archname='cygwin32'
signal_t='int'
d_voidsig='define'
i_sysselct='undef'
signal_t='void'

*) Browse Usenet archives (DejaNews), and find  "HOWTO: Builiding Perl
under Win95/98 using Cygwin32 " 
Steven Morlock <newspost@morlock.net>
1998/12/21
comp.lang.perl.misc

*) Then apply this patch (Thanks to Todd Goodman)

This is my change in Cwd.pm:
--- cwd.pm	Fri Feb 26 21:52:42 1999
+++ cwd.pm.orig	Fri Jan 22 20:49:54 1999
@@ -208,8 +208,6 @@
     my $start = @_ ? shift : '.';
     my($dotdots, $cwd, @pst, @cst, $dir, @tst);
 
-    return cwd() if ( $^O =~ /cygwin/ );
-
     unless (@cst = stat( $start ))
     {

And tell me (email) if it fails.

______________________________________________________________
Sebastien Barre                  http://www.hds.utc.fr/~barre/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Charles Wilson]

I've taken Sebastien Barre's suggestions and Steven Morlock's instructions and
successfully compiled perl5.005_02 under Cygwin B20.1 and WinNT4sp4. I took
all their suggestions and created a patch file and collected the instructions
together in the attached package (6kB). It can also be downloaded from

ftp://belgarion.resnet.gatech.edu/pub/cygwin/B20/perl-cygwin-instructions.tar.gz

Yoiu can also find a binary distribution of perl at the same location:

ftp://belgarion.resnet.gatech.edu/pub/cygwin/B20/perl5.005_02-cygwinb20.tar.bz2

It's 2.6Meg, unpack from /. It will install into /usr/local/bin/,
/usr/local/man/, /usr/local/lib/, and a few text files into
/usr/local/src/perl5.005_02/. The ftp server has been up & down a lot lately,
please be patient.

Please comment on both the collected build instructions and the binary
distribution.

Thanks,
Chuck Wilson

Re: Compiling Perl under b20.1

[Sebastien Barre]

At 16:13 05/03/99 -0500, Charles Wilson wrote:

>I've taken Sebastien Barre's suggestions and Steven Morlock's instructions and
>successfully compiled perl5.005_02 under Cygwin B20.1 and WinNT4sp4. I took
>all their suggestions and created a patch file and collected the instructions
>together in the attached package (6kB).

Very good, thanks !. I tested it, and it works. After applying the patch,
one might have to change his paths in hints/cygwin32.sh, otherwise it's
perfect.

>Please comment on both the collected build instructions and the binary
>distribution.

*) Steven Morlock  published TWO articles (a correction to the first one),
but you did not include the second one (which is related to binary mode). 

Re: HOWTO: Builiding Perl under Win95/98 using Cygwin32  
Author: Steven Morlock <newspost@morlock.net>
Date: 1998/12/22
Forum: comp.lang.perl.misc 

It's not that important because you included the modification in your patch :

+ #if defined(__CYGWIN32__)
+   /* USEMYBINMODE
...

*) I also forgot to mention this article :

     To: cygwin@sourceware.cygnus.com 
     Subject: configure and cpp problem (Was: bug: missing include files in
B20.1) 
     From: Teun Burgers <burgers@ecn.nl> 
     Date: Mon, 22 Feb 1999 16:52:09 +0100 

But I seems to me the one DO NOT need it (but I kept it, just in case). You
might have a look anyway.

*) Furthermore, I'd just add that I had some problems while building perl
if source files were extracted in a binary mounted partition. BUT I also
read some testimony regarding the contrary (i.e. you need to mount it as
binary) ! Therefore, It's just a hint, but if you experience some problems
(sadly, I forgot to save the error messages), try different mount mode.

*) make test

Here is the result after applying your modifications :

> make test
Failed 7 test scripts out of 186, 91.40% okay.

>cd t
>perl harness

Failed Test  Status Wstat Total Fail  Failed  List of failed
-------------------------------------------------------------------------------
io/fs.t                      26    4  15.38%  5, 7, 9-10
lib/anydbm.t      2   512    12    9  75.00%  2, 5-12
lib/findbin.t                 1    1 100.00%  1
lib/sdbm.t        2   512    18   15  83.33%  2, 5-18
op/magic.t                   35    1   2.86%  23
op/stat.t                    58    6  10.34%  2, 9, 19-20, 26, 35
op/taint.t                  149    3   2.01%  1, 3, 31
9 tests skipped, plus 20 subtests skipped.
Failed 7/186 test scripts, 96.24% okay. 39/6193 subtests failed, 99.37% okay.

(anydbm and sdbm might be different if you mounted your partition as binary).

Some of them just fail because they should NOT be executed in a win32
implementation. They should be skipped. Sadly, the test behind this does
NOT handle cygwin32 environment, just plain MS32 by comparing OS name to
MSWin32 ($^O eq 'MSWin32'). Let's add a test for cygwin ($^O =~ /cygwin/).
Here is a couple of tests I think that might be patched (I could not do
anything for magic.t, as well as stat.t, which is a known problem) :

diff -urN perl5.005_02/t/io/fs.t.orig perl5.005_02/t/io/fs.t
--- perl5.005_02/t/io/fs.t.orig	Sat Mar 06 12:18:26 1999
+++ perl5.005_02/t/io/fs.t	Sat Mar 06 12:18:31 1999
@@ -12,7 +12,7 @@
 $Is_Dosish = ($^O eq 'dos' or $^O eq 'os2');
 
 # avoid win32 (for now)
-do { print "1..0\n"; exit(0); } if $^O eq 'MSWin32';
+do { print "1..0\n"; exit(0); } if $^O eq 'MSWin32' || $^O =~ /cygwin/;
 
 print "1..26\n";
 
diff -urN perl5.005_02/t/lib/anydbm.t.orig perl5.005_02/t/lib/anydbm.t
--- perl5.005_02/t/lib/anydbm.t.orig	Sat Mar 06 12:22:30 1999
+++ perl5.005_02/t/lib/anydbm.t	Sat Mar 06 12:23:04 1999
@@ -22,7 +22,7 @@
 if (! -e $Dfile) {
 	($Dfile) = <Op_dbmx*>;
 }
-if ($^O eq 'amigaos' || $^O eq 'os2' || $^O eq 'MSWin32' || $^O eq 'dos') {
+if ($^O eq 'amigaos' || $^O eq 'os2' || $^O eq 'MSWin32' || $^O eq 'dos'
|| $^O =~ /cygwin/) {
     print "ok 2 # Skipped: different file permission semantics\n";
 }
 else {
diff -urN perl5.005_02/t/lib/sdbm.t.orig perl5.005_02/t/lib/sdbm.t
--- perl5.005_02/t/lib/sdbm.t.orig	Sat Mar 06 12:27:04 1999
+++ perl5.005_02/t/lib/sdbm.t	Sat Mar 06 12:27:10 1999
@@ -27,7 +27,7 @@
 if (! -e $Dfile) {
 	($Dfile) = <Op_dbmx.*>;
 }
-if ($^O eq 'amigaos' || $^O eq 'os2' || $^O eq 'MSWin32' || $^O eq 'dos') {
+if ($^O eq 'amigaos' || $^O eq 'os2' || $^O eq 'MSWin32' || $^O eq 'dos'
|| $^O =~ /cygwin/) {
     print "ok 2 # Skipped: different file permission semantics\n";
 }
 else {


(these patch might be just added to your perl.patch and used with patch -p1).

> make test
Failed 6 test scripts out of 186, 91.40% okay.

> cd t
> perl harness

Failed Test  Status Wstat Total Fail  Failed  List of failed
-------------------------------------------------------------------------------
lib/anydbm.t      2   512    12    8  66.67%  5-12
lib/findbin.t                 1    1 100.00%  1
lib/sdbm.t        2   512    18   14  77.78%  5-18
op/magic.t                   35    1   2.86%  23
op/stat.t                    58    6  10.34%  2, 9, 19-20, 26, 35
op/taint.t                  149    3   2.01%  1, 3, 31
10 tests skipped, plus 22 subtests skipped.
Failed 6/186 test scripts, 96.77% okay. 33/6167 subtests failed, 99.46% okay.

Which is slightly better :)

Hope it helps


______________________________________________________________
Sebastien Barre                  http://www.hds.utc.fr/~barre/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Charles Wilson]

Sebastien Barre wrote:

> Very good, thanks !. I tested it, and it works. After applying the patch,
> one might have to change his paths in hints/cygwin32.sh, otherwise it's
> perfect.

Yeah, that's true. The "build-instructions" were more in the nature of "here's how
I built the binary kit" than a general guide. BTW, did you apply the patch to a
pristine copy of the source, or had you already applied the changes from Teun
Burgers (below)?

> >Please comment on both the collected build instructions and the binary
> >distribution.
>
> *) Steven Morlock  published TWO articles (a correction to the first one),
> but you did not include the second one (which is related to binary mode).
>
> Re: HOWTO: Builiding Perl under Win95/98 using Cygwin32
> Author: Steven Morlock <newspost@morlock.net>
> Date: 1998/12/22
> Forum: comp.lang.perl.misc
>
> It's not that important because you included the modification in your patch :
>
> + #if defined(__CYGWIN32__)
> +   /* USEMYBINMODE
> ...

Oops. I'll go grab that usenet posting and stick it in the build instruction kit.

> *) I also forgot to mention this article :
>
>      To: cygwin@sourceware.cygnus.com
>      Subject: configure and cpp problem (Was: bug: missing include files in
> B20.1)
>      From: Teun Burgers <burgers@ecn.nl>
>      Date: Mon, 22 Feb 1999 16:52:09 +0100
>
> But I seems to me the one DO NOT need it (but I kept it, just in case). You
> might have a look anyway.

Hmmm....here's the relevant part of Teun Burgers' post:

> The configure script (relevant part in fhdr.old) creates
> a script findhdr that looks for the header file. findhr first
> simply tests for existance (test -f) of the .h file in
> H-i586-cygwin32/i586-cygwin32/include and if not found there
> it uses the C preprocessor gcc -E -.
>
Except the script says "$usrinc/\$wanted" which fails for a different reason on my
system: $usrinc is a pathlist, not a single path. However, this doesn't seem to
cause a problem, because the second step works....

>
> Because stdarg.h is not found in the first step it must be found
> in the second step. This second step goes wrong for two reasons:
>
> 1) the shell scripts tests whether the expanded include file
>    name by gcc -E matches */stdarg.h. This test fails because
>    gcc returns a DOS filename with \ e.g.
>    d:\\cygnus\\cygwin-b20  etc, so it does not match.
>
The egcs-1.1.1 returns
"F:/cygnus/cygwin-b20/usr/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.60/include/stdarg.h"
so the match succeeds. However, the correction to the search regex will work in
both cases.

>
>    There are two solutions:
>    - change the matching condition in findhdr from
>      */stdarg.h  to  *[/\\]stdarg.h
>    - make gcc -E - return a unixy file name
>
> 2) Even with this test fixed it still goes wrong.
>    This seems to be a bug in the configure script.
>    The configure scripts sets variable name in a while
>    loop that is the end of a pipe. Because the while is
>    in a pipe, it runs in a subshell and variable settings
>    are local to that subshell.
>
????. I understand the theory, but my build seemed to work okay. However, I don't
see how including Mr. Burgers' fixes will hurt anything, so I'll go ahead an add
them to the "patch", unless anyone can think of a good reason not to.

> *) Furthermore, I'd just add that I had some problems while building perl
> if source files were extracted in a binary mounted partition. BUT I also
> read some testimony regarding the contrary (i.e. you need to mount it as
> binary) ! Therefore, It's just a hint, but if you experience some problems
> (sadly, I forgot to save the error messages), try different mount mode.

I extracted into a binary mounted partition. My *guess* is that you might have
used WinZip or somesuch to extract the source. If WinZip converted all newlines to
\013\010, AND the partition was mounted binary, then that would cause problems.

> *) make test
>
> Here is the result after applying your modifications :
>
> > make test
> Failed 7 test scripts out of 186, 91.40% okay.

> >cd t
> >perl harness
>
> Failed Test  Status Wstat Total Fail  Failed  List of failed
> -------------------------------------------------------------------------------
> io/fs.t                      26    4  15.38%  5, 7, 9-10
> lib/anydbm.t      2   512    12    9  75.00%  2, 5-12
> lib/findbin.t                 1    1 100.00%  1
> lib/sdbm.t        2   512    18   15  83.33%  2, 5-18
> op/magic.t                   35    1   2.86%  23
> op/stat.t                    58    6  10.34%  2, 9, 19-20, 26, 35
> op/taint.t                  149    3   2.01%  1, 3, 31
> 9 tests skipped, plus 20 subtests skipped.
> Failed 7/186 test scripts, 96.24% okay. 39/6193 subtests failed, 99.37% okay.
>
> (anydbm and sdbm might be different if you mounted your partition as binary).

Yup, they are different. Here's my output, *without* your changes to the testing
scripts.

>make test
Failed 4 test scripts out of 186, 92.47% okay.
>cd t
>perl harness

Failed Test  Status Wstat Total Fail  Failed  List of failed
-------------------------------------------------------------------------------
lib/findbin.t                 1    1 100.00%  1
op/magic.t                   35    1   2.86%  23
op/stat.t                    58    2   3.45%  4, 35
op/taint.t                  149    3   2.01%  1, 3, 31
10 tests skipped, plus 20 subtests skipped.
Failed 4/186 test scripts, 97.85% okay. 7/6191 subtests failed, 99.89% okay.

(skipped tests: lib/thread, lib/posix, lib/odbm, lib/ndbm, lib/ipc_sysv, lib/gdbm,
lib/db-recno, lib/db-hash, lib/db-btree, op/groups)

Now, all three of your patches address problems I didn't see; the main difference
between us being binary vs. text mounts. If that is the case, should these tests
be skipped for all cygwin (binary and text mount) or should the tests be fixed so
that they work for both binary and text mounts? I'm not sure if the second option
means hacking the test scripts, or hacking perl itself.

> Some of them just fail because they should NOT be executed in a win32
> implementation. They should be skipped. Sadly, the test behind this does
> NOT handle cygwin32 environment, just plain MS32 by comparing OS name to
> MSWin32 ($^O eq 'MSWin32'). Let's add a test for cygwin ($^O =~ /cygwin/).
> Here is a couple of tests I think that might be patched (I could not do
> anything for magic.t, as well as stat.t, which is a known problem) :
>
> <SNIP>
>
> > make test
> Failed 6 test scripts out of 186, 91.40% okay.
>
> > cd t
> > perl harness
>
> Failed Test  Status Wstat Total Fail  Failed  List of failed
> -------------------------------------------------------------------------------
> lib/anydbm.t      2   512    12    8  66.67%  5-12
> lib/findbin.t                 1    1 100.00%  1
> lib/sdbm.t        2   512    18   14  77.78%  5-18
> op/magic.t                   35    1   2.86%  23
> op/stat.t                    58    6  10.34%  2, 9, 19-20, 26, 35
> op/taint.t                  149    3   2.01%  1, 3, 31
> 10 tests skipped, plus 22 subtests skipped.
> Failed 6/186 test scripts, 96.77% okay. 33/6167 subtests failed, 99.46% okay.
>
> Which is slightly better :)

--Chuck


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Sebastien Barre]

At 13:27 06/03/99 -0500, Charles Wilson wrote:

>BTW, did you apply the patch to a
>pristine copy of the source, or had you already applied the changes from Teun
>Burgers (below)?

No, from the pristine copy of course :) My perl is working quite right I
guess, I just wanted to help you controlling your build package, so I
started from the beginning, following your statements.

>Hmmm....here's the relevant part of Teun Burgers' post:

>> The configure script (relevant part in fhdr.old) creates
>> a script findhdr that looks for the header file. findhr first
>> simply tests for existance (test -f) of the .h file in
>> H-i586-cygwin32/i586-cygwin32/include and if not found there
>> it uses the C preprocessor gcc -E -.

>Except the script says "$usrinc/\$wanted" which fails for a different reason 
>on my system: $usrinc is a pathlist, not a single path. However, this
doesn't seem to
>cause a problem, because the second step works....

[...]

>The egcs-1.1.1 returns
>"F:/cygnus/cygwin-b20/usr/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.60/incl
>ude/stdarg.h" so the match succeeds. 

Oh yes, *NOW* I remember, I had the same problem, but read an article in
the list stated the egcs 1.1.1 fixed a similar problem. I upgraded to egcs
1.1.1 and that solved my problem. Therefore, I guess that this information
*definitely* need a place in your build instructions : egcs 1.1.1 might be
handy.

>However, the correction to the search regex will work in
>both cases.

[..]

>????. I understand the theory, but my build seemed to work okay.

egcs 1.1.1 :)

>However, I 
>don't see how including Mr. Burgers' fixes will hurt anything, so I'll go
ahead an 
>add them to the "patch", unless anyone can think of a good reason not to.

I tried, but was unable to find the relevant part to patch.

>> *) Furthermore, I'd just add that I had some problems while building perl
>> if source files were extracted in a binary mounted partition. BUT I also
>> read some testimony regarding the contrary (i.e. you need to mount it as
>> binary) ! Therefore, It's just a hint, but if you experience some problems
>> (sadly, I forgot to save the error messages), try different mount mode.

>I extracted into a binary mounted partition. My *guess* is that you might have
>used WinZip or somesuch to extract the source. If WinZip converted all 
>newlines to \013\010, AND the partition was mounted binary, then that
would cause problems.

Nope, I'm aware of the Winzip problem, and I'm taking care of that, by
systematically using tar / gzip :)

>> *) make test

(continuing in your answer to Earnie)

______________________________________________________________
Sebastien Barre                  http://www.hds.utc.fr/~barre/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Charles Wilson]

Sebastien Barre wrote:

> At 13:27 06/03/99 -0500, Charles Wilson wrote:
>
> >BTW, did you apply the patch to a
> >pristine copy of the source, or had you already applied the changes from Teun
> >Burgers (below)?
>
> No, from the pristine copy of course :) My perl is working quite right I
> guess, I just wanted to help you controlling your build package, so I
> started from the beginning, following your statements.

I was fairly sure that was the case, but it's best to eliminate the simple things
first.

> <snip>

> Therefore, I guess that this information

> *definitely* need a place in your build instructions : egcs 1.1.1 might be
> handy.
>

Okay. I'll update the build-kit soon.

> <snip>

> >However, I

> >don't see how including Mr. Burgers' fixes will hurt anything, so I'll go
> ahead an
> >add them to the "patch", unless anyone can think of a good reason not to.
>
> I tried, but was unable to find the relevant part to patch.
>

I found the relevant part, and have changed the build-kit to include this patch.
Even though it probably doesn't matter if you're using egcs-1.1.1.

>
> >> *) Furthermore, I'd just add that I had some problems while building perl
> >> if source files were extracted in a binary mounted partition. BUT I also
> >> read some testimony regarding the contrary (i.e. you need to mount it as
> >> binary) ! Therefore, It's just a hint, but if you experience some problems
> >> (sadly, I forgot to save the error messages), try different mount mode.
>
> >I extracted into a binary mounted partition. My *guess* is that you might have
> >used WinZip or somesuch to extract the source. If WinZip converted all
> >newlines to \013\010, AND the partition was mounted binary, then that
> would cause problems.
>
> Nope, I'm aware of the Winzip problem, and I'm taking care of that, by
> systematically using tar / gzip :)

Well, then I'm stumped. I don't know what the *build* problem is (or even if there
is one, after applying all these patches) under text / binary mounts. *make test*
problems are a whole different kettle of fish....continued in next message.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Sebastien Barre]

At 16:13 05/03/99 -0500, Charles Wilson wrote:

>I've taken Sebastien Barre's suggestions and Steven Morlock's instructions and
>successfully compiled perl5.005_02 under Cygwin B20.1 and WinNT4sp4. I took
>all their suggestions and created a patch file and collected the instructions
>together in the attached package (6kB).

Very good, thanks !. I tested it, and it works. After applying the patch,
one might have to change his paths in hints/cygwin32.sh, otherwise it's
perfect.

>Please comment on both the collected build instructions and the binary
>distribution.

*) Steven Morlock  published TWO articles (a correction to the first one),
but you did not include the second one (which is related to binary mode). 

Re: HOWTO: Builiding Perl under Win95/98 using Cygwin32  
Author: Steven Morlock <newspost@morlock.net>
Date: 1998/12/22
Forum: comp.lang.perl.misc 

It's not that important because you included the modification in your patch :

+ #if defined(__CYGWIN32__)
+   /* USEMYBINMODE
...

*) I also forgot to mention this article :

     To: cygwin@sourceware.cygnus.com 
     Subject: configure and cpp problem (Was: bug: missing include files in
B20.1) 
     From: Teun Burgers <burgers@ecn.nl> 
     Date: Mon, 22 Feb 1999 16:52:09 +0100 

But I seems to me the one DO NOT need it (but I kept it, just in case). You
might have a look anyway.

*) Furthermore, I'd just add that I had some problems while building perl
if source files were extracted in a binary mounted partition. BUT I also
read some testimony regarding the contrary (i.e. you need to mount it as
binary) ! Therefore, It's just a hint, but if you experience some problems
(sadly, I forgot to save the error messages), try different mount mode.

*) make test

Here is the result after applying your modifications :

> make test
Failed 7 test scripts out of 186, 91.40% okay.

>cd t
>perl harness

Failed Test  Status Wstat Total Fail  Failed  List of failed
-------------------------------------------------------------------------------
io/fs.t                      26    4  15.38%  5, 7, 9-10
lib/anydbm.t      2   512    12    9  75.00%  2, 5-12
lib/findbin.t                 1    1 100.00%  1
lib/sdbm.t        2   512    18   15  83.33%  2, 5-18
op/magic.t                   35    1   2.86%  23
op/stat.t                    58    6  10.34%  2, 9, 19-20, 26, 35
op/taint.t                  149    3   2.01%  1, 3, 31
9 tests skipped, plus 20 subtests skipped.
Failed 7/186 test scripts, 96.24% okay. 39/6193 subtests failed, 99.37% okay.

(anydbm and sdbm might be different if you mounted your partition as binary).

Some of them just fail because they should NOT be executed in a win32
implementation. They should be skipped. Sadly, the test behind this does
NOT handle cygwin32 environment, just plain MS32 by comparing OS name to
MSWin32 ($^O eq 'MSWin32'). Let's add a test for cygwin ($^O =~ /cygwin/).
Here is a couple of tests I think that might be patched (I could not do
anything for magic.t, as well as stat.t, which is a known problem) :

diff -urN perl5.005_02/t/io/fs.t.orig perl5.005_02/t/io/fs.t
--- perl5.005_02/t/io/fs.t.orig	Sat Mar 06 12:18:26 1999
+++ perl5.005_02/t/io/fs.t	Sat Mar 06 12:18:31 1999
@@ -12,7 +12,7 @@
 $Is_Dosish = ($^O eq 'dos' or $^O eq 'os2');
 
 # avoid win32 (for now)
-do { print "1..0\n"; exit(0); } if $^O eq 'MSWin32';
+do { print "1..0\n"; exit(0); } if $^O eq 'MSWin32' || $^O =~ /cygwin/;
 
 print "1..26\n";
 
diff -urN perl5.005_02/t/lib/anydbm.t.orig perl5.005_02/t/lib/anydbm.t
--- perl5.005_02/t/lib/anydbm.t.orig	Sat Mar 06 12:22:30 1999
+++ perl5.005_02/t/lib/anydbm.t	Sat Mar 06 12:23:04 1999
@@ -22,7 +22,7 @@
 if (! -e $Dfile) {
 	($Dfile) = <Op_dbmx*>;
 }
-if ($^O eq 'amigaos' || $^O eq 'os2' || $^O eq 'MSWin32' || $^O eq 'dos') {
+if ($^O eq 'amigaos' || $^O eq 'os2' || $^O eq 'MSWin32' || $^O eq 'dos'
|| $^O =~ /cygwin/) {
     print "ok 2 # Skipped: different file permission semantics\n";
 }
 else {
diff -urN perl5.005_02/t/lib/sdbm.t.orig perl5.005_02/t/lib/sdbm.t
--- perl5.005_02/t/lib/sdbm.t.orig	Sat Mar 06 12:27:04 1999
+++ perl5.005_02/t/lib/sdbm.t	Sat Mar 06 12:27:10 1999
@@ -27,7 +27,7 @@
 if (! -e $Dfile) {
 	($Dfile) = <Op_dbmx.*>;
 }
-if ($^O eq 'amigaos' || $^O eq 'os2' || $^O eq 'MSWin32' || $^O eq 'dos') {
+if ($^O eq 'amigaos' || $^O eq 'os2' || $^O eq 'MSWin32' || $^O eq 'dos'
|| $^O =~ /cygwin/) {
     print "ok 2 # Skipped: different file permission semantics\n";
 }
 else {


(these patch might be just added to your perl.patch and used with patch -p1).

> make test
Failed 6 test scripts out of 186, 91.40% okay.

> cd t
> perl harness

Failed Test  Status Wstat Total Fail  Failed  List of failed
-------------------------------------------------------------------------------
lib/anydbm.t      2   512    12    8  66.67%  5-12
lib/findbin.t                 1    1 100.00%  1
lib/sdbm.t        2   512    18   14  77.78%  5-18
op/magic.t                   35    1   2.86%  23
op/stat.t                    58    6  10.34%  2, 9, 19-20, 26, 35
op/taint.t                  149    3   2.01%  1, 3, 31
10 tests skipped, plus 22 subtests skipped.
Failed 6/186 test scripts, 96.77% okay. 33/6167 subtests failed, 99.46% okay.

Which is slightly better :)

Hope it helps


______________________________________________________________
Sebastien Barre                  http://www.hds.utc.fr/~barre/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Compiling Perl under b20.1

[Allan Peda]

Has there been much success with this?  I've done it with MSVC + nmake,
but I'd get more of a thrill using cygwin.

I searched at www.qub.com, but it doesn't look too active.  The
directory entry in the distribution with cygwin instructions didn't work
well for me last time I tried.

Allan

A


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Sebastien Barre]

At 13:27 06/03/99 -0500, Charles Wilson wrote:

>BTW, did you apply the patch to a
>pristine copy of the source, or had you already applied the changes from Teun
>Burgers (below)?

No, from the pristine copy of course :) My perl is working quite right I
guess, I just wanted to help you controlling your build package, so I
started from the beginning, following your statements.

>Hmmm....here's the relevant part of Teun Burgers' post:

>> The configure script (relevant part in fhdr.old) creates
>> a script findhdr that looks for the header file. findhr first
>> simply tests for existance (test -f) of the .h file in
>> H-i586-cygwin32/i586-cygwin32/include and if not found there
>> it uses the C preprocessor gcc -E -.

>Except the script says "$usrinc/\$wanted" which fails for a different reason 
>on my system: $usrinc is a pathlist, not a single path. However, this
doesn't seem to
>cause a problem, because the second step works....

[...]

>The egcs-1.1.1 returns
>"F:/cygnus/cygwin-b20/usr/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.60/incl
>ude/stdarg.h" so the match succeeds. 

Oh yes, *NOW* I remember, I had the same problem, but read an article in
the list stated the egcs 1.1.1 fixed a similar problem. I upgraded to egcs
1.1.1 and that solved my problem. Therefore, I guess that this information
*definitely* need a place in your build instructions : egcs 1.1.1 might be
handy.

>However, the correction to the search regex will work in
>both cases.

[..]

>????. I understand the theory, but my build seemed to work okay.

egcs 1.1.1 :)

>However, I 
>don't see how including Mr. Burgers' fixes will hurt anything, so I'll go
ahead an 
>add them to the "patch", unless anyone can think of a good reason not to.

I tried, but was unable to find the relevant part to patch.

>> *) Furthermore, I'd just add that I had some problems while building perl
>> if source files were extracted in a binary mounted partition. BUT I also
>> read some testimony regarding the contrary (i.e. you need to mount it as
>> binary) ! Therefore, It's just a hint, but if you experience some problems
>> (sadly, I forgot to save the error messages), try different mount mode.

>I extracted into a binary mounted partition. My *guess* is that you might have
>used WinZip or somesuch to extract the source. If WinZip converted all 
>newlines to \013\010, AND the partition was mounted binary, then that
would cause problems.

Nope, I'm aware of the Winzip problem, and I'm taking care of that, by
systematically using tar / gzip :)

>> *) make test

(continuing in your answer to Earnie)

______________________________________________________________
Sebastien Barre                  http://www.hds.utc.fr/~barre/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

How can I get off of this list?

[Ed Peddycoart]

I have tried at least a half dozen times to unsubscribe from this list by
sending a message to cygwin-unsubscribe@sourceware.cygnus.com.  I have
placed unsubscribe as the subject and in the body, just as the subject, just
as the body etc. but have not been able to unsubscribe.  Am I doing
something wrong?
Ed


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Charles Wilson]

Sebastien Barre wrote:

> Very good, thanks !. I tested it, and it works. After applying the patch,
> one might have to change his paths in hints/cygwin32.sh, otherwise it's
> perfect.

Yeah, that's true. The "build-instructions" were more in the nature of "here's how
I built the binary kit" than a general guide. BTW, did you apply the patch to a
pristine copy of the source, or had you already applied the changes from Teun
Burgers (below)?

> >Please comment on both the collected build instructions and the binary
> >distribution.
>
> *) Steven Morlock  published TWO articles (a correction to the first one),
> but you did not include the second one (which is related to binary mode).
>
> Re: HOWTO: Builiding Perl under Win95/98 using Cygwin32
> Author: Steven Morlock <newspost@morlock.net>
> Date: 1998/12/22
> Forum: comp.lang.perl.misc
>
> It's not that important because you included the modification in your patch :
>
> + #if defined(__CYGWIN32__)
> +   /* USEMYBINMODE
> ...

Oops. I'll go grab that usenet posting and stick it in the build instruction kit.

> *) I also forgot to mention this article :
>
>      To: cygwin@sourceware.cygnus.com
>      Subject: configure and cpp problem (Was: bug: missing include files in
> B20.1)
>      From: Teun Burgers <burgers@ecn.nl>
>      Date: Mon, 22 Feb 1999 16:52:09 +0100
>
> But I seems to me the one DO NOT need it (but I kept it, just in case). You
> might have a look anyway.

Hmmm....here's the relevant part of Teun Burgers' post:

> The configure script (relevant part in fhdr.old) creates
> a script findhdr that looks for the header file. findhr first
> simply tests for existance (test -f) of the .h file in
> H-i586-cygwin32/i586-cygwin32/include and if not found there
> it uses the C preprocessor gcc -E -.
>
Except the script says "$usrinc/\$wanted" which fails for a different reason on my
system: $usrinc is a pathlist, not a single path. However, this doesn't seem to
cause a problem, because the second step works....

>
> Because stdarg.h is not found in the first step it must be found
> in the second step. This second step goes wrong for two reasons:
>
> 1) the shell scripts tests whether the expanded include file
>    name by gcc -E matches */stdarg.h. This test fails because
>    gcc returns a DOS filename with \ e.g.
>    d:\\cygnus\\cygwin-b20  etc, so it does not match.
>
The egcs-1.1.1 returns
"F:/cygnus/cygwin-b20/usr/bin/../lib/gcc-lib/i586-cygwin32/egcs-2.91.60/include/stdarg.h"
so the match succeeds. However, the correction to the search regex will work in
both cases.

>
>    There are two solutions:
>    - change the matching condition in findhdr from
>      */stdarg.h  to  *[/\\]stdarg.h
>    - make gcc -E - return a unixy file name
>
> 2) Even with this test fixed it still goes wrong.
>    This seems to be a bug in the configure script.
>    The configure scripts sets variable name in a while
>    loop that is the end of a pipe. Because the while is
>    in a pipe, it runs in a subshell and variable settings
>    are local to that subshell.
>
????. I understand the theory, but my build seemed to work okay. However, I don't
see how including Mr. Burgers' fixes will hurt anything, so I'll go ahead an add
them to the "patch", unless anyone can think of a good reason not to.

> *) Furthermore, I'd just add that I had some problems while building perl
> if source files were extracted in a binary mounted partition. BUT I also
> read some testimony regarding the contrary (i.e. you need to mount it as
> binary) ! Therefore, It's just a hint, but if you experience some problems
> (sadly, I forgot to save the error messages), try different mount mode.

I extracted into a binary mounted partition. My *guess* is that you might have
used WinZip or somesuch to extract the source. If WinZip converted all newlines to
\013\010, AND the partition was mounted binary, then that would cause problems.

> *) make test
>
> Here is the result after applying your modifications :
>
> > make test
> Failed 7 test scripts out of 186, 91.40% okay.

> >cd t
> >perl harness
>
> Failed Test  Status Wstat Total Fail  Failed  List of failed
> -------------------------------------------------------------------------------
> io/fs.t                      26    4  15.38%  5, 7, 9-10
> lib/anydbm.t      2   512    12    9  75.00%  2, 5-12
> lib/findbin.t                 1    1 100.00%  1
> lib/sdbm.t        2   512    18   15  83.33%  2, 5-18
> op/magic.t                   35    1   2.86%  23
> op/stat.t                    58    6  10.34%  2, 9, 19-20, 26, 35
> op/taint.t                  149    3   2.01%  1, 3, 31
> 9 tests skipped, plus 20 subtests skipped.
> Failed 7/186 test scripts, 96.24% okay. 39/6193 subtests failed, 99.37% okay.
>
> (anydbm and sdbm might be different if you mounted your partition as binary).

Yup, they are different. Here's my output, *without* your changes to the testing
scripts.

>make test
Failed 4 test scripts out of 186, 92.47% okay.
>cd t
>perl harness

Failed Test  Status Wstat Total Fail  Failed  List of failed
-------------------------------------------------------------------------------
lib/findbin.t                 1    1 100.00%  1
op/magic.t                   35    1   2.86%  23
op/stat.t                    58    2   3.45%  4, 35
op/taint.t                  149    3   2.01%  1, 3, 31
10 tests skipped, plus 20 subtests skipped.
Failed 4/186 test scripts, 97.85% okay. 7/6191 subtests failed, 99.89% okay.

(skipped tests: lib/thread, lib/posix, lib/odbm, lib/ndbm, lib/ipc_sysv, lib/gdbm,
lib/db-recno, lib/db-hash, lib/db-btree, op/groups)

Now, all three of your patches address problems I didn't see; the main difference
between us being binary vs. text mounts. If that is the case, should these tests
be skipped for all cygwin (binary and text mount) or should the tests be fixed so
that they work for both binary and text mounts? I'm not sure if the second option
means hacking the test scripts, or hacking perl itself.

> Some of them just fail because they should NOT be executed in a win32
> implementation. They should be skipped. Sadly, the test behind this does
> NOT handle cygwin32 environment, just plain MS32 by comparing OS name to
> MSWin32 ($^O eq 'MSWin32'). Let's add a test for cygwin ($^O =~ /cygwin/).
> Here is a couple of tests I think that might be patched (I could not do
> anything for magic.t, as well as stat.t, which is a known problem) :
>
> <SNIP>
>
> > make test
> Failed 6 test scripts out of 186, 91.40% okay.
>
> > cd t
> > perl harness
>
> Failed Test  Status Wstat Total Fail  Failed  List of failed
> -------------------------------------------------------------------------------
> lib/anydbm.t      2   512    12    8  66.67%  5-12
> lib/findbin.t                 1    1 100.00%  1
> lib/sdbm.t        2   512    18   14  77.78%  5-18
> op/magic.t                   35    1   2.86%  23
> op/stat.t                    58    6  10.34%  2, 9, 19-20, 26, 35
> op/taint.t                  149    3   2.01%  1, 3, 31
> 10 tests skipped, plus 22 subtests skipped.
> Failed 6/186 test scripts, 96.77% okay. 33/6167 subtests failed, 99.46% okay.
>
> Which is slightly better :)

--Chuck


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Sebastien Barre]

At 22:04 04/03/99 -0500, Allan Peda wrote:

>Has there been much success with this?  I've done it with MSVC + nmake,
>but I'd get more of a thrill using cygwin.

I did (5.005_002  static build, 91.4% successfull test).

As many people from this list helped me, I'd glad to offer the same. 

Basically, 

*) Read the README.cywin32

*) Edit the hints/cygwin32.sh file to reflect your paths.

Here are also a couple of settings I found useful when performing automatic
build (copy hints/cygwin32.sh to config.sh, and do sh Configure -d)

usedl='n'
i_stdarg='define'
i_varargs='undef'
osname='cygwin_nt-4.0'
osvers='20.1'
archname='cygwin32'
signal_t='int'
d_voidsig='define'
i_sysselct='undef'
signal_t='void'

*) Browse Usenet archives (DejaNews), and find  "HOWTO: Builiding Perl
under Win95/98 using Cygwin32 " 
Steven Morlock <newspost@morlock.net>
1998/12/21
comp.lang.perl.misc

*) Then apply this patch (Thanks to Todd Goodman)

This is my change in Cwd.pm:
--- cwd.pm	Fri Feb 26 21:52:42 1999
+++ cwd.pm.orig	Fri Jan 22 20:49:54 1999
@@ -208,8 +208,6 @@
     my $start = @_ ? shift : '.';
     my($dotdots, $cwd, @pst, @cst, $dir, @tst);
 
-    return cwd() if ( $^O =~ /cygwin/ );
-
     unless (@cst = stat( $start ))
     {

And tell me (email) if it fails.

______________________________________________________________
Sebastien Barre                  http://www.hds.utc.fr/~barre/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Charles Wilson]

Sebastien Barre wrote:

> At 13:27 06/03/99 -0500, Charles Wilson wrote:
>
> >BTW, did you apply the patch to a
> >pristine copy of the source, or had you already applied the changes from Teun
> >Burgers (below)?
>
> No, from the pristine copy of course :) My perl is working quite right I
> guess, I just wanted to help you controlling your build package, so I
> started from the beginning, following your statements.

I was fairly sure that was the case, but it's best to eliminate the simple things
first.

> <snip>

> Therefore, I guess that this information

> *definitely* need a place in your build instructions : egcs 1.1.1 might be
> handy.
>

Okay. I'll update the build-kit soon.

> <snip>

> >However, I

> >don't see how including Mr. Burgers' fixes will hurt anything, so I'll go
> ahead an
> >add them to the "patch", unless anyone can think of a good reason not to.
>
> I tried, but was unable to find the relevant part to patch.
>

I found the relevant part, and have changed the build-kit to include this patch.
Even though it probably doesn't matter if you're using egcs-1.1.1.

>
> >> *) Furthermore, I'd just add that I had some problems while building perl
> >> if source files were extracted in a binary mounted partition. BUT I also
> >> read some testimony regarding the contrary (i.e. you need to mount it as
> >> binary) ! Therefore, It's just a hint, but if you experience some problems
> >> (sadly, I forgot to save the error messages), try different mount mode.
>
> >I extracted into a binary mounted partition. My *guess* is that you might have
> >used WinZip or somesuch to extract the source. If WinZip converted all
> >newlines to \013\010, AND the partition was mounted binary, then that
> would cause problems.
>
> Nope, I'm aware of the Winzip problem, and I'm taking care of that, by
> systematically using tar / gzip :)

Well, then I'm stumped. I don't know what the *build* problem is (or even if there
is one, after applying all these patches) under text / binary mounts. *make test*
problems are a whole different kettle of fish....continued in next message.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Compiling Perl under b20.1

[Charles Wilson]

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

I've taken Sebastien Barre's suggestions and Steven Morlock's instructions and
successfully compiled perl5.005_02 under Cygwin B20.1 and WinNT4sp4. I took
all their suggestions and created a patch file and collected the instructions
together in the attached package (6kB). It can also be downloaded from

ftp://belgarion.resnet.gatech.edu/pub/cygwin/B20/perl-cygwin-instructions.tar.gz

Yoiu can also find a binary distribution of perl at the same location:

ftp://belgarion.resnet.gatech.edu/pub/cygwin/B20/perl5.005_02-cygwinb20.tar.bz2

It's 2.6Meg, unpack from /. It will install into /usr/local/bin/,
/usr/local/man/, /usr/local/lib/, and a few text files into
/usr/local/src/perl5.005_02/. The ftp server has been up & down a lot lately,
please be patient.

Please comment on both the collected build instructions and the binary
distribution.

Thanks,
Chuck Wilson


[-- Attachment #2: perl-cygwin-instructions.tar.gz --]
[-- Type: application/x-gzip, Size: 6208 bytes --]