From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ian Lance Taylor <ian@airs.com>
Cc: Paul Brook <paul@codesourcery.com>,
binutils@sources.redhat.com, 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 21:56:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61L.0503221843550.19842@blysk.ds.pg.gda.pl> (raw)
Message-ID: <20050322215600.LTXKk2rtbpEoIL8J5i0qOhsi8AN5Y8BbfaKosK_95Oc@z> (raw)
In-Reply-To: <m3sm2nfuoq.fsf@gossamer.airs.com>
On Tue, 22 Mar 2005, Ian Lance Taylor wrote:
> > > 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 =
Prompted by Paul's notice I've checked automake documentation and done
some testing and he is indeed right. But there's a working solution
actually suggested in automake info pages by using an auxiliary archive
library as detailed in the "Per-Object Flags Emulation" chapter there.
Maciej
next prev parent reply other threads:[~2005-03-22 18:48 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
2005-03-22 19:44 ` Ian Lance Taylor
2005-03-22 21:54 ` Maciej W. Rozycki [this message]
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=Pine.LNX.4.61L.0503221843550.19842@blysk.ds.pg.gda.pl \
--to=macro@linux-mips.org \
--cc=binutils@sources.redhat.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=ian@airs.com \
--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).