Hi Noah, Noah Lavine <noah.b.lav...@gmail.com> skribis:
> One idea I had been toying with is whether Guile could compile faster > if it had another copy of Guile already around, so it could skip the > portion of compile-time where the interpreter is running the compiler. > This is how most compilers do it - you want another C compiler around > to compile GCC, etc. I was afraid that this would result in a > too-complicated build system, but maybe not. Does anyone have > experience with implementing something like this? $GUILE_FOR_BUILD is used when cross-compiling Guile itself–i.e., a native Guile is needed to cross-build Guile. And according to <http://hydra.nixos.org/build/2517410>, Guile is cross-built in ~4m, whereas the native Guile itself is cross-built in ~40m. Now, using $GUILE_FOR_BUILD to build the native Guile itself would be tricky, because there’s no distinction between the run-time load path and the compiler’s search path (see ‘GUILE_CHECK_GUILE_FOR_BUILD’ in acinclude.m4.) Thanks, Ludo’.
