After removing call "C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat", calling misc/vs2008.bat in gambc-v4_6_6 sources from VS2010 command prompt gives these errors for gsc:
_gambcgsc.obj : error LNK2001: unresolved external symbol _____20___t_2d_univ _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___codegen _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___x86 _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___asm _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___assert gsc.exe : fatal error LNK1120: 5 unresolved externals
Afficher les réponses par date
vc2008.bat is missing
%COMP_LIB% _asm.c %COMP_LIB% _assert.c %COMP_LIB% _codegen.c %COMP_LIB% _t-univ.c %COMP_LIB% _x86.c
and respective .obj from cl -Fegsc.exe line
În data de Sat, 16 Jun 2012 18:07:19 +0300, Cristian Baboi cristian.baboi@gmail.com a scris:
After removing call "C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat", calling misc/vs2008.bat in gambc-v4_6_6 sources from VS2010 command prompt gives these errors for gsc:
_gambcgsc.obj : error LNK2001: unresolved external symbol _____20___t_2d_univ _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___codegen _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___x86 _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___asm _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___assert gsc.exe : fatal error LNK1120: 5 unresolved externals
To the best of my experience, calling the vcvars bat file prior to getting into Gambit (or at least, prior to any Visual C compiler executable invocation) is vital to Gambit C file compilation success when using VC, as well as for the compilation of pretty much any other C file too btw.
Why do you use misc/vs2008.bat, doesn't the Gambit-VC binary distro use CL appropriately in gambc-cc.bat as used by |compile-file| already?
(As of currently I'm unaware of what misc/vs2008.bat is for, if you are please feel free to share.)
Generally the Mingw Gambit distro gives you a smoother experience, if it's good for your needs (which it ought to, I suppose), you can consider it.
2012/6/16 Cristian Baboi cristian.baboi@gmail.com
After removing call "C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat", calling misc/vs2008.bat in gambc-v4_6_6 sources from VS2010 command prompt gives these errors for gsc:
_gambcgsc.obj : error LNK2001: unresolved external symbol _____20___t_2d_univ _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___codegen _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___x86 _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___asm _gambcgsc.obj : error LNK2001: unresolved external symbol _____20___assert gsc.exe : fatal error LNK1120: 5 unresolved externals _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
În data de Sat, 16 Jun 2012 19:03:00 +0300, Mikael mikael.rcv@gmail.com a scris:
To the best of my experience, calling the vcvars bat file prior to getting into Gambit (or at least, prior to any Visual C compiler executable invocation) is vital to Gambit C file compilation success when using VC, as well as for the compilation of pretty much any other C file too btw.
I was compiling from a command prompt that already had vcvars called.
Why do you use misc/vs2008.bat, doesn't the Gambit-VC binary distro use CL appropriately in gambc-cc.bat as used by |compile-file| already?
I was trying to compile gsi & gsc, not some scheme source.
(As of currently I'm unaware of what misc/vs2008.bat is for, if you are please feel free to share.)
It's for compiling gambit-c with visual studio.
Trying misc\vc2008.bat from a x64 Win64 VS2010 command prompt gives 64 bit gsi.exe & gsc.exe Unfortunatelly,unlike 32 bit versions, they crash on launch.
Can you compile Gambit anew and paste all output you got here (so open a console window, increase its width a bit (to 120-200 cols somewhere) and its buffer length to be sufficient for the entire compilation, say to 15000)?
2012/6/16 Cristian Baboi cristian.baboi@gmail.com
În data de Sat, 16 Jun 2012 19:03:00 +0300, Mikael mikael.rcv@gmail.com a scris:
To the best of my experience, calling the vcvars bat file prior to getting
into Gambit (or at least, prior to any Visual C compiler executable invocation) is vital to Gambit C file compilation success when using VC, as well as for the compilation of pretty much any other C file too btw.
I was compiling from a command prompt that already had vcvars called.
Why do you use misc/vs2008.bat, doesn't the Gambit-VC binary distro use CL
appropriately in gambc-cc.bat as used by |compile-file| already?
I was trying to compile gsi & gsc, not some scheme source.
(As of currently I'm unaware of what misc/vs2008.bat is for, if you are
please feel free to share.)
It's for compiling gambit-c with visual studio.
Trying misc\vc2008.bat from a x64 Win64 VS2010 command prompt gives 64 bit gsi.exe & gsc.exe Unfortunatelly,unlike 32 bit versions, they crash on launch.
În data de Sun, 17 Jun 2012 11:46:45 +0300, Mikael mikael.rcv@gmail.com a scris:
Can you compile Gambit anew and paste all output you got here (so open a console window, increase its width a bit (to 120-200 cols somewhere) and its buffer length to be sufficient for the entire compilation, say to 15000)?
See the attachment.
2012/6/16 Cristian Baboi cristian.baboi@gmail.com
În data de Sat, 16 Jun 2012 19:03:00 +0300, Mikael mikael.rcv@gmail.com a scris:
(As of currently I'm unaware of what misc/vs2008.bat is for, if you are
please feel free to share.)
It's for compiling gambit-c with visual studio.
Trying misc\vc2008.bat from a x64 Win64 VS2010 command prompt gives 64 bit gsi.exe & gsc.exe Unfortunatelly,unlike 32 bit versions, they crash on launch.
Aha.
There's one warning message in there:
os_tty.c(752) : warning C4273: 'GetConsoleWindow' : inconsistent dll linkage c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\include\wincon.h(946) : see previous definition of 'GetConsoleWindow' os_tty.c(851) : warning C4113: 'BOOL (__cdecl *)()' differs in parameter lists from 'PHANDLER_ROUTINE' os_tty.c(8515) : warning C4113: 'BOOL (__cdecl *)()' differs in parameter lists from 'PHANDLER_ROUTINE' os_tty.c(8536) : warning C4113: 'BOOL (__cdecl *)()' differs in parameter lists from 'PHANDLER_ROUTINE'
Could be due to it; resolve it and see what happens?
2012/6/17 Cristian Baboi cristian.baboi@gmail.com
În data de Sun, 17 Jun 2012 11:46:45 +0300, Mikael mikael.rcv@gmail.com a scris:
Can you compile Gambit anew and paste all output you got here (so open a
console window, increase its width a bit (to 120-200 cols somewhere) and its buffer length to be sufficient for the entire compilation, say to 15000)?
See the attachment.
2012/6/16 Cristian Baboi cristian.baboi@gmail.com
În data de Sat, 16 Jun 2012 19:03:00 +0300, Mikael <mikael.rcv@gmail.com
a scris:
(As of currently I'm unaware of what misc/vs2008.bat is for, if you are
please feel free to share.)
It's for compiling gambit-c with visual studio.
Trying misc\vc2008.bat from a x64 Win64 VS2010 command prompt gives 64 bit gsi.exe & gsc.exe Unfortunatelly,unlike 32 bit versions, they crash on launch.
-
Cristian Baboi -
Mikael