Build the toolchain using 9.2 first, configuring with --disable-default-plugins. Then build the whole system from the toolchain, configuring with --with-scheme-build=../toolchain (or whatever).
If you make source changes and want to update both, run make in the toolchain build, then run it again in the full build. On Wed, Oct 24, 2018 at 7:35 PM Taylor R Campbell <campb...@mumble.net> wrote: > > Date: Thu, 25 Oct 2018 02:12:04 +0000 > > From: Taylor R Campbell <campb...@mumble.net> > > > > Can you avoid using what doesn't exist in 9.2 in the build, and pass > > --no-init-file? > > Sorry, missed the part of your mail about having to do a manual > multi-stage build to make this work on 9.2. > > Can't build x11 before mit-scheme.h is installed: > > --- x11-shim.lo --- > libtool: compile: gcc "-DPACKAGE_NAME=\"MIT/GNU Scheme x11 plugin\"" > -DPACKAGE_TARNAME=\"mit-scheme-x11\" -DPACKAGE_VERSION=\"1.2\" > "-DPACKAGE_STRING=\"MIT/GNU Scheme x11 plugin 1.2\"" -DPACKAGE_BUGREPORT=\" > bug-mit-sch...@gnu.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"mit-scheme-x11\" > -DVERSION=\"1.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 > -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -DHAVE_MALLOC_H=1 -I. > -I/home/riastradh/scheme/mit/git/master/src/root/lib/mit-scheme-x86-64/ > -Wall -Wundef -Wpointer-arith -Winline -Wstrict-prototypes -Wnested-externs > -Wredundant-decls -Wextra -Wno-sign-compare -Wno-unused-parameter > -Wold-style-definition -Wunreachable-code -Wwrite-strings > -I/usr/X11R7/include -g -O2 -MT x11-shim.lo -MD -MP -MF .deps/x11-shim.Tpo > -c x11-shim.c -fPIC -DPIC -o .libs/x11-shim.o > x11-shim.c:3:24: fatal error: mit-scheme.h: No such file or directory > compilation terminated. > *** [x11-shim.lo] Error code 1 > > Not sure what the right way to deal with this is. I can work around > it now by making compile-x11 depend on stamp_install-microcode, but > it's bad form for one build target to depend on another install > target. On the other hand, these are effectively separate projects > with interdependencies on installation now, so... >
_______________________________________________ MIT-Scheme-devel mailing list MIT-Scheme-devel@gnu.org https://lists.gnu.org/mailman/listinfo/mit-scheme-devel
