Hi! Christopher Allan Webber <[email protected]> writes:
> Jan Nieuwenhuizen writes: > >> While building guile2.2-gdbm-ffi an error is printed that does not >> prevent the package from being built >> >> @ build-started >> /gnu/store/z9m20fz1ayyl0g9b4ad6wgmq3fv2h7gi-guile2.2-gdbm-ffi-20120209.fa1d5b6.drv >> - x86_64-linux >> /var/log/guix/drvs/z9//m20fz1ayyl0g9b4ad6wgmq3fv2h7gi-guile2.2-gdbm-ffi-20120209.fa1d5b6.drv.bz2 >> ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0 >> ;;; or pass the --no-auto-compile argument to disable. >> ;;; compiling >> /gnu/store/d3gli8g5bv6yhd3qwk5rfzqpsfvnj4lv-guile-next-2.1.5/bin/guild >> ;;; WARNING: compilation of >> /gnu/store/d3gli8g5bv6yhd3qwk5rfzqpsfvnj4lv-guile-next-2.1.5/bin/guild >> failed: >> ;;; ERROR: failed to create path for auto-compiled file I've notice this same problem recently while looking at the build-log of our GnuCash package.. It seems to be the problem is caused by the Guile wanting to auto-compile the guild script, and not being able to as it wants to store the compiled version somewhere under $HOME. Could a generally applicable solution be to distribute a pre-compiled guild.go in the store, so that it would use that and never attempt to 'auto-compile' it? This would effectively fix this problem for good without having to create workaround such as using environment variables or setting HOME to a temp dir. WDYT? Maxim
signature.asc
Description: PGP signature
