Re: Automated report: NetBSD-current/i386 build failure

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Sun,  8 Jul 2018 19:28:34 +0000 (UTC)
    From:        NetBSD Test Fixture <bracket%NetBSD.org@localhost>
    Message-ID:  <153107811457.517.12437998665914189616%babylon5.NetBSD.org@localhost>

  | This is an automatically generated notice of a NetBSD-current/i386
  | build failure.
  |
  | The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
  | using sources from CVS date 2018.07.08.17.58.39.
  |
  | An extract from the build.sh output follows:

  |     /tmp/bracket/build/2018.07.08.17.58.39-i386/tools/bin/i486--netbsdelf-objcopy -j .text -j .sdata -j .data -j .dynamic -j .dynsym	 -j .rel -j .rel.* -j .rela -j .rela.* -j .reloc		 --subsystem efi-app	--target=pei-i386 bootia32.efi.so bootia32.efi
  |     /tmp/bracket/build/2018.07.08.17.58.39-i386/tools/bin/i486--netbsdelf-objcopy:bootia32.efi.so: Invalid bfd target
  |     *** [bootia32.efi] Error code 1
  |     nbmake[11]: stopped in /tmp/bracket/build/2018.07.08.17.58.39-i386/src/sys/arch/i386/stand/efiboot/bootia32
  |     1 error

This is (I believe) because this change ...

Modified Files:
	src/external/gpl3/binutils/dist/bfd: config.bfd
	src/external/gpl3/binutils/lib/libbfd/arch/i386: defs.mk

Log Message:
enable coff/pe executable vectors for i386 for the efi bootblocks.
XXX: pullup-8

is all very nice, but i386 is still using binutils.old rather than binutils.

Changing that is way above my pay grade, so instead I am checking to
see if the changes made to binutils, if applied to binutils.old, will have the
desired effect (and ideally, not break anything else).

More later (unless someone else fixes this quicker than I can.)

kre