[Sbcl-help] Building on Windows

1 view
Skip to first unread message

Knut Arne Storeide

unread,
Jul 2, 2023, 12:07:28 PM7/2/23
to sbcl...@lists.sourceforge.net
Greetings all,

Since the official build for Windows hasn't been updated since version 2.3.2, I made an attempt at compiling on my own.

I have version 2.3.2 of sbcl installed in C:\tools\sbcl

In a fresh install of msys2 the following commands were run:

pacman -S make mingw-w64-ucrt-x86_64-gcc
export PATH=/c/tools/sbcl:$PATH
export SBCL_HOME=/c/tools/sbcl
tar xvf sbcl-2.3.6-source.tar.bz2
cd sbcl-2.3.6/
sh make.sh --prefix=/c/tools/sbcl-2.3.6 --dynamic-space-size=4Gb

The build is terminated while compiling gencgc.c, with the following error:

during RTL pass: pro_and_epilogue
gencgc.c: In function 'collect_garbage':
gencgc.c:4717:1: internal compiler error: in choose_baseaddr, at config/i386/i386.cc:7141
 4717 | }
      | ^
libbacktrace could not find executable to open
Please submit a full bug report, with preprocessed source (by using -freport-bug).
See <https://github.com/msys2/MINGW-packages/issues> for instructions.
make: *** [<builtin>: gencgc.o] Error 1
make: Leaving directory 'C:/Projects/sbcl-2.3.6/src/runtime'

The same error occurs with both the ucrt64 and mingw64 builds of gcc. Any pointers to what could be the problem here?

Kind regards,
Knut 

Douglas Katzman via Sbcl-help

unread,
Jul 2, 2023, 12:12:39 PM7/2/23
to Knut Arne Storeide, sbcl...@lists.sourceforge.net
I had to downgrade my msys2 to work around that.  It's pretty clearly a gcc bug.  
You could try clang as the compiler but I ran into problems with header files because there are massive conflicts between src/runtime/pthreads_win32.h and the real pthreads, which for some reason do not occur with gcc. Something about the default include path in the default environment just works, other than the fact that the compiler doesn't.

_______________________________________________
Sbcl-help mailing list
Sbcl...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sbcl-help
Reply all
Reply to author
Forward
0 new messages