This issue is probably caused by Gambit's bootstrap. I assume you can built from the v4.6.7 release, correct? The foolproof method (usually!) to build Gambit is to start from the most recent release (v4.6.7 in this case) or to clone the github repo. These methods avoid incompatibilities between a gsc-boot created from a previous release and the code of the current release.

If you have suggestions on how this could be improved, please go ahead!

Marc

On 2013-04-04, at 6:04 PM, Paul Wolneykien manowar@altlinux.org wrote:

Hi, all,

Currently I'm unable to build v4.6.7 when I set up gsc v4.6.6 as gsc-boot:

_num.c:1410:1: error: '___SYMCOUNT' undeclared here (not in a function) _num.c: In function '___H__20___num': _num.c:15316:1: error: '___lp' undeclared (first use in this function) _num.c:15316:1: note: each undeclared identifier is reported only once for each function it appears in _num.c: In function '___init_proc': _num.c:74427:1: error: '___lp' undeclared (first use in this function) make[1]: *** [_num.o] Error 1 make[1]: *** Waiting for unfinished jobs....

If the gsc-boot dummy script (exit 0) is not replaced by the real gsc and the _num.c and _io.c aren't regenerated, the situation is much worse: all of the above errors and much more...

My building scheme was already tested on 4.6.4 -> 4.6.5 and 4.6.5 -> 4.6.6 builds.

Regards,

  Paul.

---

Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list