Re: Forced to use --enable-unit-tests=no otherwise cross-compilation fail
"Christian Biesinger via gdb" <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CAPTJ0XGJK8L6R2OYzrLa4LQZjyLpMOE-eXzRJTWfpxpG-2NgkA@mail.gmail.com> |
On Thu, Feb 13, 2020 at 5:28 PM William Tambe <[email protected]> wrote: > > On Sun, Feb 9, 2020 at 3:28 PM William Tambe <[email protected]> wrote: > > > > On Tue, Feb 4, 2020 at 11:27 AM Christian Biesinger > > <[email protected]> wrote: > > > > > > On Tue, Feb 4, 2020 at 5:51 AM William Tambe <[email protected]> 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