From: Richard Biener <richard.guenther@gmail.com>
To: Eric Gallager <egall@gwmail.gwu.edu>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][WIP] have configure probe prefix for gmp/mpfr/mpc [PR44425]
Date: Tue, 14 Jun 2022 15:14:00 +0200 [thread overview]
Message-ID: <CAFiYyc2uczYL=gbH270uMuLt0Upj0eoE3kPAFu12tprES73NeQ@mail.gmail.com> (raw)
In-Reply-To: <CAMfHzOuTaq_zHeD6OmLbqMyU1Yg5dafwDSaKkX6D3=u33dLvVw@mail.gmail.com>
On Mon, Jun 13, 2022 at 4:27 PM Eric Gallager <egall@gwmail.gwu.edu> wrote:
>
> On Mon, Jun 13, 2022 at 7:02 AM Richard Biener
> <richard.guenther@gmail.com> wrote:
> >
> > On Thu, Jun 2, 2022 at 5:54 PM Eric Gallager via Gcc-patches
> > <gcc-patches@gcc.gnu.org> wrote:
> > >
> > > So, I'm working on fixing PR bootstrap/44425, and have this patch to
> > > have the top-level configure script check in the value passed to
> > > `--prefix=` when looking for gmp/mpfr/mpc. It "works" (in that
> > > configuring with just `--prefix=` and none of
> > > `--with-gmp=`/`--with-mpfr=`/`--with-mpc=` now works where it failed
> > > before), but unfortunately it results in a bunch of duplicated
> > > `-I`/`-L` flags stuck in ${gmplibs} and ${gmpinc}... is that
> > > acceptable or should I try another approach?
> >
> > --prefix is documented as to be used for installing (architecture
> > independent) files,
> > I'm not sure it is a good idea to probe that for gmp/mpfr/mpc installs used for
> > the host.
> >
> > Richard.
> >
> > > Eric
>
> So... I guess that means we should close bug 44425 as INVALID or
> WONTFIX then? https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44425
That would be my reaction, yes.
prev parent reply other threads:[~2022-06-14 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:53 Eric Gallager
2022-06-09 20:04 ` [PING][PATCH][WIP] " Eric Gallager
2022-06-10 11:22 ` Xi Ruoyao
2022-06-11 14:23 ` Eric Gallager
2022-06-21 3:17 ` Alexandre Oliva
2022-06-13 11:02 ` [PATCH][WIP] " Richard Biener
2022-06-13 14:27 ` Eric Gallager
2022-06-14 13:14 ` Richard Biener [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='CAFiYyc2uczYL=gbH270uMuLt0Upj0eoE3kPAFu12tprES73NeQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=egall@gwmail.gwu.edu \
--cc=gcc-patches@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).