From: Eric Gallager <egall@gwmail.gwu.edu>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Paolo Bonzini <bonzini@gnu.org>,
neroden@gcc.gnu.org, aoliva@gcc.gnu.org, Ralf.Wildenhues@gmx.de
Subject: [PATCH] configure: respect --with-build-time-tools [PR43301]
Date: Sun, 31 Jul 2022 16:55:14 -0400 [thread overview]
Message-ID: <CAMfHzOuW5PZrTPVtoFBuPL20Yp=-Lp7Ec=M-5UG7peb=mX7ErA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
Hi, there's been a patch sitting in bug 43301 for over a decade that I
think still makes sense to apply, so I rebased it against current
trunk and found that it still applies. It just makes the configure
script respect the --with-build-time-tools flag. OK to commit?
ChangeLog:
PR bootstrap/43301
* configure: Regenerate.
* configure.ac: Respect --with-build-time-tools flag.
[-- Attachment #2: patch-configure_1.diff --]
[-- Type: application/octet-stream, Size: 1040 bytes --]
diff --git a/configure b/configure
index 65d7078dbe7..4d46b94ebc4 100755
--- a/configure
+++ b/configure
@@ -12850,7 +12850,9 @@ fi
# Check whether --with-build-time-tools was given.
if test "${with_build_time_tools+set}" = set; then :
withval=$with_build_time_tools; case x"$withval" in
- x/*) ;;
+ x/*)
+ with_build_time_tools=$withval
+ ;;
*)
with_build_time_tools=
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: argument to --with-build-time-tools must be an absolute path" >&5
diff --git a/configure.ac b/configure.ac
index 371def9b421..96a878a14cb 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3600,7 +3600,9 @@ AC_ARG_WITH([build-time-tools],
[AS_HELP_STRING([--with-build-time-tools=PATH],
[use given path to find target tools during the build])],
[case x"$withval" in
- x/*) ;;
+ x/*)
+ with_build_time_tools=$withval
+ ;;
*)
with_build_time_tools=
AC_MSG_WARN([argument to --with-build-time-tools must be an absolute path])
next reply other threads:[~2022-07-31 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 20:55 Eric Gallager [this message]
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
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='CAMfHzOuW5PZrTPVtoFBuPL20Yp=-Lp7Ec=M-5UG7peb=mX7ErA@mail.gmail.com' \
--to=egall@gwmail.gwu.edu \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@gcc.gnu.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=neroden@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).