I still don't understand. You're still compiling Gambit-generated code with gcc without the correct options.
Are you saying that now that gsc is fixed you don't need the second command, beginning with "gcc ..."?
Brad
On Mar 8, 2016, at 2:20 PM, Marc Feeley feeley@iro.umontreal.ca wrote:
Yes, the one that was broken and is now fixed!
Marc
On Mar 8, 2016, at 2:18 PM, Bradley Lucier lucier@math.purdue.edu wrote:
On Mar 8, 2016, at 1:50 PM, Marc Feeley feeley@iro.umontreal.ca wrote:
So after that, you can build your app with the following commands:
gsc -link -l core/ab.c myapp.scm gcc -o myapp ab.a `gsc -e '(print (path-expand "~~lib/libgambit.a"))'` myapp_.c myapp.c
You probably shouldn't use a bare "gcc" command because it won't have the options Gambit-generated code needs for correctness. Isn't there a gsc command that does the same thing?
Brad