gsc failure on Windows 10
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?
Afficher les réponses par date
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
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
Mikel: did you have any success building Gambit on Windows 10 using Visual Studio 2017? I would like to do the same but I have failed. Marc: I'd like to use Gambit (version 4.8.8 or whatever version) on Windows 10, using Visual Studio Community 2017 (which is free, like express was). To no success, I've tried mimicking how the build works on appveyor, I've tried "make prebuilt" using the MinGW/msys environment invoked from the developer command prompt, and I've tried to build using a slightly modified misc/vc2012.bat (since I used the developer command prompt, I just removed the call to vcvarsall.bat). I have too many failed build logs to include in this email, and I can't deduce what I'm doing wrong. I would appreciate if you could tell me either 1) how to compile Gambit using "make prebuilt" (which I assume uses the MinGW environment with CC=cl.exe) or 2) if you could make an updated misc\vs2017.bat and tell me what needs to be invoked before it, i.e., do I have to run configure from the msys environment first? Thanks, Bill On Thu, Jun 22, 2017 at 7:44 AM, mikel evins <mevins@me.com> wrote:
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
_______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
On Jul 10, 2017, at 7:18 PM, Bill Six <billsix@gmail.com> wrote:
Mikel: did you have any success building Gambit on Windows 10 using Visual Studio 2017? I would like to do the same but I have failed.
Marc: I'd like to use Gambit (version 4.8.8 or whatever version) on Windows 10, using Visual Studio Community 2017 (which is free, like express was). To no success, I've tried mimicking how the build works on appveyor, I've tried "make prebuilt" using the MinGW/msys environment invoked from the developer command prompt, and I've tried to build using a slightly modified misc/vc2012.bat (since I used the developer command prompt, I just removed the call to vcvarsall.bat). I have too many failed build logs to include in this email, and I can't deduce what I'm doing wrong.
I would appreciate if you could tell me either 1) how to compile Gambit using "make prebuilt" (which I assume uses the MinGW environment with CC=cl.exe) or 2) if you could make an updated misc\vs2017.bat and tell me what needs to be invoked before it, i.e., do I have to run configure from the msys environment first?
Sorry, Bill; I have not succeeded. I'll post if I get it working (but don't be surprised if I don't; some other work is ahead of it in priority right now).
participants (3)
-
Bill Six -
Marc Feeley -
mikel evins