> On Jan 24, 2018, at 1:57 PM, Eli Zaretskii <e...@gnu.org> wrote: > >> From: Matthew Keeter <matt.j.kee...@gmail.com> >> Date: Tue, 23 Jan 2018 21:18:17 -0500 >> Cc: guile-devel@gnu.org >> >> BOOTSTRAP GUILEC ice-9/eval.go >> ;;; note: source file >> C:/msys64/home/mkeeter/guile/src/guile-2.2.3/module/ice-9/boot-9.scm >> ;;; newer than compiled >> C:/msys64/home/mkeeter/guile/src/guile-2.2.3/prebuilt/32-bit-little-endian/ice-9/boot-9.go >> Backtrace: >> 8 (apply-smob/1 #<catch-closure 4fba0e0>) >> In ice-9/eval.scm: >> 657:36 7 (_ _) >> 619:8 6 (_ #(#(#<directory (guile-user) 4fdcb40>))) >> 155:9 5 (_ _) >> 619:8 4 (_ #(#(#(#(#(#(#(#(#(#(#(#) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒)) >> 159:9 3 (_ #(#(#(#(#(#(#(#(#(#(#(#) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒)) >> 223:20 2 (proc #(#(#(#(#(#(#(#(#(#(# ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒) ▒)) >> In unknown file: >> 1 (%resolve-variable (7 . SIGINT) #<directory (scripts co▒>) >> 0 (_ #<procedure 62ef720 at ice-9/eval.scm:330:13 ()> #<▒> ▒) >> >> ERROR: Unbound variable: SIGINT >> >> If I boot up the interpreter, it too does not know about SIGINT: >> >> mkeeter@MATTHEWKEETA8AA MINGW32 ~/guile/src/build-i686-w64-mingw32 >> $ GUILE_AUTO_COMPILE=0 >> GUILE_LOAD_PATH=/home/mkeeter/guile/src/guile-2.2.3/module >> ./meta/build-env guile >> GNU Guile 2.2.3 >> Copyright (C) 1995-2017 Free Software Foundation, Inc. >> >> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'. >> This program is free software, and you are welcome to redistribute it >> under certain conditions; type `,show c' for details. >> >> Enter `,help' for help. >> scheme@(guile-user)> SIGINT >> ice-9/eval.scm:619:8: In procedure module-lookup: Unbound variable: SIGINT >> >> On my Mac, the variable is defined (and has a value of 2). > > You should grep the libguile directory for "SIGINT" and make sure the > file(s) involved in defining that variable are compiled in your build. > (The MinGW port of Guile 2.0.11 I have here does know about SIGINT, > FWIW.) > >> I believe the odd printing is a quirk of the MinGW terminal – it certainly >> doesn’t help in >> debugging, but I think the fundamental issue here is Guile not knowing about >> SIGINT. > > Yes, but you should also look into the printing issue, as that > shouldn't happen. It's a problem of some sort, perhaps Guile thinks > your terminal is UTF-8 capable or something.
Well, that was an obvious problem: I had configured the build with --without-posix, which I guess is no longer supported. Unfortunately, the rebuild is now back to having trouble with building the documentation, with the same error as before: ERROR: In procedure primitive-load-path: In procedure primitive-load-path: Unable to find file "C:/msys64/home/mkeeter/guile/src/build-i686-w64-mingw32/libguile/C:/msys64/home/mkeeter/guile/src/build-i686-w64-mingw32/meta/guild" in load path Time to strap a bunch of instrumentation onto load.c and see where this is coming from… -Matt
