Subject: re: RFC: splitting out libopcodes from libbfd.
To: Todd Vierling <>
From: matthew green <>
List: tech-toolchain
Date: 02/24/2003 09:21:59
   : currently, we build libbfd & libopcodes together into a single
   : libbfd that is installed.  this is problematic because the CFLAGS
   : for these two entities are merged in gnu/lib/libbfd, but in the
   : distribution, they are disjoint, and, in 2.13, they are conflicting.
   : in particular, opcodes defines SHMEDIA_INCLUDE in Makefile while
   : bfd defines it in individual .c files that include elf32-sh.c..
   So how does the GNU-typical build handle this if --with-unified-bfd is given
   to "configure"?
   If that doesn't work either, it's a binutils config bug.  If it works with
   --with-unified-bfd but not with NetBSD's (unified) bfd, "huh?".

this is irrelevant.  GNU-style builds build them separately so the
problem seen in the netbsd tree only exists there.

we don't have a "(unified) bfd" any more, AFAIK.