Op vrijdag 14-11-2008 om 22:58 uur [tijdzone +0100], schreef John Mandereau:
Hi John, > On 2008/11/12 21:43 +0100, Jan Nieuwenhuizen wrote: > > John Mandereau: > > > CPP='x86_64-linux-gcc -E -x c-header' > > > /home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/elf/ld-linux-x86-64.so.2 > > > --library-path > > > /home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3:/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/math:/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/elf:/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/dlfcn:/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/nss:/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/nis:/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/rt:/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/resolv:/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/crypt:/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/linuxthreads > > > > > > /home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/sunrpc/rpcgen > > > -Y ../scripts -c rpcsvc/bootparam_prot.x -o > > > /home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/sunrpc/xbootparam_prot.T > > > make[4]: *** > > > [/home/lilydev/git/newgub/target/linux-64/build/glibc-core-2.3/sunrpc/xbootparam_prot.stmp] > > > Floating point exception > > > > Ugh. Is this reproducible? What if you run the command manually? Make > > sure to set > > the path, ie, run > > > > PATH=/home/lilydev/git/newgub/target/linux-64/root/usr/cross/bin:$PATH > > CPP='x86.... rpcgen -Y ... > > If I run the ld-linux-x86-64.so.2 command above manually with the PATH > you suggested, it exits successfully. Producing the xbootparam_prot.T file? Can you manually continue make from that point, ie PATH=/home/lilydev/...:$PATH make > I tried to rebuild glibc-core > with "rm ...status; make lilypond" twice, and I even did "rm -rf > target/linux-64; make lilypond", but it didn't help, I got the same > crash again. Unlike first time I got this crash, I ran the compilations > on an idle system with Firefox and my email-client opened. > I'll try to call make commands manually later... if I manage to > reproduce GUB in the shell. Ok, great. In the meantime, still som GUB hacking going on here, expect another batch of updates RSN. Think I found your weird rm -f .. libiberty thing. > 4 GB RAM, Intel Core 2 Duo at 3,17 GHz, Fedora 9 64-bit, Linux 2.6.26.6. okay ..., nothing like 256 Mb swap going OOM. Otoh, I heard Linux 2.7.27.5 is really awesome. ;-) > It doesn't help, a similar crash happens, with exactly the same > floating > point exception error message. This crash seems not to be related > with > the CPU load. And at exactly the same command? Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
