This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: PATCH: Remove dependency on libiberty from libbfd.so.

To: hjl at lucon dot org
Subject: Re: PATCH: Remove dependency on libiberty from libbfd.so.
From: DJ Delorie <dj at delorie dot com>
Date: Fri, 19 Oct 2001 15:38:51 -0400
CC: binutils at sourceware dot cygnus dot com
References: <20011018202149.A9395@lucon.org> <200110191432.f9JEWOt12770@envy.delorie.com> <20011019094822.B21150@lucon.org> <200110191755.f9JHtVt14351@envy.delorie.com> <20011019115402.A23285@lucon.org>


> How about this patch?

Shouldn't this be handled in configure?  It should *know* which
libiberty we're going to need, right?  The build would also do the
right thing (i.e. stop) if libiberty.a is missing but *supposed* to be
there.

And if configure is handling it, why use -l at all?  Why not just
list ../libiberty/libiberty.a in LIBADD?

Follow-Ups:
- Re: PATCH: Remove dependency on libiberty from libbfd.so.
  - From: H . J . Lu

References:
- PATCH: Remove dependency on libiberty from libbfd.so.
  - From: H . J . Lu
- Re: PATCH: Remove dependency on libiberty from libbfd.so.
  - From: DJ Delorie
- Re: PATCH: Remove dependency on libiberty from libbfd.so.
  - From: H . J . Lu
- Re: PATCH: Remove dependency on libiberty from libbfd.so.
  - From: DJ Delorie
- Re: PATCH: Remove dependency on libiberty from libbfd.so.
  - From: H . J . Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]