public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/40447] Add a switch to configure to allow *source* directory of mprt and gmp to be specified.
Date: Mon, 19 Jul 2021 06:52:42 +0000 [thread overview]
Message-ID: <bug-40447-4-tsvP7cIPEF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40447-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40447
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |WONTFIX
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Rather the ask is not going to be fixed, the symbolic link trick works, even
more you can make a new directory which symbolic links from the gcc sources
toplevel directory and then have the GMP symbolic link there. So if GCC
sources can still be in read only directory if needed.
Oh the version of GMP/MPFR/MPC is already printed out for a long time now.
next prev parent reply other threads:[~2021-07-19 6:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-40447-4@http.gcc.gnu.org/bugzilla/>
2021-07-19 6:50 ` pinskia at gcc dot gnu.org
2021-07-19 6:52 ` pinskia at gcc dot gnu.org [this message]
2009-06-15 14:03 [Bug bootstrap/40447] New: " david dot kirkby at onetel dot net
2009-06-15 14:59 ` [Bug bootstrap/40447] " pinskia at gcc dot gnu dot org
2009-06-15 16:52 ` david dot kirkby at onetel dot net
2009-06-15 16:54 ` pinskia at gcc dot gnu dot org
2009-06-15 16:57 ` david dot kirkby at onetel dot net
2009-06-15 17:19 ` jwakely dot gcc at gmail dot com
2009-06-15 17:20 ` pinskia at gcc dot gnu dot org
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-40447-4-tsvP7cIPEF@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).