Sounds simple enough; thanks. I'll let you know the results.
Sent from my iPad
On Jun 21, 2017, at 4:57 PM, Marc Feeley feeley@iro.umontreal.ca wrote:
Not sure what the problem is. But found this with a Google search:
https://groups.google.com/forum/#!topic/dislin-users/kagVl9LVFJA
So if I understand correctly, you need to use the exact same C compiler that was used to build gambit-v4_8_8-windows-visualc64.exe .
It is probably best to build Gambit yourself from source from the github repo.
Marc
On Jun 21, 2017, at 5:41 PM, mikel evins mevins@me.com wrote:
I just installed gambit-v48_8_8-windows-visualc64.exe on a machine that has VisualStudio Community 2017 on it (with C++ for CLI tools installed). I tried a quick gsc -exe hello.scm (on a file with a simple hello world in it), and got an error message like this:
d:\Users\mikel\Workshop\hello-scm>gsc -exe hello.scm hello.c hello_.c libgambit.lib(os_base.obj) : error LNK2019: unresolved external symbol __iob_func referenced in function ___display_error libgambit.lib(os_shell.obj) : error LNK2019: unresolved external symbol _environ referenced in function ___getenv_UCS_2 hello.exe : fatal error LNK1120: 2 unresolved externals
Did I overlook something obvious in the setup or compilation?
Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list