develooper Front page | perl.perl5.porters | Postings from April 2000

Re: [ID 20000407.001] failing to build 5.6.0

Thread Previous | Thread Next
Dominic Dunlop
April 7, 2000 03:21
Re: [ID 20000407.001] failing to build 5.6.0
Message ID:
At 10:26 +0200 2000-04-07, Lukas Karrer wrote:
>Configure: syntax error at line 590: `do' unexpected

Weird.  Apart from anything else, there's no `do' on or near that 
line of Configure or  I don't know what's up, but here 
are a few random thoughts (from a non-Sun user):

1. Maybe Configure picked up an old and/or which 
confused it.  Try rerunning Configure after deleting any files with 
these names from the source directory.

2. Maybe something's corrupted or truncated.  Here are the MD5 
checksums of some suspects on my system:

$ md5sum Configure *.SH
2129e17b572a5652021155a457f2c376 b Configure
659e958aba04136850c7fd8cccceb373 b Makefile.SH
488b5b40239b8d1e918a56b0a0e4b93f b Policy_sh.SH
68389c0a83934b408116730c75df756c b cflags.SH
a693de7093e98933c51460f94bcc0b3b b config_h.SH
a7ac59ee32d0936b5b506d18f073dfa7 b makeaperl.SH
94b9af9121fde66e3298f9c2b21ba4cf b makedepend.SH
808876092fcc169f0970ef9ff550383d b makedir.SH
c5e076b2fe93555c9b0ffcae1ca8a5a3 b myconfig.SH
378a80b1cbed1905a9d4d38f46a311bc b writemain.SH

3. Maybe your shell is the problem.  You could try saying  bash Configure ...
(or (ksh, or zsh -- whatever you have to hand) to see if that makes 
the problem go away.  That said, it would be odd if the shell were at 
fault: we've had a report of a successful build on a configuration 
which differs only very slightly from yours (assuming you're still 
using the box on which you built the 5.005_03 perl you used to submit 
the problem report):

Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration:

     osname=solaris, osvers=2.7, archname=sun4-solaris
     uname='sunos new-stinky 5.7 generic_106541-04 sun4u sparc sunw,ultra-5_10 '

Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:

     osname=solaris, osvers=2.7, archname=sun4-solaris
     uname='sunos husar 5.7 generic_106541-05 sun4u sparc 
sunw,ultra-enterprise '

for the full report.)

4. To see waht happened just before sh choked, you can try saying
sh -c Configure ... >configure.out2 2>&1
or sh -x Configure ... .  (Both are useful.  Depends on the bug.) 
Redirect  STDOUT and STDERR To a file as shown, then look at the 
voluminous debris later.

So, please try poking around some more, and tell us what you find.
Dominic Dunlop

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About