INQUIRY: Inconsistent gcc compile failures
Erik Mouw
J.A.K.Mouw@ITS.TUDelft.NL
Thu Dec 21 11:41:00 GMT 2000
On Thu, Dec 21, 2000 at 02:19:00PM -0500, fhirsch@tse.com wrote:
> I am getting a number of compile failures at inconsistent points of major
> compiles with no code specific errors or warnings. Examples of code sources
> which I have seen these errors are the expat-lib, Apache, and PHP 3 and 4
> are especially prone to the problem. I believe that the compiler may be
> running out of memory somehow (32MB RAM w/150MB swap), though if I run the
> make through the gdb tool, I have never receive these errors. Errors do not
> always occur in the same module of code. Sometimes the code element will
> compile fine, and fail on a subsequent element. Eventually the code will
> compile all the way through in most cases.
Random crashes while compiling stuff...
> Enclosed is a sample report of the error (received when compiling Perl DBD
> mysql module). I believe I had one of these in gdb once, but no backtrace
> was actually available. gdb reported a normal exit state.
>
> cc: Internal compiler error: program cc1 got fatal signal 11
> cpp: output pipe has been closed
> make[1]: *** [mysql.o] Error 1
> make[1]: Leaving directory `/somepath'
> make: *** [subdirs] Error 2
... and Sig11. Sounds like flaky hardware. If you are running
GNU/Linux, check out the sig11 FAQ at:
http://www.BitWizard.nl/sig11/
Erik
--
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands
Phone: +31-15-2783635 Fax: +31-15-2781843 Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/
More information about the Gcc
mailing list