From: Yao Qi <qiyaoltc@gmail.com>
To: "Maciej W. Rozycki" <macro@imgtec.com>
Cc: sergiodj+buildbot@sergiodj.net,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Your commit 'MIPS/opcodes: Also set disassembler's ASE flags from ELF structures' broke GDB
Date: Thu, 15 Dec 2016 19:47:00 -0000 [thread overview]
Message-ID: <CAH=s-PPEZHpSPOQK-Sf6Z8YbxT2v9Oh_mXf2GzNaVP00rXwCyQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1612150502490.6743@tp.orcam.me.uk>
On 16-12-15 12:15:33, Maciej W. Rozycki wrote:
>
> 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.
>
Hi, Maciej,
Did you build GDB on an i686-linux? I can somehow reproduce it on
x86_64-linux, like this,
../opcodes/libopcodes.a(mips-dis.o): In function `set_default_mips_dis_options':
mips-dis.c:(.text+0x906): undefined reference to `bfd_mips_elf_get_abiflags'
collect2: error: ld returned 1 exit status
make: *** [gdb] Error 1
I configure with these options,
../binutils-gdb/configure --host=i686-pc-linux-gnu --disable-sim
--disable-binutils --disable-gprof --disa
ble-gold --disable-gas --disable-ld --enable-targets=all CFLAGS='-m32'
CXXFLAGS='-m32'
however, the build fails due to failing to find i686-pc-linux-gnu-ar.
I explicitly set AR=ar in make,
or modify libtool in several directories. Finally, the build failed
on the error above.
--
Yao
prev parent reply other threads:[~2016-12-15 19:47 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
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 ` Yao Qi [this message]
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='CAH=s-PPEZHpSPOQK-Sf6Z8YbxT2v9Oh_mXf2GzNaVP00rXwCyQ@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@imgtec.com \
--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