From: "Ben Elliston" <bje@au1.ibm.com>
To: amodra@bigpond.net.au, binutils@sources.redhat.com
Subject: Re: Add -Werror to build_warnings
Date: Wed, 16 Feb 2005 07:27:00 -0000 [thread overview]
Message-ID: <20050216022818.GA5900@namadgi> (raw)
In-Reply-To: <20050216013653.GJ10128@bubble.modra.org>
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
> > These flags are only used when the user
> > explicitly passes --enable-build-warnings
>
> Huh? I seem to get them by default.
Oh, I misread the shell code in configure.in. OK, it's on by default.
In that case, I withdraw my patch. We're not ready yet.
Cheers, Ben
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-02-16 2:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 5:01 Ben Elliston
2005-02-16 6:30 ` Alan Modra
2005-02-16 7:27 ` Ben Elliston [this message]
2005-02-16 13:01 ` Nick Clifton
2005-02-18 2:56 ` Alan Modra
2005-02-18 6:33 Paul Schlie
2005-02-18 14:34 ` Alan Modra
2005-02-18 15:58 Paul Schlie
2005-02-18 16:05 ` Zack Weinberg
2005-02-18 16:08 ` Paul Schlie
2005-02-18 16:23 ` Alan Modra
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=20050216022818.GA5900@namadgi \
--to=bje@au1.ibm.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).