From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: "Fu, Chao-Ying" <fu@mips.com>,
Richard Sandiford <richard@codesourcery.com>,
gcc-patches@gcc.gnu.org, "Thekkath,
Radhika" <radhika@mips.com>, "Stephens, Nigel" <nigel@mips.com>
Subject: Re: [patch] Fixed-point patch 9/10
Date: Wed, 12 Sep 2007 14:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0709121205340.21875@digraph.polyomino.org.uk> (raw)
In-Reply-To: <46E7757E.6050804@codesourcery.com>
On Tue, 11 Sep 2007, Mark Mitchell wrote:
> Thank you for pointing this out. The make code you've written looks
> very tidy. However, I don't think we can require GNU make 3.81 at this
> point. I think it would be reasonable to require that for GCC 4.4, but
> I think it's a bit late in the game to require that for 4.3. In any
> case, it's not a decision I can make unilaterally. Is it possible to do
> what you need to do with an older version of GNU make? (I can't
> remember what the oldest supported version of GNU make is for GCC.)
The required version documented in install.texi is 3.79.1 or later.
With make there's also the issue that 3.81 has a POSIX-compatibility fix
that breaks building some software relying on the old behavior (such as
old versions of GCC, see bug 26764/27334). (There are also some other
incompatible changes, but I think they are less important in practice.)
This does mean that make upgrades are not completely safe, although not so
problematic as flex upgrades (where newer versions introduce gratuitous
POSIX-incompatibilities, see previous discussions) may be.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2007-09-12 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 0:25 Fu, Chao-Ying
2007-09-11 19:48 ` Fu, Chao-Ying
2007-09-12 7:00 ` Mark Mitchell
2007-09-12 14:19 ` Joseph S. Myers [this message]
2007-09-12 19:15 ` Fu, Chao-Ying
2007-09-15 2:15 ` Fu, Chao-Ying
2007-09-17 21:37 ` Mark Mitchell
2007-09-17 23:11 ` Fu, Chao-Ying
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.64.0709121205340.21875@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fu@mips.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=nigel@mips.com \
--cc=radhika@mips.com \
--cc=richard@codesourcery.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).