On Tuesday 04 November 2008 03:30:16 HG wrote: > Build errors with parrot-0.8.0 :- > src/exceptions.c > src/exceptions.c: In function `Parrot_ex_build_exception': > src/exceptions.c:74: `_CONST_STRING_74' undeclared (first use in this > function) src/exceptions.c:74: (Each undeclared identifier is reported only > once src/exceptions.c:74: for each function it appears in.) > src/exceptions.c:76: `_CONST_STRING_76' undeclared (first use in this > function) src/exceptions.c: In function `find_exception_handler': > src/exceptions.c:106: `_CONST_STRING_106' undeclared (first use in > this function) > src/exceptions.c:125: `_CONST_STRING_125' undeclared (first use in > this function) > src/exceptions.c: In function `Parrot_ex_throw_from_c': > src/exceptions.c:274: `_CONST_STRING_274' undeclared (first use in > this function) > src/exceptions.c: In function `Parrot_ex_mark_unhandled': > src/exceptions.c:400: `_CONST_STRING_400' undeclared (first use in > this function) > gmake: *** [src/exceptions.o] Error 1
> Summary of my perl5 (revision 5 version 8 subversion 6) configuration: > Platform: > ccversion='', gccversion='2.96 20000731 (Red Hat Linux 7.2 > 2.96-118.7.2)' Hm, I'm not sure it's worth our time to work around bugs in an eight year old GCC (and RH 7.2 is ... well, Fedora is at version 10). If we're not seeing a similar problem in GCC 4.x, we're happy to suggest a workaround, but I lean toward marking this as "wontfix". -- c
