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>
Cc: 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 21:23:13 +0200	[thread overview]
Message-ID: <20220824192313.GA32066@zira.vinc17.org> (raw)
In-Reply-To: <20220824180423.dubtsnvgropsdtb3@mattwilson.org>

On 2022-08-24 11:04:23 -0700, Matthew R. Wilson wrote:
> > Yes, I see that and also the words :
> > 
> >    The -Z option sets the modification time of the patched files
> >    from time stamps given in the patch file, thus avoiding the need
> >    of some development utilities (such as autoconf); this may generate
> >    a "Not setting time" warning for the PATCHES file, but you can
> >    safely ignore it.
> > 
> > Really?  Can I safely ignore it?  Because NetBSD has no such option for
> > the patch command therein.
> 
> The "you can safely ignore it" applies to specifically the warning when
> trying to set the time on the PATCHES file, not that you can safely
> ignore the entire -Z option (or lack thereof).
> 
> > Seems that we can not safely ignore that option. Perhaps the failure
> > here is with the "patch" software in NetBSD?  Maybe GNU patch is what
> > is needed to get that -Z option?
> 
> If the patch utility that comes with NetBSD does not have the -Z option,
> then yes, that seems to be a problem for the workflow you're trying to
> accomplish (protected source tree but using an 'unclean' source
> distribution of MPFR during the build since the effects of the -Z option
> aren't being correctly applied).

I'll update the MPFR text later in order to clarify it and give more
details.

If the -Z option is not available, I suggest to use the
--disable-maintainer-mode configure option in order to avoid the
unnecessary rebuilds (which the -Z patch option allows to avoid).

-- 
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)

  reply	other threads:[~2022-08-24 19:23 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 [this message]
2022-08-24 19:43           ` Dennis Clarke
2022-08-24 20:00           ` Vincent Lefevre
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=20220824192313.GA32066@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).