From: "Christian Biesinger via gdb" <gdb@sourceware.org>
To: William Tambe <tambewilliam@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Forced to use --enable-unit-tests=no otherwise cross-compilation fail
Date: Thu, 13 Feb 2020 23:48:00 -0000 [thread overview]
Message-ID: <CAPTJ0XGJK8L6R2OYzrLa4LQZjyLpMOE-eXzRJTWfpxpG-2NgkA@mail.gmail.com> (raw)
In-Reply-To: <CAF8i9mNCT4hGvUyL+y5uKmL43Pw3Tpn_m=hCQH=NJH8t_NxKrg@mail.gmail.com>
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
prev parent reply other threads:[~2020-02-13 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 10:51 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 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=CAPTJ0XGJK8L6R2OYzrLa4LQZjyLpMOE-eXzRJTWfpxpG-2NgkA@mail.gmail.com \
--to=gdb@sourceware.org \
--cc=cbiesinger@google.com \
--cc=tambewilliam@gmail.com \
/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