[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-users] Dramas installing Perl 5.6 or 5.8 on a Raq4i



On Mon, 2003-09-15 at 19:51, H.P. Noordam wrote:
> > 
> > 
> > Hi all,
> > 
> > Firstly I have managed to get Perl 5.8.0 installed on our
> > (production) Raq4i in the fashion quoted in other posts.
> > but with side effects.
> > Using:
> > [Method 1]
> > http://cobalt.depopo.net/html/q3__perl5_8.html
> > 
> > I have also managed to install (on our test machine) perl 
> > 5.6.1 using the information here: Which replaces the Raq4 
> > perl for the interface. [Method 2] 
> > http://www.nuonce.net/cobalt-perl.php
> > No problems there.
> > 
> > But the problem I have had is when doing the "make test"
> > some of the tests fail, typically 3 or 4 out of like 300.
> > So I was wary of installing 5.6 [Method 2] on the production 
> > server not knowing if it would be a problem.
> > 
> > So, I did it by ignoring the "make test" failures using the 
> > 5.8.0 [Method 1], it is all ok  But the scripts that run on 
> > 5.8 have to omit the "-w" to work eg: #!/usr/bin/perl580
> > 
> > when installing this is the error that comes up allot, but 
> > I'm not sure if this is related to the installation problem: 
> > "Can't ignore signal CHLD, forcing to default." I have 
> > searched this topic and I understand the idea of it, but I 
> > don't understand how it causes the failures or why its there 
> > at all Oh yeah the "test machine" is a clone of the 
> > "production server" about 2 weeks ago :|
> > 
> > SELECTED INFO FROM "make test" [Method 1] - cropped cause its 
> > big otherwise
> > :)
> > 
> > [root root]# cd perl-5.8.0/
> > [root perl-5.8.0]# make test
> > //XXXXXXXXXXXXXXXXXXX break XXXXXXXXXXXXXXXXXXXXX 
> > t/cmd/subval.........................ok
> > t/cmd/switch.........................ok
> > t/cmd/while..........................ok
> > t/run/exit...........................ok
> > t/run/fresh_perl.....................# PROG:
> > #
> > # $| = 1;
> > # sub foo {
> > #     print "In foo1\n";
> > #     eval 'sub foo { print "In foo2\n" }';
> > #     print "Exiting foo1\n";
> > # }
> > # foo;
> > # foo;
> > # EXPECTED:
> > # In foo1
> > # Subroutine foo redefined at (eval 1) line 1.
> > # Exiting foo1
> > # In foo2
> > # GOT:
> > # Can't ignore signal CHLD, forcing to default.
> > # In foo1
> > # Subroutine foo redefined at (eval 1) line 1.
> > # Exiting foo1
> > # In foo2
> > # STATUS: 0
> > # Failed at ./test.pl line 567
> > FAILED at test 42
> > t/run/noswitch.......................ok
> > t/run/runenv.........................# Test 1 got: '' 
> > (run/runenv.t at line
> > 77)
> > #   Expected: '1' (Stderr mismatch: expected [Name "main::x" 
> > used only once:
> > possible typo at -e line 1.\nUse of uninitialized value in 
> > print at -e line 1.\n], saw [Can't ignore signal CHLD, 
> > forcing to default.\nName "main::x" used only once: possible 
> > typo at -e line 1.\nUse of uninitialized value in print at -e 
> > line 1.\n]) FAILED at test 1 t/run/switchF........................ok
> > t/run/switchPx.......................ok
> > t/run/switcha........................ok
> > //XXXXXXXXXXXXXXXXXXX break XXXXXXXXXXXXXXXXXXXXX 
> > t/op/chdir...........................ok
> > t/op/chop............................ok
> > t/op/closure.........................Can't ignore signal 
> > CHLD, forcing to default. Can't ignore signal CHLD, forcing 
> > to default. Can't ignore signal CHLD, forcing to default. 
> > Can't ignore signal CHLD, forcing to default. Can't ignore 
> > signal CHLD, forcing to default. Can't ignore signal CHLD, 
> > forcing to default. Can't ignore signal CHLD, forcing to 
> > default. Can't ignore signal CHLD, forcing to default. Can't 
> > ignore signal CHLD, forcing to default. Can't ignore signal 
> > CHLD, forcing to default. Can't ignore signal CHLD, forcing 
> > to default. Can't ignore signal CHLD, forcing to default. 
> > Can't ignore signal CHLD, forcing to default. Can't ignore 
> > signal CHLD, forcing to default. Can't ignore signal CHLD, 
> > forcing to default. Can't ignore signal CHLD, forcing to 
> > default. Can't ignore signal CHLD, forcing to default. Can't 
> > ignore signal CHLD, forcing to default. ok 
> > t/op/cmp.............................ok
> > t/op/concat..........................ok
> > //XXXXXXXXXXXXXXXXXXX break XXXXXXXXXXXXXXXXXXXXX 
> > ext/B/t/debug........................ok
> > ext/B/t/deparse......................FAILED at test 17 
> > ext/B/t/lint.........................ok
> > //XXXXXXXXXXXXXXXXXXX break XXXXXXXXXXXXXXXXXXXXX 
> > ext/File/Glob/t/taint................ok
> > ext/Filter/t/call....................FAILED at test 2 
> > ext/GDBM_File/gdbm...................ok
> > //XXXXXXXXXXXXXXXXXXX break XXXXXXXXXXXXXXXXXXXXX 
> > lib/CPAN/t/Nox.......................ok
> > lib/CPAN/t/vcmp......................ok
> > lib/DB...............................ok
> > lib/Devel/SelfStubber................Can't ignore signal 
> > CHLD, forcing to default. Can't ignore signal CHLD, forcing 
> > to default. ok lib/diagnostics......................ok
> > lib/Digest...........................ok
> > //XXXXXXXXXXXXXXXXXXX break XXXXXXXXXXXXXXXXXXXXX 
> > lib/warnings.........................Can't ignore signal 
> > CHLD, forcing to default. Can't ignore signal CHLD, forcing 
> > to default. Can't ignore signal CHLD, forcing to default. 
> > Can't ignore signal CHLD, forcing to default. Can't ignore 
> > signal CHLD, forcing to default. Can't ignore signal CHLD, 
> > forcing to default. Can't ignore signal CHLD, forcing to 
> > default. Can't ignore signal CHLD, forcing to default. Can't 
> > ignore signal CHLD, forcing to default. Can't ignore signal 
> > CHLD, forcing to default. Can't ignore signal CHLD, forcing 
> > to default. Can't ignore signal CHLD, forcing to default. 
> > Can't ignore signal CHLD, forcing to default. Can't ignore 
> > signal CHLD, forcing to default. Can't ignore signal CHLD, 
> > forcing to default. Can't ignore signal CHLD, forcing to 
> > default. Can't ignore signal CHLD, forcing to default. Can't 
> > ignore signal CHLD, forcing to default. Can't ignore signal 
> > CHLD, forcing to default. Can't ignore signal CHLD, forcing 
> > to default. Can't ignore signal CHLD, forcing to default. 
> > Can't ignore signal CHLD, forcing to default. Can't ignore 
> > signal CHLD, forcing to default. Can't ignore signal CHLD, 
> > forcing to default. Can't ignore signal CHLD, forcing to 
> > default. Can't ignore signal CHLD, forcing to default. Can't 
> > ignore signal CHLD, forcing to default. Can't ignore signal 
> > CHLD, forcing to default. Can't ignore signal CHLD, forcing 
> > to default. Can't ignore signal CHLD, forcing to default. 
> > Can't ignore signal CHLD, forcing to default. ok 
> > t/pod/emptycmd.......................ok
> > //XXXXXXXXXXXXXXXXXXX break XXXXXXXXXXXXXXXXXXXXX 
> > t/x2p/s2p............................ok
> > Failed 4 test scripts out of 665, 99.40% okay.
> > ### Since not all tests were successful, you may want to run 
> > some of ### them individually and examine any diagnostic 
> > messages they produce. ### See the INSTALL document's section 
> > on "make test". ### You have a good chance to get more 
> > information by running
> > ###   ./perl harness
> > ### in the 't' directory since most (>=80%) of the tests 
> > succeeded. ### You may have to set your dynamic library 
> > search path, ### LD_LIBRARY_PATH, to point to the build directory:
> > ###   setenv LD_LIBRARY_PATH `pwd`; cd t; ./perl harness
> > ###   LD_LIBRARY_PATH=`pwd`; export LD_LIBRARY_PATH; cd t; 
> > ./perl harness
> > ###   export LD_LIBRARY_PATH=`pwd`; cd t; ./perl harness
> > ### for csh-style shells, like tcsh; or for 
> > traditional/modern ### Bourne-style shells, like bash, ksh, 
> > and zsh, respectively. u=8.93  s=1.96  cu=365.22  cs=63.24  
> > scripts=665  tests=68511
> > make[2]: *** [_test_tty] Error 1
> > make[2]: Leaving directory `/home/root/perl-5.8.0'
> > make[1]: *** [_test] Error 2
> > make[1]: Leaving directory `/home/root/perl-5.8.0'
> > make: *** [test] Error 2
> > [root perl-5.8.0]#
> > 
> > --
> > Thanks
> > Jonathan Buckland
> > SIAB
> > 
> > 
> > 
> > ---
> 
> 
> Hi,
> 
> Method 1 was intended for qube´s only, i´ll take a look at it sometime to add a proper howto for the raq series.
> Anyway, if you run a simple /urs/sbin/perl580 --version  does that also result in the message ? Or does that give proper output ?
> 
> There seem to be more reports of this problem. While the message indicated problems with a wrapper, shell, or cron-like script initiator, sometimes even the version request yields incorrect results, which might indicate problems and compiletime. Is the machine you used to compile the program a "real and original"  raq4, or an other cobalt with a newer os, (possible speed upgrade etc etc). 
> 
> Bob.

Bob,

I did leave out some info, because I was trying to get the post smaller.
I always test an install on my test machine first, so i did an install
of [Method 1] on the test machine, NO problems, that is, it fully works
with the scripts I installed it for. I recommend [Method 1] as a
solution on a raq4i.  
 
#!/usr/bin/perl580 -w  (also works, [test Machine] _not_ [production
server])

So the really crux of the question is why our production server doesn't
like to compile perl, 5.6.1 or 5.8.0 (fails "make test")

On both machines I can install perl modules using the "perl580 -MCPAN -e
'install Bundle::DBI' for example.
And the production server is working with the >5.6.1 perl script as
well.

//XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[root root]# /usr/bin/perl580 -v

This is perl, v5.8.0 built for i586-linux

Copyright 1987-2002, Larry Wall

Perl may be copied only under the terms of either the Artistic License
or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using `man perl' or `perldoc perl'.  If you have access to
the
Internet, point your browser at http://www.perl.com/, the Perl Home Page
//XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

--
Jonathan