(By the way, attempting to build the package with devtools will fail, during the namcap stage, to install the package.)

In order to be more future-proof to things like this, I suggest using the builtin Makefile target for preventing conflicting files.

replace:

# resolve conflicts with binutils
rm $pkgdir/usr/include/{ansidecl,bfd,bfdlink,dis-asm,plugin-api,symcat}.h
rm $pkgdir/usr/share/info/bfd.info
rm $pkgdir/usr/lib/{libbfd,libopcodes}.a

with:

make -C bfd DESTDIR="$pkgdir" uninstall

Thanks for the fix.

I messed around with it a bit more, and it could be simplified further (no need for another pkgrel bump this time):

replace:
make DESTDIR=$pkgdir install
make -C bfd DESTDIR=$pkgdir uninstall

with:

make -C gdb DESTDIR="$pkgdir" install

also gdb-common can replace its whole rm -r lots-of-stuff, by using the make target:

make -C gdb/data-directory DESTDIR="$pkgdir" install

(Obviously again you no longer need to uninstall bfd)

I tried to see if you could *just* configure, make, make install inside the gdb/ subdirectory, but then it errors with:
make: *** No rule to make target '../bfd/libbfd.a', needed by 'gdb'. Stop.

:(

Unfortunately the build system seems to be very very specific about wanting the internal copy only. Which is ever so slightly awkward when building gdb and binutils separately... but eh, it is just extra build time AFAICT.

OTOH make install, can at least be confined to gdb/ I think, since it should not be depending on anything outside that subdirectory except as static libraries used for internal compilation.

The fix has been pushed to the testing repos. Please verify that it works as expected.

Thanks Eli for providing better install command for `gdb` package.