Subject: Re: Problems with upgrade to current: and
To: None <>
From: Mike Long <>
List: current-users
Date: 07/14/1995 16:07:45
>Date: Fri, 14 Jul 1995 11:10:20 -0600
>From: Chris Jones <>
>I haven't seen this covered in the howto, so I'm wondering if anybody
>else has encountered this problem:  The new version of
>that gets built is apparently incompatible with something.  When I try
>to run programs which are dynamically linked with libgnumalloc (such
>as ld), I get this error:
># ld
> Undefined symbol "_vlimit" in ld:/usr/lib/

If the new library were incompatible, then the shared library major
version should be different.  Are you sure you did everything in the
right order?

It may be too late for you, but one technique that I found very
helpful when I upgraded to -current from 1.0 was to

setenv LDSTATIC -static

before I built -current's toolchain (make, gas, gcc, ld, &c.).  That
way, I didn't have to worry about my world exploding when I installed
the new libraries.  YMMV.
Mike Long <> 
VLSI Design Engineer         finger for PGP public key
Analog Devices, CPD Division          CCBF225E7D3F7ECB2C8F7ABB15D9BE7B
Norwood, MA 02062 USA                assert(*this!=opinionof(Analog));