From: Ian Lance Taylor <ian@airs.com>
To: Paul Brook <paul@codesourcery.com>
Cc: binutils@sources.redhat.com,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Nick Clifton <nickc@redhat.com>,
Richard Sandiford <rsandifo@redhat.com>,
Daniel Jacobowitz <drow@false.org>,
binutils@sourceware.org
Subject: Re: Binutils builds broken with -Werror
Date: Tue, 22 Mar 2005 19:44:00 -0000 [thread overview]
Message-ID: <m3sm2nfuoq.fsf@gossamer.airs.com> (raw)
Message-ID: <20050322194400.TOWcm32fp9YqisoT4eTApx20jRXRu2WloFYWt_uCpg0@z> (raw)
In-Reply-To: <200503221728.06922.paul@codesourcery.com>
Paul Brook <paul@codesourcery.com> writes:
> On Tuesday 22 March 2005 17:12, Maciej W. Rozycki wrote:
> > On Tue, 22 Mar 2005, Nick Clifton wrote:
> > > Hmm, well I am not wedded to GNU make, but do other versions of make
> > > support the $(subst FROM,TO,TEXT) function ? If not then can anyone
> > > suggest a more portable way of achieving the same effect ?
> >
> > Well, since that -Werror is added by configure scripts in the first
> > place, the most reasonable way of dealing with it is probably letting
> > autoconf/automake do their jobs. This flag could be substituted
> > separately instead of along other flags in WARN_CFLAGS and then omitted
> > selectively for generated files -- automake permits overriding default
> > compilation flags in templates on a file by file basis.
>
> Does it? I thought that only worked on a per-library basis.
No, you can override on a per-file basis using something like
foo_c_CFLAGS =
Ian
next prev parent reply other threads:[~2005-03-22 17:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 2:24 Daniel Jacobowitz
2005-03-21 12:08 ` Nick Clifton
2005-03-21 13:19 ` Richard Sandiford
2005-03-22 17:08 ` Nick Clifton
2005-03-22 17:12 ` Ian Lance Taylor
2005-03-22 17:31 ` Nick Clifton
2005-03-22 18:14 ` Maciej W. Rozycki
2005-03-22 18:24 ` Paul Brook
2005-03-22 18:48 ` Paul Brook
2005-03-22 19:38 ` Ian Lance Taylor [this message]
2005-03-22 19:44 ` Ian Lance Taylor
2005-03-22 21:54 ` Maciej W. Rozycki
2005-03-22 21:56 ` Maciej W. Rozycki
2005-03-23 14:43 ` Nick Clifton
2005-03-23 15:34 ` Nick Clifton
2005-03-25 2:15 ` Maciej W. Rozycki
2005-03-22 19:27 ` Dave Korn
2005-03-22 20:49 ` Nick Clifton
2005-03-23 5:31 ` Andreas Schwab
2005-03-23 14:41 ` Nick Clifton
2005-03-24 23:48 Nick Clifton
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=m3sm2nfuoq.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=binutils@sources.redhat.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=macro@linux-mips.org \
--cc=nickc@redhat.com \
--cc=paul@codesourcery.com \
--cc=rsandifo@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).