public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@gnu.org>
To: Eric Gallager <egall@gwmail.gwu.edu>
Cc: Eric Gallager via Gcc-patches <gcc-patches@gcc.gnu.org>,
	Andreas Schwab <schwab@suse.de>, Paolo Bonzini <bonzini@gnu.org>,
	neroden@gcc.gnu.org
Subject: Re: [PATCH] configure: respect --with-build-time-tools [PR43301]
Date: Fri, 05 Aug 2022 00:18:14 -0300	[thread overview]
Message-ID: <orczdfgyyx.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAMfHzOsm-R_CuSEk2xdO1pGN0dAO0uxU1ANXgHuykF78zyLrLg@mail.gmail.com> (Eric Gallager's message of "Wed, 3 Aug 2022 07:51:46 -0400")

On Aug  3, 2022, Eric Gallager <egall@gwmail.gwu.edu> wrote:

> OK, after reviewing the surrounding code, I think it makes sense; do
> you want to commit it, or should I?

Please proceed, if you have the cycles to give it a round of meaningful
testing (as in, including reconfigure with configure-generated as, and
also with external as in place).

Adjusting the analogous test patterns covering the other tools and
generated scripts would surely be welcome as well ;-)

Thanks!

-- 
Alexandre Oliva, happy hacker                https://FSFLA.org/blogs/lxo/
   Free Software Activist                       GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>

      reply	other threads:[~2022-08-05  3:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 20:55 Eric Gallager
2022-08-01  7:54 ` Andreas Schwab
2022-08-01 15:40   ` Eric Gallager
2022-08-02  5:24     ` Alexandre Oliva
2022-08-02 12:19       ` Eric Gallager
2022-08-03  3:33         ` Alexandre Oliva
2022-08-03 11:51           ` Eric Gallager
2022-08-05  3:18             ` Alexandre Oliva [this message]

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=orczdfgyyx.fsf@lxoliva.fsfla.org \
    --to=oliva@gnu.org \
    --cc=bonzini@gnu.org \
    --cc=egall@gwmail.gwu.edu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=neroden@gcc.gnu.org \
    --cc=schwab@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).