Rex Dieter <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: | > Rex Dieter <[EMAIL PROTECTED]> writes: | > | Jose' Matos wrote: | > | | > FWIW this is already fixed in latest CVS and soon to be | > 1.4.0pre4... | > | | Another failure, now with pre4 (this one seems not so trivial): | > To me this looks like a problem with gcc or boost (I see the same | > problem) and this issue should be to either or both of them. | > (As the code compiles and runs with gcc 4.0.x, and fails with gcc 4.1 | > prerelease, that seems plausible to me...) | > | /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H | > -I. | > | -I. -I../../src -I./.. -I../../boost -O2 -g -pipe -Wall | > | -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector | > | --param=ssp-buffer-size=4 -m64 -mtune=nocona -c -o render_graphic.lo | > | render_graphic.C | > | g++ -DHAVE_CONFIG_H -I. -I. -I../../src -I./.. -I../../boost -O2 -g | > | -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector | > | --param=ssp-buffer-size=4 -m64 -mtune=nocona -c render_graphic.C -o | > | render_graphic.o | > btw. where are all these funky args to g++ comming from? | > (and seemingly they turn -fno-exceptions off... which is one switch | > that we "require") | | They're the standard $RPM_OPT_FLAGS on Fedora Core (soon to be) 5. | I'll look into manually removing -fexceptions from the list.
Well... you have to replace it with '-fno-exceptions' since '-fexceptions' is the default. -- Lgb