Hi,

On 02.02.19 10:27, Knut Petersen wrote:
On 01.02.19 15:06, Alexander Kobel wrote:
On 01.02.19 14:51, Alexander Kobel wrote:
GUB-bing further down the road now...

Hrmpf, back here sooner than I hoped.
Guile barfed - see the attached log.

libtool: link: x86_64-linux-gcc -g -O2 -Wall -Wmissing-prototypes -o .libs/guile guile-guile.o  ./.libs/libguile.so /home/akobel/gub/gub/target/linux-64/root/usr/lib/libgmp.so -lcrypt -lm /home/akobel/gub/gub/target/linux-64/root/usr/lib/libltdl.so -ldl -Wl,-rpath -Wl,/usr/lib -Wl,-rpath -Wl,/home/akobel/gub/gub/target/linux-64/root/usr/lib /home/akobel/gub/gub/target/linux-64/root/lib64/libc.so.6: undefined reference to `_dl_out_of_memory@GLIBC_PRIVATE' collect2: error: ld returned 1 exit status

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?


Cheers,
Alex

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to