On 11 August 2016 at 00:42, Brad Smith <b...@comstyle.com> wrote: > On 08/08/16 12:11, Peter Maydell wrote: >> >> The various host OSes are irritatingly variable about the name >> of the linker emulation we need to pass to ld's -m option to >> build the i386 option ROMs. Instead of doing this via a >> CONFIG ifdef, check in configure whether any of the emulation >> names we know about will work and pass the right answer through >> to the makefile. If we can't find one, we fall back to not trying >> to build the option ROMs, in the same way we would for a non-x86 >> host platform. >> >> This is in particular necessary to unbreak the build on OpenBSD, >> since it wants a different answer to FreeBSD and we don't have >> an existing CONFIG_ variable that distinguishes the two. > > > To add to this.. amd64 uses "elf_i386". Looking at i386 it uses > elf_i386_obsd and that is the only emulation supported. > > So change the list of emulations to try to > > elf_i386 elf_i386_fbsd elf_i386_obsd i386pe > > > Someone needs to take a look at what NetBSD / DragonFly are > using.
My NetBSD 6.1.4 amd64 VM uses elf_i386. Building should still work on an OS which doesn't support an emulation in the list in configure -- we'll just fall back to not building the option ROMs, which is the same position any non-x86 host architecture is in. thanks -- PMM
