On Mon, 2022-03-28 at 21:14 +0200, Jean Abou Samra wrote: > Le 28/03/2022 à 21:10, Jonas Hahnfeld via LilyPond user discussion a écrit : > > Correct, the relocation doesn't follow symlinks, I've opened > > https://gitlab.com/lilypond/lilypond/-/issues/6314 For the time being, > > you'll need to create a wrapper shell script that just calls lilypond > > with its full path. > > Relatedly, I am seeing hardcoded paths apparently coming from > your computer in the binaries. Is that expected? > > $ ~/lilypond2.23.7/bin/lilypond scheme-sandbox > [...] > scheme@(#{ g102}#)> %load-path > $1 = ("/home/jean/lilypond2.23.7/share/lilypond/2.23.7/scm" > "/home/jean/lilypond2.23.7/share/guile/2.2" > "/home/lily/lilypond-2.23.7/release/binaries/dependencies/install/guile-2.2.7/share/guile/2.2" > > "/home/lily/lilypond-2.23.7/release/binaries/dependencies/install/guile-2.2.7/share/guile/site/2.2" > > "/home/lily/lilypond-2.23.7/release/binaries/dependencies/install/guile-2.2.7/share/guile/site" > > "/home/lily/lilypond-2.23.7/release/binaries/dependencies/install/guile-2.2.7/share/guile")
Yes, it's the place where I build the binaries in my VM. I think you can partly see the same with the GUB binaries. Not for %load-path though, where it actually includes /usr/share/guile/1.8 from the system, which is arguably worse - including a non-existing path at least doesn't do any harm. At some point, I'll maybe go through all dependencies and teach them that they should forget about the place where they were built / installed. Jonas
signature.asc
Description: This is a digitally signed message part
