From owner-freebsd-current  Thu Jan 16 14:46:06 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id OAA19010
          for current-outgoing; Thu, 16 Jan 1997 14:46:06 -0800 (PST)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA18996;
          Thu, 16 Jan 1997 14:46:01 -0800 (PST)
Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) with ESMTP id OAA28442; Thu, 16 Jan 1997 14:45:59 -0800 (PST)
Message-Id: <199701162245.OAA28442@austin.polstra.com>
To: gj@freebsd.org
Cc: current@freebsd.org
Subject: The new gdb links with -lmalloc ?!
Date: Thu, 16 Jan 1997 14:45:58 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

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



John
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth