On Sun, 30 Mar 2008 19:15:36 +0200 Oliver Herold <[EMAIL PROTECTED]> wrote:
> Hi > > building games/vavoom isn't possible it breaks while compiling with > default options. I'm using FreeBSD 7 (RELENG_7). > > > ---------------------------------------------------------------- > [...] > > gmake[2]: Leaving directory > `/usr/ports/games/vavoom/work/vavoom-1.26/source' > gmake[1]: Leaving directory > `/usr/ports/games/vavoom/work/vavoom-1.26/source' > Making all in progs > gmake[1]: Entering directory > `/usr/ports/games/vavoom/work/vavoom-1.26/progs' > Making all in common > gmake[2]: Entering directory > `/usr/ports/games/vavoom/work/vavoom-1.26/progs/common' > ../../utils/bin/vcc -P../../basev/common/progs ./engine/classes.vc > ../../basev/common/progs/engine.dat > ../../utils/bin/vcc -P../../basev/common/progs ./linespec/classes.vc > ../../basev/common/progs/linespec.dat > ./linespec/RedParticleFountain.vc:12: End of file inside a comment > ./linespec/GreenParticleFountain.vc:12: End of file inside a comment > ./linespec/BlueParticleFountain.vc:12: End of file inside a comment > ./linespec/YellowParticleFountain.vc:12: End of file inside a comment > ./linespec/PurpleParticleFountain.vc:12: End of file inside a comment > ./linespec/BlackParticleFountain.vc:12: End of file inside a comment > ./linespec/WhiteParticleFountain.vc:12: End of file inside a comment > Confused by previous errors, bailing out > gmake[2]: *** [../../basev/common/progs/linespec.dat] Fehler 1 > gmake[2]: Leaving directory > `/usr/ports/games/vavoom/work/vavoom-1.26/progs/common' > gmake[1]: *** [all-recursive] Fehler 1 > gmake[1]: Leaving directory > `/usr/ports/games/vavoom/work/vavoom-1.26/progs' > gmake: *** [all-recursive] Fehler 1 > *** Error code 2 > > Stop in /usr/ports/games/vavoom. > *** Error code 1 > > Stop in /usr/ports/games/vavoom. > ---------------------------------------------------------------- > Hello. The port builds on clean systems (pointyhat) and on my machine, so I think the problem may be local. What fails here is the internal VavoomC compiler, which is known to misbehave when built with "-fno-strict-aliasing" (and the port removes it if present). To debug this I would need your CFLAGS ('make -V CFLAGS' in port directory) and the complete build log (so we can see which flags were used when building 'vcc', and other oddities). Best Regards, Ale
signature.asc
Description: PGP signature