Subject: Re: problems with gcc 2.7.2
To: None <current-users@NetBSD.ORG>
From: Mike Long <mike.long@analog.com>
List: current-users
Date: 01/05/1996 11:01:06
>Date: Fri, 5 Jan 1996 09:15:39 +0100 (MET)
>From: Erik Bertelsen <erik@sockdev.uni-c.dk>
>
>> On Thu, 4 Jan 1996 16:16:41 +0000 (GMT) 
>>  Thorsten Frueauf <frueauf@ira.uka.de> wrote:
>> 
>>  > /usr/libexec/ld.so: Undefined symbol "_vlimit" in grep:/usr/lib/libgnumalloc.so.0.0
>>  > /usr/libexec/ld.so: Undefined symbol "_vlimit" in gcc:/usr/lib/libgnumalloc.so.0.0
>> 
>> I recently fixed this.  Here's the commit message to mem-limits.h:
>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.

It's probably not the fastest way to do it, but something like this
should work:

cd /usr/src/gnu
setenv LDSTATIC -static
(cd usr.bin; make clean && make && make install)
unsetenv LDSTATIC
(cd lib; make && make install)
(cd usr.bin; make clean && make && make install)
-- 
Mike Long <mike.long@analog.com>           http://www.shore.net/~mikel
VLSI Design Engineer         finger mikel@shore.net for PGP public key
Analog Devices, CPD Division          CCBF225E7D3F7ECB2C8F7ABB15D9BE7B
Norwood, MA 02062 USA       (eq (opinion 'ADI) (opinion 'mike)) -> nil