Hi Zack, "Zack Weinberg" <z...@owlfolio.org> skribis:
> The Guile packages currently install all their binaries under their > basic name only, e.g. > > $ ls /gnu/store/4gvgcfdiz67wv04ihqfa8pqwzsb0qpv5-guile-3.0.9/bin > /gnu/store/4gvgcfdiz67wv04ihqfa8pqwzsb0qpv5-guile-3.0.9/bin: > guild guile guile-config guile-snarf guile-tools > > However, the Autoconf macro GUILE_PROGS (from guile.m4) looks first > for a guile binary with a version number suffix (e.g. ‘guile-3.0’). > If it finds one, then it looks *only* for a matching guild-X.Y and > errors out if it can’t find that. This is a problem for building Guix > itself from source in a non-pure ‘guix shell -D guix’ on top of a > foreign distro that provides a ‘guile-3.0’ binary but not the other > four programs: I think the solution is to use ‘guix shell -D guix -CP’: that’ll give you a container, where /usr/bin/guile-3.0 isn’t accessible, which ensures there’s no interference. (FWIW this is what I do, even on Guix System, for my development environments.) Does that work for you? If your distro doesn’t support unprivileged user namespaces, which ‘-C’ relies on, you can fall back to ‘--pure’. Ludo’.