Hi Alexander!

The file /usr/lib/ld-linux-x86-64.so.2 is used instead of the expected 
/home/akobel/gub/gub/target/linux-64/root/usr/lib/ld-linux-x86-64.so.2.

Could you please execute

    ls -l `find -L /lib* /usr /home/akobel/gub | grep ld-linux-x86-64.so.2`

and mail me the result?

Sure, that'd be

lrwxrwxrwx 1 akobel akobel 11 31. Jan 17:32 
/home/akobel/gub/gub/target/linux-64/root/lib64/ld-linux-x86-64.so.2 -> 
ld-2.3.6.so
lrwxrwxrwx 1 root   root   10 11. Okt 10:18 /lib64/ld-linux-x86-64.so.2 -> 
ld-2.28.so
lrwxrwxrwx 1 root   root   10 11. Okt 10:18 /lib/ld-linux-x86-64.so.2 -> 
ld-2.28.so
lrwxrwxrwx 1 root   root   10 11. Okt 10:18 /usr/lib64/ld-linux-x86-64.so.2 -> 
ld-2.28.so
lrwxrwxrwx 1 root   root   10 11. Okt 10:18 /usr/lib/ld-linux-x86-64.so.2 -> 
ld-2.28.so

and /usr/lib/ld-2.28.so is part of the glibc package.

In case you wonder, on Arch both /lib and /lib64 are symlinked to /usr/lib; 
they also abandoned the distiction between /bin, /sbin, /usr/sbin and /usr/bin, 
and the former three are symlinked to the latter.

Ok, that's an important difference to other linux systems:

Could it be that

   bin/gub --fresh darwin-ppc::guile darwin-x86::guile freebsd-64::guile 
freebsd-x86::guile linux-ppc::guile mingw::guile tools::guile

succeeds and that

   bin/gub --fresh linux-x86::guile
   bin/gub --fresh linux-64::guile

both fail? I think (hope) that

   bin/gub --fresh darwin-ppc::lilypond darwin-x86::lilypond 
freebsd-64::lilypond freebsd-x86::lilypond linux-ppc::lilypond mingw::lilypond

should also succeed in that case ...

Knut


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

Reply via email to