public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vincent Lefevre <vincent+gcc@vinc17.org>
To: "Matthew R. Wilson" <mwilson@mattwilson.org>,
	Dennis Clarke <dclarke@blastwave.org>,
	gcc-help@gcc.gnu.org, mpfr@inria.fr
Subject: Re: one of those annoying little things
Date: Wed, 24 Aug 2022 22:00:30 +0200	[thread overview]
Message-ID: <20220824200030.GB32066@zira.vinc17.org> (raw)
In-Reply-To: <20220824192313.GA32066@zira.vinc17.org>

On 2022-08-24 21:23:13 +0200, Vincent Lefevre wrote:
> I'll update the MPFR text later in order to clarify it and give more
> details.

The text on https://www.mpfr.org/mpfr-current/ is now:

  Because make's rebuild decisions are based on timestamps, the -Z
  option is highly recommended: it sets the modification time of
  the patched files from timestamps given in the patch file, thus
  avoiding unnecessary rebuilds that could need some development
  utilities (such as autoconf); for the special PATCHES file, this
  may generate a "Not setting time" warning, which you can safely
  ignore. If the -Z option is not available, you can also avoid
  the unnecessary rebuilds by using the --disable-maintainer-mode
  configure option later.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

  parent reply	other threads:[~2022-08-24 20:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  4:21 Dennis Clarke
2022-08-24  5:20 ` Xi Ruoyao
2022-08-24  8:27   ` Matthew R. Wilson
2022-08-24 16:51     ` Dennis Clarke
2022-08-24 18:04       ` Matthew R. Wilson
2022-08-24 19:23         ` Vincent Lefevre
2022-08-24 19:43           ` Dennis Clarke
2022-08-24 20:00           ` Vincent Lefevre [this message]
2022-08-24 11:26 ` Jonathan Wakely

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=20220824200030.GB32066@zira.vinc17.org \
    --to=vincent+gcc@vinc17.org \
    --cc=dclarke@blastwave.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=mpfr@inria.fr \
    --cc=mwilson@mattwilson.org \
    /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).