Subject: re: RFC: splitting out libopcodes from libbfd.
To: Todd Vierling <>
From: matthew green <>
List: tech-toolchain
Date: 02/24/2003 22:37:07
   :    So how does the GNU-typical build handle this if --with-unified-bfd is given
   :    to "configure"?
   : this is irrelevant.  GNU-style builds build them separately so the
   : problem seen in the netbsd tree only exists there.
   "./configure --with-unified-bfd" was the model upon which the original
   NetBSD libbfd was built, and was still there as of binutils 2.11.2 (I

there's no support for building a unified BFD library in the netbsd source
tree currently that i'm aware of.  there used to be a BFD_UNIFIED variable
but that doesn't exist anymore.

(BTW, it's called "--enable-targets=all" now in the FSF tools.)

   haven't checked since then).  IMNSHO, they're so interdependent that there's
   no point separating them, so GNU's wrong.  <cynical grin>
   But "whatever works"....

did you miss the part where i explained that they have separate CFLAGS
and that mixing them breaks things?  they may be interdependant, but
they are supposed to be built differently.