On Fri, 5 Jan 1996 09:15:39 +0100 (MET) 
 Erik Bertelsen <erik@sockdev.uni-c.dk> wrote:

 > Isn't this a dead-lock? When compiling you need 
 > /usr/lib/libgnumalloc.so.0.0 to be the old one (e.g. from the 1.1 
 > release) to be able to execute the compiler and linker, but then you link 
 > your new software with this same libgnumalloc, which in the end has the effect 
 > of never being able to upgrade it.

No ... actually, I grabbed the 1.1 libgnumalloc.so.0.0 and was able to 
build one with the fix...

 > >  #if defined(__bsdi__) && defined(__NetBSD__)
 > 
 > I didn't check the definition of __bsdi__, but I'm tempted to suggest to 
 > double-check whether to use || or &&.

*sigh*  Yup ... typo ... I'm sorry ... I just checked in the right thing...

 > I believe you. In fact I did this, and every non-statically-linked program
 > produced a core dump instead of doing their work. Rather nasty. 
 > Reinstalling just ld.so from the 1.1 release made the system work again,
 > and then the libgnumalloc problem popped up while I was trying to 
 > recompile and install again, so now I just hope that I'll be able to 
 > catch up again before the next show stopper appears. :-)

Yah .. I flipped .. my fileserver/router was crippled because of the 
ld.so lossage... :-)

--------------------------------------------------------------------------
Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffett Field, CA 94035                                Pager: 415.428.6939