From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, gdb@sources.redhat.com
Subject: Re: Status on cross builds
Date: Thu, 03 Nov 2005 21:13:00 -0000 [thread overview]
Message-ID: <20051103211221.GA11262@nevyn.them.org> (raw)
In-Reply-To: <200511022328.jA2NS2ox020148@elgar.sibelius.xs4all.nl>
On Thu, Nov 03, 2005 at 12:28:02AM +0100, Mark Kettenis wrote:
> > Date: Wed, 2 Nov 2005 13:24:27 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > Honestly, I recommend we disable -Werror for this release, if we aren't
> > going to spend a month fixing them. You think the cross builds are
> > bad? It's the natives that really break badly.
>
> But it's only enabled in gdb_mbuild.sh. That hardly matters for the
> release. By default, we still configure without -Werror. I really
> think that's why so many stuff has problems with -Werror. So instead
> I think, we should *enable* -Werror by default on the main branch
> after the release branch has been made. I volunteer to do the
> necessary legwork and create a suitable patch.
Sorry, we get -Werror by default for the various directories from
binutils. I was close.
After a release would be the right time to switch it on for gdb, if
ever. But we would need broad build testing from CVS on the native
platforms, and I don't think we've _ever_ had that.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-03 21:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 18:18 Joel Brobecker
2005-11-02 18:24 ` Daniel Jacobowitz
2005-11-02 18:58 ` Eli Zaretskii
2005-11-02 23:28 ` Mark Kettenis
2005-11-03 21:13 ` Daniel Jacobowitz [this message]
2005-11-03 22:51 ` Mark Kettenis
2005-11-03 22:52 ` Daniel Jacobowitz
2005-11-02 23:35 ` Mark Kettenis
2005-11-03 19:56 ` Stephane Carrez
2005-11-03 21:20 ` Mark Kettenis
2005-11-04 10:19 ` Corinna Vinschen
2005-11-04 10:34 ` Andreas Schwab
2005-11-07 19:43 ` Kevin Buettner
2005-11-07 22:24 ` Joel Brobecker
2005-11-07 22:38 ` Joel Brobecker
2005-11-08 1:56 ` Kevin Buettner
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=20051103211221.GA11262@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).