From: Andreas Schwab <schwab@suse.de>
To: apinski--- via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: <binutils@sourceware.org>, <gdb-patches@sourceware.org>,
<gcc-patches@sourceware.org>, <apinski@marvell.com>
Subject: Re: [PATCH] Use toplevel configure for GMP and MPFR for gdb
Date: Tue, 08 Nov 2022 17:46:28 +0100 [thread overview]
Message-ID: <mvmsfitbdi3.fsf@suse.de> (raw)
In-Reply-To: <1667924955-9218-1-git-send-email-apinski@marvell.com> (apinski's message of "Tue, 8 Nov 2022 08:29:15 -0800")
On Nov 08 2022, apinski--- via Gcc-patches wrote:
> diff --git a/configure b/configure
> index 7bcb894d1fe..9ee7a1a3abe 100755
> --- a/configure
> +++ b/configure
> @@ -769,6 +769,7 @@ infodir
> docdir
> oldincludedir
> includedir
> +runstatedir
> localstatedir
> sharedstatedir
> sysconfdir
Please avoid using a patched autoconf command.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2022-11-08 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 16:29 apinski
2022-11-08 16:46 ` Andreas Schwab [this message]
2022-11-08 16:55 ` Andrew Pinski
2022-11-10 16:25 ` Tom Tromey
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=mvmsfitbdi3.fsf@suse.de \
--to=schwab@suse.de \
--cc=apinski@marvell.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-patches@sourceware.org \
--cc=gdb-patches@sourceware.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).