From: Andreas Schwab <schwab@linux-m68k.org>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Richard Biener <rguenther@suse.de>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>,
gcc-patches@gcc.gnu.org
Subject: Re: werror fallout for cross-builds
Date: Tue, 22 Jul 2014 22:12:00 -0000 [thread overview]
Message-ID: <87iompccxz.fsf@igel.home> (raw)
In-Reply-To: <alpine.BSF.2.02.1407221017320.68621@arjuna.pair.com> (Hans-Peter Nilsson's message of "Tue, 22 Jul 2014 16:40:31 -0400 (EDT)")
Hans-Peter Nilsson <hp@bitrange.com> writes:
> gcc:
> * configure.ac: For cross-builds of non-releases with gcc 4.4.4
> and newer, enable -Werror. Provide per-target exceptions, and do
> except vax-*.
This will break when a new printf format is added.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2014-07-22 21:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 5:04 [BUILDROBOT][PATCH] Fix mmix (unused variable) Jan-Benedict Glaw
2014-07-18 8:08 ` Hans-Peter Nilsson
2014-07-18 13:11 ` Jan-Benedict Glaw
2014-07-19 6:42 ` Hans-Peter Nilsson
2014-07-19 17:27 ` Jan-Benedict Glaw
2014-07-22 13:01 ` Richard Biener
2014-07-22 20:49 ` werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable)) Hans-Peter Nilsson
2014-07-22 22:12 ` Andreas Schwab [this message]
2014-07-23 0:09 ` Mike Stump
2014-07-23 2:54 ` Hans-Peter Nilsson
2014-07-23 8:06 ` Mike Stump
2014-07-24 11:13 ` Maciej W. Rozycki
2014-07-24 0:42 ` Jan-Benedict Glaw
2014-07-24 20:56 ` Hans-Peter Nilsson
2014-07-25 9:58 ` Jan-Benedict Glaw
2014-07-25 16:51 ` Hans-Peter Nilsson
2014-07-26 17:33 ` Hans-Peter Nilsson
2014-08-22 11:55 ` Jan-Benedict Glaw
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=87iompccxz.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@bitrange.com \
--cc=jbglaw@lug-owl.de \
--cc=rguenther@suse.de \
/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).