🚀 go-pugleaf

Dean Schulze (schulze@lpl.arizona.edu) wrote:
:     Yes.  When gcc aborts a compile with "Internal compiler error"
: I'm sure that it is gcc's fault.  And there is no mention of signal 11
: in the Linux FAQ.

People post about signal 11 error messages quite often, and the stock
reply is to check for bad memory, bad motherboard, etc.  There are so
many Linux FAQ's and HOWTO's, no wonder he couldn't recall which one it
was mentioned in.  Gcc pushes hardware a great deal, so it finds faults
that may rarely be found otherwise.  It is not true that "internal compiler
error" automatically implies a non-hardware problem.

:     If I may say so, your comments illustrate part of the problem.
: Here you refer to some "known" configuration bugs, but you can't tell
: me where these bugs are documented.  (I've never heard anyone else refer
: to these "known" bugs.  Who are these bugs known to?) 

He was probably referring to the well-known Zenon Fortuna slackware bugfixes
WWW page.  I think that this has now moved to
    http://www.cuug.ab.ca:8001/~barkers/programs/slackware-fixes
Quite a few of these distribution bugs are known to many people who read
the c.o.l.*. newsgroups.

:     A few days ago I asked you to try and compile the code that gcc
: couldn't compile on my machine, but you have not even responded to that.

I have access to Slackware3.0 (pristine, out-of-box) on i486DX66 with
gcc-2.7.0 or Red Hat 2.1 on a P-120 with gcc-2.7.0 or slackware2.3 on a 
AMD486/100 upgraded to gcc-2.7.2.  Email me your code (better yet, post it?)
and I will give it a shot.  Please list your gcc-version, your libc version,
etc. etc.

Dave
dwl@apmaths.uwo.ca
http://pineapple.apmaths.uwo.ca/~dwl

% ./configure --enable-humour
checking for -lICE... no