Re: Your commit 'MIPS/opcodes: Also set disassembler's ASE flags from ELF structures' broke GDB

["Maciej W. Rozycki" <macro at imgtec dot com>]

On Thu, 15 Dec 2016, sergiodj+buildbot@sergiodj.net wrote:

> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> 
> Buildslave:
> 	wildebeest-debian-jessie-i686
> 
> Full Build URL:
> 	<http://gdb-build.sergiodj.net/builders/Debian-i686-native-extended-gdbserver/builds/4691>
> 
> Commit(s) tested:
> 	5e7fc731f80e0d08385a05ad47dda332a49d9341
> 
> Author(s) (in the same order as the commits):
> 	Maciej W. Rozycki <macro@imgtec.com>
> 
> Subject:
> 	MIPS/opcodes: Also set disassembler's ASE flags from ELF structures
> 
> Testsuite log (gdb.sum and gdb.log) URL(s):
> 	<http://gdb-build.sergiodj.net/results/Debian-i686-native-extended-gdbserver/5e/5e7fc731f80e0d08385a05ad47dda332a49d9341/>
> 
> *** Failed to compiled GDB.  ***
> ============================

 How do I get the canonical build/host/target system and `configure' 
options used for this build?

 This failure is very odd to me, it looks like `opcodes/mips-dis.c' has 
been included in the build of `libopcodes.a', however `bfd/elfxx-mips.c' 
has *not* been included in the build of `libbfd.a'.  Offhand I would 
consider such a configuration broken, however maybe it is legitimate after 
all.  Has the opcodes/ subdirectory been configured differently from the 
bfd/ subdirectory by any chance?

 In any case I have tried building a couple of GDB configurations and all 
completed successfully.

  Maciej