From owner-freebsd-current  Fri Jan 17 01:33:35 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id BAA19948
          for current-outgoing; Fri, 17 Jan 1997 01:33:35 -0800 (PST)
Received: from mail12.digital.com (mail12.digital.com [192.208.46.20])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA19943
          for <current@freebsd.org>; Fri, 17 Jan 1997 01:33:25 -0800 (PST)
From: garyj@frt.dec.com
Received: from cssmuc.frt.dec.com by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV)
	id EAA31385; Fri, 17 Jan 1997 04:25:10 -0500 (EST)
Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM)
	id AA04780; Fri, 17 Jan 1997 10:24:46 +0100
Message-Id: <9701170924.AA04780@cssmuc.frt.dec.com>
X-Mailer: exmh version 1.6.4 10/10/95
To: John Polstra <jdp@polstra.com>
Cc: current@freebsd.org, Gary.Jennejohn@munich.netsurf.de
In-Reply-To: Message from John Polstra <jdp@polstra.com>  of Thu, 16 Jan 97 
 14:45:58 PST.
Reply-To: gjennejohn@frt.dec.com
Subject: Re: The new gdb links with -lmalloc ?! 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 17 Jan 97 10:24:45 +0100
X-Mts: smtp
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


jdp@polstra.com writes:
> I'm working with a slightly old -current, so this could be simple
> cockpit error.  I just updated my src/contrib/gdb and
> src/gnu/usr.bin/gdb sources to the latest, and tried building it.  All
> went fine until the final link step, when it tried to link with
> "-lmalloc".  That library was banished to /usr/lib/compat long ago,
> wasn't it?
> 
> I fixed src/gnu/usr.bin/gdb/gdb/Makefile and then it linked OK:
> 
> Index: Makefile
> ===================================================================
> RCS file: /home/ncvs/src/gnu/usr.bin/gdb/gdb/Makefile,v
> retrieving revision 1.15
> diff -u -r1.15 Makefile
> --- Makefile    1997/01/15 22:35:22     1.15
> +++ Makefile    1997/01/16 22:40:01
> @@ -56,7 +56,7 @@
>  .endif
>  
>  DPADD+= ${LIBTERMCAP}
> -LDADD+= -ltermcap -lmalloc
> +LDADD+= -ltermcap
>  
>  .if exists(${.OBJDIR}/../libiberty)
>  LDADD+=   -L${.OBJDIR}/../libiberty -liberty
> 

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.

Anybody else having problems with the new gdb ?

---
Gary Jennejohn				(work) gjennejohn@frt.dec.com
					(home) Gary.Jennejohn@munich.netsurf.de
					(play) gj@freebsd.org