Am So., 8. März 2020 um 13:37 Uhr schrieb David Kastrup <[email protected]>:
> We have a current issue that > has already bitten several not-completely-stupid developers I'm obviously one of the more stupid ones ;) I never understood how to use pkg-config, thus I always make the guile-version I need, the system-guile, i.e. sudo make install... Right now I've guile-1 system-wide and tried to compile current master with $ ../configure GUILE_CONFIG=/home/hermann/guile-2.2/meta/guile-config GUILE=/home/hermann/guile-2.2/meta/guile Obviously guile-2 was picked: checking for guile... /home/hermann/guile-2.2/meta/guile checking /home/hermann/guile-2.2/meta/guile version... 2.2.6.7 checking for /home/hermann/guile-2.2/meta/guile... /home/hermann/guile-2.2/meta/guile checking for /home/hermann/guile-2.2/meta/guile... /home/hermann/guile-2.2/meta/guile But I've got guile-1 (after 'make' finishd): $ lilypond-git scheme-sandbox GNU LilyPond 2.21.0 Processing `/home/hermann/lilypond-git/build/out/share/lilypond/current/ly/scheme-sandbox.ly' Parsing... guile> (version) "1.8.8" No warning or else... I've no clue what I should give configure instead of GUILE_CONFIG As said, I could make guile-2.2 the system-guile, but I would be interested how that pkg-stuff is supposed to work. Btw, deprecated or not, I see guile-config even in guile-3: ~$ /home/hermann/guile-3.0/meta/guile-config --version guile-config - Guile version 3.0.0.6-f3298 Cheers, Harm
