Hi Ludo, On lun., 06 mai 2024 at 11:34, Ludovic Courtès <l...@gnu.org> wrote:
>>> - stage0) >>> GUILE_LOAD_COMPILED_PATH="${top_builddir}/stage0:${top_srcdir}/prebuilt/@SCM_PREBUILT_BINARIES@" >>> ;; >>> + stage0) >>> GUILE_LOAD_COMPILED_PATH="${top_srcdir}/prebuilt/@SCM_PREBUILT_BINARIES@:${top_builddir}/stage0" >>> ;; > > I don’t understand why changing the order would make a difference. > Surely if .go files are available under prebuilt/, they’ll be found, > even if that directory comes second? Or am I missing something? Well, depending on what had been built before, it might read: --8<---------------cut here---------------start------------->8--- $ ls -1 {stage0,prebuilt/x86_64-unknown-linux-gnu}/ice-9/{boot-9,eval,psyntax-pp}.go prebuilt/x86_64-unknown-linux-gnu/ice-9/boot-9.go prebuilt/x86_64-unknown-linux-gnu/ice-9/eval.go prebuilt/x86_64-unknown-linux-gnu/ice-9/psyntax-pp.go stage0/ice-9/boot-9.go stage0/ice-9/eval.go stage0/ice-9/psyntax-pp.go --8<---------------cut here---------------end--------------->8--- Therefore, the order in GUILE_LOAD_COMPILED_PATH matters, no? Somehow, similarly as: stage1) GUILE_LOAD_COMPILED_PATH="${top_builddir}/stage1:${top_builddir}/stage0" ;; I would set the expected most optimized first, such that: stage0) GUILE_LOAD_COMPILED_PATH="${top_srcdir}/prebuilt/@SCM_PREBUILT_BINARIES@:${top_builddir}/stage0" ;; assuming ’prebuilt’ provides something more optimized than ’stage0’. Cheers, simon