public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/43301] top-level configure script ignores ---with-build-time-tools
Date: Sun, 31 Jul 2022 20:58:20 +0000 [thread overview]
Message-ID: <bug-43301-4-Hk4JOzQEqm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43301-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43301
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |https://gcc.gnu.org/piperma
| |il/gcc-patches/2022-July/59
| |9118.html
Keywords| |patch
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #4)
> (In reply to Eric Gallager from comment #3)
> > Patches go to the gcc-patches mailing list if you still want to see this
> > fixed
>
> Actually I guess I can try taking it myself
OK, submitted: https://gcc.gnu.org/pipermail/gcc-patches/2022-July/599118.html
next prev parent reply other threads:[~2022-07-31 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43301-4@http.gcc.gnu.org/bugzilla/>
2022-05-24 15:04 ` egallager at gcc dot gnu.org
2022-07-31 20:58 ` egallager at gcc dot gnu.org [this message]
2022-08-02 23:05 ` iains at gcc dot gnu.org
2022-08-04 2:20 ` egallager at gcc dot gnu.org
2022-12-02 6:27 ` egallager at gcc dot gnu.org
2010-03-09 1:00 [Bug bootstrap/43301] New: " scovich at gmail dot com
2010-03-09 1:04 ` [Bug bootstrap/43301] " scovich at gmail dot com
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=bug-43301-4-Hk4JOzQEqm@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).