Now that I"ve created make.conf to set my architecture so that gcc
doesn't crash while compiling KDE with -O as is the default, I have
another question. Somehow it still ends up with -O2 in the Makefiles
that the configure script builds. g++ gives a big warning about known
optimizer bugs on this platform with that switch. Now does this mean
gcc might crash while compiling or that it may produce bad object code?
I've always tried to edit that flag out of makefiles, but this damn
thing has a makefile in every subdirectory so I'd have to edit several
Possible bad code -- but with using the -mev56 flag, it may produce OK
When I built kde, I seem to remember running find with a perl -pi to
edit each make file (or configure file). Its been a while..
Another thing to note is that it adds the flags from make.conf _after_
the KDE makefile flags. The result is that the -O? you specified in
make.conf is the one that comes last, and according to the gcc
man pages, the -O parameter specified last is the one that is used.
I suspect that it spews out those warnings simply because -O2 is
part of the command line at all, without necessarily beeing the one
that is used.
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message