While I have no problem building quakeforge-0.7.0 on FreeBSD, qfcc crashes trying to build quakeforge-0.7.2 and quakeforge-0.7.1a.
...
Making all in qwaq
...
../../tools/qfcc/source/qfcc -qq -O -g -Werror --advanced --no-default-paths -I../../ruamoko/include
gmake[3]: *** [qwaq.dat] Segmentation fault: 11 (core dumped)
$ cd tools/qwaq/ && gdb ../../tools/qfcc/source/.libs/qfcc
(gdb) run -v -O -g -Werror --advanced --no-default-paths -I../../ruamoko/include
Program received signal SIGSEGV, Segmentation fault.
0x08057dc8 in emit_ivars (ivars=0x287fc7c0, name=0x809f8d3 "Class")
at class.c:611
611 if (s->sy_type == sy_var)
(gdb) bt
#0 0x08057dc8 in emit_ivars (ivars=0x287fc7c0, name=0x809f8d3 "Class")
at class.c:611
#1 0x08058011 in begin_class (class=0x28408eb0) at class.c:645
#2 0x08058332 in class_begin (class_type=0x28408ed4) at class.c:680
#3 0x08051eb1 in qc_yyparse () at qc-parse.y:1555
#4 0x0807f98c in compile_file (filename=0x287ca400 "qfccCnOG2e") at qfcc.c:624
#5 0x0807fed4 in progs_src_compile () at qfcc.c:749
#6 0x08080046 in main (argc=8, argv=0xbfbfdc38) at qfcc.c:815
Please ask me if you need any other info or test.
I believe this is fixed in git. A patch for fixing emit_ivars is the first patch to qfcc after 0.7.2 was released. Please get the latest and let me know if it's fixed.
The problem went away after patching 0.7.2 with
https://sourceforge.net/p/quake/quakeforge/ci/6a3c775270701d3672461f143b6632484e5f32fa/
https://sourceforge.net/p/quake/quakeforge/ci/9d418379bfd515a1707742b4d3d295e47846fc8f/
and then, after switching to gcc-4.7 from the one in base, with
https://sourceforge.net/p/quake/quakeforge/ci/7137783e47ad97f2a1352fe34b876015f4dfd1a8/
I'm not sure that just the first patch (+ maybe gcc-4.7) is enough, I should make another test.
In the meanwhile, and waiting for a new release ;), thank you very much for your fast reply and suggestion.
Last edit: gnazioqf 2014-03-28
BTW, it seems that keybindings are buggy in 0.7.2 compared to 0.7.0.
In 0.7.0 I have K_w to walk forward but in 0.7.2 is not working.
Last edit: gnazioqf 2014-03-29
Any idea about what could be the problem?
It's the same for 0.7.1.
Why not just get the latest git version? Many more bug fixes and some nice new features.
However, yeah, I do need to do another release sometime.