Date: Fri, 17 Jan 97 10:24:45 +0100 From: garyj@frt.dec.com To: John Polstra <jdp@polstra.com> Cc: current@freebsd.org, Gary.Jennejohn@munich.netsurf.de Subject: Re: The new gdb links with -lmalloc ?! Message-ID: <9701170924.AA04780@cssmuc.frt.dec.com> In-Reply-To: Message from John Polstra <jdp@polstra.com> of Thu, 16 Jan 97 14:45:58 PST.
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9701170924.AA04780>