On 2025-04-26 08:22, Ian Eure wrote: > I have two patches I contributed which I need to make some > additional changes to, but which I can’t make progress on because > they fail to build. The failures are repeatable -- I can > replicate them every time, across multiple computers -- but not > /consistent/ -- the same code fails when built from a clean state, > but works if I build the base commit of the branch, then the HEAD. > > First bug -- #77653. Working state is in the wasm-toolchain > branch at https://codeberg.org/ieure/guix.git > > Symptom: `make clean && make' fails to build with: > > ice-9/eval.scm:293:34: error: clang-runtime-16: unbound > variable > hint: Did you forget a `use-modules' form? > > It’d be nice if this gave me a file/line for the problem, but the > only added mention of this package is in gnu/packages/wasm.scm, > where the wasm32-wasi-clang-runtime package inherits from it. The > clang-runtime-16 package is in (gnu packages llvm), is public, and > gnu/packages/wasm.scm uses (gnu packages llvm). If I load > wasm.scm in the Guix REPL, it works fine. If I build the base > commit of that branch (7ff20b9e94), then build the HEAD > (dd2172a054), it builds fine. It only fails when I `make clean && > make' on dd2172a054.
It might not help much, but sometimes this type of errors appear on my side when using some type of gexps, in particular things like using this-package-(native-)input when the argument string is not the exact expected name of the package. Pretty annoying indeed, the error printed in this case is usually unrelated. Maybe try bisecting/making more minimal changes? If you could find the culprit commit between 7ff20b9e94 and dd2172a054, it might be easier to see where such an error might have occured (that is, if the error you observe is indeed gexp-related). -- Best regards, Nicolas Graves
