Alan Modra amodra@gmail.com
Mon Feb 3 04:55:00 GMT 2020

• Previous message (by thread): Forced to use --enable-unit-tests=no otherwise cross-compilation fail
• Next message (by thread): [COMMITTED] moxie: don't force big-endian
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Sat, Feb 01, 2020 at 07:14:39PM -0500, 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 ?

This is the wrong place to report problems with gdb.

-- 
Alan Modra
Australia Development Lab, IBM

---

• Previous message (by thread): Forced to use --enable-unit-tests=no otherwise cross-compilation fail
• Next message (by thread): [COMMITTED] moxie: don't force big-endian
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Binutils mailing list