Re: egcs-1.0.3a weirdness with lynx-2.8 on v2.1.107

[Andreas Jaeger <aj at arthur dot rhein-neckar dot de>]

>>>>> Alex Buell writes:

 > Hi guys,
 > I could hardly believe my eyes tonight when I finally compiled lynx-2.8
 > with egcs-1.0.3a, using glibc-2.0.94, on kernel v2.1.107. 

 > What happened was that for some reasons (yet undetermined), the cc1
 > trundled off merrily on its way compiling LYMainLoop.c (in the src
 > subdirectory), and it seemed to get stuck somewhere. I then went into top
 > to see what it was doing and I was astonished to see that the swap space
 > was FULL, no more swap space available (this on a 32MB i486 machine with a
 > 26MB swap file - it never used up more than 6MB normally and only uses up
 > more than that rarely when looking at some stupid java-based web sites)
 > and Linux was thrashing the hard disk so hard I was very afraid for the
 > poor thing's safety.  According to top, it had well over 49MB of virtual
 > memory used up on compiling that source file. Of course when the real
 > memory dropped to less than 512k, the compiler finally aborted with a
 > sig-11 error (please don't quote me the reference to that sig-11 error web
 > site - I have never had a sig-11 in the last 18 months that I have been
 > using Linux - and this is the first sig-11 error I have seen).

glibc 2.0.94 uses optimized inline functions.  Inlining these
functions might case this.  Try -D__NO_STRING_INLINES.

(see also the glibc FAQ entry: 3.8. I've got errors compiling code
that uses certain string functions.  Why?)

Andreas
-- 
 Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
  for pgp-key finger ajaeger@alma.student.uni-kl.de