Front page | perl.perl5.porters |
Postings from December 2003
Andy Dougherty <doughera@lafayette.edu> writes: >On Mon, 1 Dec 2003, David Nicol wrote: > >> okeydokey, repeating compilation experiment... >> >> /home/david/perl-5.8.2/Configure -Dcc=gcc -Dprefix=/opt/perl-5.8.2 >> -Dmksymlinks -d >> >> make runs a while and ends with this: >> >> ./miniperl -Ilib configpm configpm.tmp >> make[2]: *** [lib/Config.pm] Error 9 > >Ok, this is a sign that your miniperl has some serious trouble. I don't >know what, specifically, errno 9 (Bad File Number) is telling us, but it's >definitely not good. It isn't necessarily errno == 9 but $? == 9 which may mean signal 9 killed it. I have seem linux do equivalent of kill -9 when it runs out of resources in some vague sense. > >> You may see some irrelevant test failures if you have been unable >> to build lib/Config.pm or lib/lib.pm. >> >> cd t && (rm -f perl; /bin/ln -s ../miniperl perl) \ >> && ./perl TEST base/*.t comp/*.t cmd/*.t run/*.t io/*.t op/*.t uni/*.t >> </dev/tty >> make[1]: [minitest] Error 9 (ignored) > >Oh, dear. This is bad. None of the tests run. Usually, most of the >tests run successfully, and we can use the failed tests to track down >what's wrong with miniperl. > >Your next step is to try to run ./miniperl manually to see if you can get >it to fail more informatively. I'd suggest things like > > cd t > ./perl t/base.t > >and gradually build up to > > ./perl TEST base/*.t > >and ever more complex commands. > >> Summary of my perl5 (revision 5.0 version 8 subversion 2) configuration: >> Platform: >> osname=linux, osvers=2.6.0-test7, archname=i686-linux > >> gccversion='2.96 20000731 (Red Hat Linux 7.2 2.96-112.7.2)', > >> gnulibc_version='2.2.4' > >One vague possibility that comes to mind is that you are using a >pre-release test 2.6.0 kernel on a rather old system (glibc-2.2.4 and >gcc-2.96). Are you *sure* that this kernel and this libc work well >together?