This is just a guess… I haven’t tried it… but the --prefix should use the Windows path (i.e. --prefix=C:\opt\gambit\bld) because on Windows, even with mingw, the Gambit runtime will call the WIN32 CreateFile function to open files and it expects a Windows path. I don’t understand why gsc would segfault however. Do you have more details? Can you try with gdb? Marc
On Oct 10, 2016, at 8:57 PM, Bill Six <billsix@gmail.com> wrote:
I'm unable to figure out how to use Gambit on Windows successfully, and I'd like some help. (I'm plenty comfortable with Gambit on Linux/OSX). My general feeling is that I'm using configure's "prefix" argument incorrectly on Windows, which may be causing my problem.
I can build gambit just fine using the msys2 environment with mingw64 as the compiler.
(Here's the head of config.log "$ ./configure --prefix=/c/opt/gambit/bld --enable-single-host --enable-gcc-opts")
I can do basic stuff in gsi, such as
(+ 1 2) 3
But the following doesn't work:
(include "~~/lib/_gambit#.scm") *** ERROR IN (console)@2.1 -- Can't open file "\\c\\opt\\gambit\\bld\\lib/_gambit#.scm"
and I can't get "gsc -exe foo.scm" (for some trivial foo.scm) to not segfault.
Any ideas?
Thanks, Bill _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list