* Forced to use --enable-unit-tests=no otherwise cross-compilation fail
@ 2020-02-04 10:51 William Tambe
2020-02-04 14:29 ` Simon Marchi
2020-02-04 16:27 ` Christian Biesinger via gdb
0 siblings, 2 replies; 6+ messages in thread
From: William Tambe @ 2020-02-04 10:51 UTC (permalink / raw)
To: gdb
With Binutils 2.34, I have to use --enable-unit-tests=no with
./configure otherwise cross-compilation fail trying to link
gdbarch-selftests.o:
/usr/bin/ld: gdbarch-selftests.o: in function `_initialize_gdbarch_selftests()':
/binutils-gdb-build/gdb/../../binutils-gdb/gdb/gdbarch-selftests.c:168:
undefined reference to
`selftests::register_test_foreach_arch(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&, void
(*)(gdbarch*))'
Why is it now required to use --enable-unit-tests=no when cross-compiling ?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Forced to use --enable-unit-tests=no otherwise cross-compilation fail
2020-02-04 10:51 Forced to use --enable-unit-tests=no otherwise cross-compilation fail William Tambe
@ 2020-02-04 14:29 ` Simon Marchi
2020-02-04 16:27 ` Christian Biesinger via gdb
1 sibling, 0 replies; 6+ messages in thread
From: Simon Marchi @ 2020-02-04 14:29 UTC (permalink / raw)
To: William Tambe, gdb
On 2020-02-04 5:51 a.m., William Tambe wrote:
> With Binutils 2.34, I have to use --enable-unit-tests=no with
> ./configure otherwise cross-compilation fail trying to link
> gdbarch-selftests.o:
>
> /usr/bin/ld: gdbarch-selftests.o: in function `_initialize_gdbarch_selftests()':
> /binutils-gdb-build/gdb/../../binutils-gdb/gdb/gdbarch-selftests.c:168:
> undefined reference to
> `selftests::register_test_foreach_arch(std::__cxx11::basic_string<char,
> std::char_traits<char>, std::allocator<char> > const&, void
> (*)(gdbarch*))'
>
> Why is it now required to use --enable-unit-tests=no when cross-compiling ?
>
Hmm this is not expected. That missing symbol should be provided by gdb/selftest-arch.o.
Does that file get compiled (and linked) in your configuration?
Simon
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Forced to use --enable-unit-tests=no otherwise cross-compilation fail
2020-02-04 10:51 Forced to use --enable-unit-tests=no otherwise cross-compilation fail William Tambe
2020-02-04 14:29 ` Simon Marchi
@ 2020-02-04 16:27 ` Christian Biesinger via gdb
2020-02-09 20:29 ` William Tambe
1 sibling, 1 reply; 6+ messages in thread
From: Christian Biesinger via gdb @ 2020-02-04 16:27 UTC (permalink / raw)
To: William Tambe; +Cc: gdb
On Tue, Feb 4, 2020 at 5:51 AM William Tambe <tambewilliam@gmail.com> wrote:
>
> With Binutils 2.34, I have to use --enable-unit-tests=no with
> ./configure otherwise cross-compilation fail trying to link
> gdbarch-selftests.o:
By the way, I would recommend using a GDB release tag instead of a
binutils one... the release processes are independent and the GDB tags
have more testing for GDB.
Christian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Forced to use --enable-unit-tests=no otherwise cross-compilation fail
2020-02-04 16:27 ` Christian Biesinger via gdb
@ 2020-02-09 20:29 ` William Tambe
2020-02-13 23:28 ` William Tambe
0 siblings, 1 reply; 6+ messages in thread
From: William Tambe @ 2020-02-09 20:29 UTC (permalink / raw)
To: Christian Biesinger; +Cc: gdb
On Tue, Feb 4, 2020 at 11:27 AM Christian Biesinger
<cbiesinger@google.com> wrote:
>
> On Tue, Feb 4, 2020 at 5:51 AM William Tambe <tambewilliam@gmail.com> wrote:
> >
> > With Binutils 2.34, I have to use --enable-unit-tests=no with
> > ./configure otherwise cross-compilation fail trying to link
> > gdbarch-selftests.o:
>
> By the way, I would recommend using a GDB release tag instead of a
> binutils one... the release processes are independent and the GDB tags
> have more testing for GDB.
Is it ok to use the master branch ? would it include all fixes from
both binutils and GDB ?
>
> Christian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Forced to use --enable-unit-tests=no otherwise cross-compilation fail
2020-02-09 20:29 ` William Tambe
@ 2020-02-13 23:28 ` William Tambe
2020-02-13 23:48 ` Christian Biesinger via gdb
0 siblings, 1 reply; 6+ messages in thread
From: William Tambe @ 2020-02-13 23:28 UTC (permalink / raw)
To: Christian Biesinger; +Cc: gdb
On Sun, Feb 9, 2020 at 3:28 PM William Tambe <tambewilliam@gmail.com> wrote:
>
> On Tue, Feb 4, 2020 at 11:27 AM Christian Biesinger
> <cbiesinger@google.com> wrote:
> >
> > On Tue, Feb 4, 2020 at 5:51 AM William Tambe <tambewilliam@gmail.com> wrote:
> > >
> > > With Binutils 2.34, I have to use --enable-unit-tests=no with
> > > ./configure otherwise cross-compilation fail trying to link
> > > gdbarch-selftests.o:
> >
> > By the way, I would recommend using a GDB release tag instead of a
> > binutils one... the release processes are independent and the GDB tags
> > have more testing for GDB.
>
> Is it ok to use the master branch ? would it include all fixes from
> both binutils and GDB ?
Is it ok to use the master in order to get all fixes from both
Binutils and GDB ?
In order words, does the master branch has all commits found in the
branches for Binutils and GBD ?
>
> >
> > Christian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Forced to use --enable-unit-tests=no otherwise cross-compilation fail
2020-02-13 23:28 ` William Tambe
@ 2020-02-13 23:48 ` Christian Biesinger via gdb
0 siblings, 0 replies; 6+ messages in thread
From: Christian Biesinger via gdb @ 2020-02-13 23:48 UTC (permalink / raw)
To: William Tambe; +Cc: gdb
On Thu, Feb 13, 2020 at 5:28 PM William Tambe <tambewilliam@gmail.com> wrote:
>
> On Sun, Feb 9, 2020 at 3:28 PM William Tambe <tambewilliam@gmail.com> wrote:
> >
> > On Tue, Feb 4, 2020 at 11:27 AM Christian Biesinger
> > <cbiesinger@google.com> wrote:
> > >
> > > On Tue, Feb 4, 2020 at 5:51 AM William Tambe <tambewilliam@gmail.com> wrote:
> > > >
> > > > With Binutils 2.34, I have to use --enable-unit-tests=no with
> > > > ./configure otherwise cross-compilation fail trying to link
> > > > gdbarch-selftests.o:
> > >
> > > By the way, I would recommend using a GDB release tag instead of a
> > > binutils one... the release processes are independent and the GDB tags
> > > have more testing for GDB.
> >
> > Is it ok to use the master branch ? would it include all fixes from
> > both binutils and GDB ?
>
> Is it ok to use the master in order to get all fixes from both
> Binutils and GDB ?
>
> In order words, does the master branch has all commits found in the
> branches for Binutils and GBD ?
Yeah, that's fine. Of course occasionally that introduces new breakage
but most of the time it works just fine; it's what I use.
Christian
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-02-13 23:48 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-04 10:51 Forced to use --enable-unit-tests=no otherwise cross-compilation fail William Tambe
2020-02-04 14:29 ` Simon Marchi
2020-02-04 16:27 ` Christian Biesinger via gdb
2020-02-09 20:29 ` William Tambe
2020-02-13 23:28 ` William Tambe
2020-02-13 23:48 ` Christian Biesinger via gdb
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox