From owner-freebsd-current  Fri Jan 17 02:22:24 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id CAA21989
          for current-outgoing; Fri, 17 Jan 1997 02:22:24 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA21982
          for <current@freebsd.org>; Fri, 17 Jan 1997 02:22:17 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id VAA10162; Fri, 17 Jan 1997 21:16:15 +1100
Date: Fri, 17 Jan 1997 21:16:15 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199701171016.VAA10162@godzilla.zeta.org.au>
To: garyj@frt.dec.com, jdp@polstra.com
Subject: Re: The new gdb links with -lmalloc ?!
Cc: current@freebsd.org, Gary.Jennejohn@munich.netsurf.de
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> I fixed src/gnu/usr.bin/gdb/gdb/Makefile and then it linked OK:
>>  ...
>>  DPADD+= ${LIBTERMCAP}
>> -LDADD+= -ltermcap -lmalloc
>> +LDADD+= -ltermcap
>>  

>well, it worked for me. I even did a make world with the new gdb.
>I'm running 3.0-current, right up-to-date. Of course, I might have
>had an old libmalloc laying around in /usr/lib. Have to look when I
>get home tonight.
>
>I thought that gnumalloc disappeared, not malloc.

libmalloc is in ports/devel and has never been in /usr/src IIRC.

Checking DPADD using `make checkdpadd' would have detected the bug.
There is no ${LIBMALLOC}...

>Anybody else having problems with the new gdb ?

I haven't seen it yet, since ctm has stopped.  Is this a hint to
switch to cvsup? :-)

Bruce