Looking at the output from "emerge texmacs" it doesn't use the cflags set in /etc/make.conf.
I think this might be related to a bug determined to be an upstream problem with GCC 3.2. I will create a new revision and mask it to make sure it works under GCC 3.2 with optimizations.
Well, this is a choice being done by the texmacs makefiles... There are lots of problems with optimization indeed with texmacs, so I wouldn't play too much on the flags and rather keep the default ones... Yet, whatever the flags, the texmacs binary generated with gcc 3.2 will segfault quite randomly (and frequently...) This is not specific to gentoo. The only fix right now is to use a staticly generated binary from www.texmacs.org There was a bug about it a few weeks ago... This one was closed since, don't know why.
It seems to do quite well when I modify the configure script to not use -O3 and -fexpensive-optimizations. Quite well means it doesn't crash for me after having it running ofr 10 minutes.
Looks like it does indeed... Don't remember if I tried previously (certainly didn't try to remove everything which was the most sensible thing to do as a beginning...) Indeed with all optimization removed : it seems to work fine. Wasn't able to make it segfault... although I tried ! With -O2 instead, it does segfault :(
So the ebuild now uses the /etc/make.conf flags? If not, which is the best way to change the flags and still make portage know that texmacs is installed? Which flags should I use on my p4 system? Just "-march=pentium4"?
This package has proven to be very unreliable under GCC 3.2, and with any optimizations in general. As such, it's being moved to an unsupported status. Issues with the package should be taken to the developing party www.texmacs.org. The best solution to any problems has been, in the past, to disable optimizations. If a guaranteed, tried and tested cross-platform solution to optimization/segfault woes can be found, we will implement it.
