This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Linking shared libopcodes against libbfd


Alan Modra <amodra@bigpond.net.au> writes:

> On Wed, May 14, 2003 at 01:43:03PM +0200, Andreas Jaeger wrote:
>> 	* Makefile.am (libopcodes_la_LIBADD): Add libbfd.la.
>> 	(libopcodes_la_DEPENDENCIES): Add libbfd.la.
>> 	* Makefile.in: Regenerated.
>
> This is OK, as long as libopcodes.a doesn't include libbfd.a (I'm not
> familiar enough with libtool to know).

This will not happen, libtool handles this correctly.

Now we need to add a dependency on an installed bfd, otherwise
libopcodes might get relinked against the previously installed libbfd
instead of the newly installed libbfd during make install :-(.  

Ok to commit the appended patch from Andreas Schwab together with the
previous one (to both SRC and GCC repositories)?

Andreas

2003-05-15  Andreas Schwab  <schwab@suse.de>

	* Makefile.tpl (install-opcodes): Define.
	* Makefile.in: Rebuild.

--- Makefile.tpl
+++ Makefile.tpl
@@ -1334,6 +1334,8 @@
 # binutils might be on PATH, and they might need the shared opcodes
 # library.
 install-binutils: maybe-install-opcodes
+# libopcodes depends on libbfd
+install-opcodes: maybe-install-bfd
 all-gas: maybe-all-libiberty maybe-all-opcodes maybe-all-bfd maybe-all-intl
 all-gprof: maybe-all-libiberty maybe-all-bfd maybe-all-opcodes maybe-all-intl
 all-ld: maybe-all-libiberty maybe-all-bfd maybe-all-opcodes maybe-all-bison maybe-all-byacc maybe-all-flex maybe-all-intl

-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj


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