On Mar 30, 2007, at 12:32 PM, Null Heart wrote:
I was just poking around with the latest snapshot for fun
Two thoughts come to mind. First, qualify your system with a known
to build, known to be good compiler. Build it 20 times, if it never
fails to build, you probably have a good system. If it ever fails,
toss the system out and get a real machine. :-)
when I came across a huge problem: the make would fail without reason.
If you need help reading a build log, well, this isn't quite the
right place for it. Look for '***' in the log as a very rough
approximation. Does sound like you did track it down to the right
failed file.
I fear, the problem with this specific line, is that the "-O2" option
Ok.
Running the included libtool command manually without the "-O2"
worked perfectly.
Run the command with the -O2 option, does it fail? If so, does it
always fail if you run it 5 times? If so, that bug is probably a run
of the mill compiler bug. Feel free to file a bug report. Do make
sure you have enough memory and paging file space on the system though.
Also, you should be able to check the gcc-testresults mailing list, say:
http://gcc.gnu.org/ml/gcc-testresults/2006-11/msg00519.html
and try and replicate the result. If you can, then you probably
don't have to worry about your system. If you can't... well, not
much we can probably do.
If you can't find any results to compare to, you might want to use
cygwin and compare against, say
http://gcc.gnu.org/ml/gcc-testresults/2007-02/msg00886.html
or http://gcc.gnu.org/ml/gcc-testresults/2007-01/msg00811.html
