From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Antoine Tremblay <antoine.tremblay@ericsson.com>
Cc: <sergiodj+buildbot@sergiodj.net>, <gdb-patches@sourceware.org>,
<binutils@sourceware.org>
Subject: Re: Your commit 'MIPS/opcodes: Also set disassembler's ASE flags from ELF structures' broke GDB
Date: Thu, 15 Dec 2016 20:10:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1612151946340.6743@tp.orcam.me.uk> (raw)
In-Reply-To: <wwok1sx9nhet.fsf@ericsson.com>
On Thu, 15 Dec 2016, Antoine Tremblay wrote:
> > 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?
>
> I would look for:
> http://gdb-build.sergiodj.net/builders/Debian-i686-native-extended-gdbserver/builds/4691/steps/configure%20gdb/logs/stdio
> and
> http://gdb-build.sergiodj.net/builders/Debian-i686-native-extended-gdbserver/builds/4691/steps/compile%20gdb/logs/stdio
>
> For all the configure options.
Thanks, `--build=i686-pc-linux-gnu' does trigger the problem for me as
well, and AFAICT the underlying issue is MIPS target support is not
included in BFD as it wants 64-bit BFD which is not enabled, however the
opcodes library is still built.
Obviously such a configuration is useless for `libopcodes' as you can't
get at all the target-specific particulars BFD would normally provide, so
not even the binutils/ subdirectory tools (excluded, by request, from this
configuration, though otherwise buildable) can correctly support the MIPS
target, let alone GDB.
So I think we need to arrange for the list of targets enabled for other
subdirectories to be driven somehow by BFD or, more likely, the top level.
I'm not sure offhand how to do this though. Cc-ing `binutils' for wider
audience.
I'll see if there is something I could do right away as a temporary
measure to unbreak 32-bit BFD configurations -- I would make the reference
from `opcodes/mips-dis.c' to `bfd_mips_elf_get_abiflags' weak, however
regrettably this does not appear supported, so maybe we'll require a dummy
stub or suchlike hackery if MIPS target support is enabled, but not
included in BFD.
Any better suggestions?
Maciej
next prev parent reply other threads:[~2016-12-15 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1cHNui-0007Mp-46@kwanyin.sergiodj.net>
2016-12-15 12:16 ` Maciej W. Rozycki
2016-12-15 19:04 ` Antoine Tremblay
2016-12-15 20:10 ` Maciej W. Rozycki [this message]
2016-12-15 23:03 ` Alan Modra
2016-12-15 23:19 ` Maciej W. Rozycki
2016-12-19 11:49 ` Maciej W. Rozycki
[not found] ` <20161222123958.GA2896@bubble.grove.modra.org>
[not found] ` <alpine.DEB.2.00.1612222017020.6743@tp.orcam.me.uk>
2016-12-27 10:08 ` [PATCH, RFA] opcodes: Use autoconf to check for `bfd_mips_elf_get_abiflags' in BFD Joel Brobecker
2016-12-28 12:11 ` Alan Modra
2016-12-30 6:44 ` Joel Brobecker
2016-12-31 9:15 ` Maciej W. Rozycki
2016-12-15 19:47 ` Your commit 'MIPS/opcodes: Also set disassembler's ASE flags from ELF structures' broke GDB Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1612151946340.6743@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=antoine.tremblay@ericsson.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj+buildbot@sergiodj.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox