Hi Alexander!
The argumens given are ok. As usual
mkdir -p STRACE
strace -v -f -ff -s 10000 -o STRACE/TP bin/gub --fresh linux-64::guile
will help to identify the problem.
hm, that gives appx. 2 GB of traces, and I'm not sure which process' trace I
should look at. Nothing segfaults, so I don't get a PID hint as for the
previous problem.
Appx. 380 MB worth of traces contain the buzzwords out_of_memory; those
compress to 4.6 MB, so I could send them off-list?
In your log I read:
/home/akobel/gub/gub/target/linux-64/root/lib64/libc.so.6: undefined reference
to `_dl_out_of_memory@GLIBC_PRIVATE'.
As ld announces problems to stderr
grep _dl_out_of_memory@GLIBC_PRIVATE STRACE/* | grep 'write(2,'
will probably give exactly one match ... gub is writing to a file with fd!=2
and collect2 should only read ...
With STRACE/TP.xxxx changed to the match
grep '^execve' STRACE/TP.xxxx | grep -o '^[^,]*'
should result in
execve("/home/akobel/gub/gub/target/linux-64/root/usr/cross/bin/x86_64-linux-ld"
Please send that one file STRACE/TP.xxxx.... that's enough ;-)
Knut
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
