public inbox for
 help / color / mirror / Atom feed
From: Luis Machado <>
To: Joel Brobecker <>
Subject: Re: --with-gmp and --with-libgmp-prefix
Date: Fri, 11 Mar 2022 10:08:30 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <YisfFH/YFTC/>

On 3/11/22 10:06, Joel Brobecker wrote:
>> I was talking to a colleague and we noticed the top-level binutils-gdb
>> configure accepts --with-gmp, which looks like what gcc's configure uses to
>> specify the gmp library installation path.
>> But gdb's configure expects that information to be passed through the
>> --with-libgmp-prefix switch. Was that a deliberate choice (I'm looking at
>> commit 2c947d9bc2ff3b84f1676b83577fe1bba05b4a5f).
>> When one is used to building gcc, it is a little odd to have to specify
>> --with-libgmp-prefix instead of --with-gmp.
>> The top-level configure lists this:
>>    --with-gmp=PATH         specify prefix directory for the installed GMP
>>                            package. Equivalent to
>>                            --with-gmp-include=PATH/include plus
>>                            --with-gmp-lib=PATH/lib
>> And gdb's configure lists this:
>>    --with-libgmp-prefix[=DIR]  search for libgmp in DIR/include and DIR/lib
>> I'm wondering if we can reuse the top-level configure's --with-gmp option.
> Deja vu ;-)


> The problem is that GDB has some shared configury that follows
> a certain style, which is not the style that is used by the toplevel
> configury. This triggered a number of discussions, but in the end
> we found no good solution, unfortunately.
Yeah, that's unfortunate. I was imagining GDB's independent configure 
would have something to do with it. Thanks for clarifying that. And 
sorry for bringing this back again. :-)

  reply	other threads:[~2022-03-11 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  9:47 Luis Machado
2022-03-11 10:06 ` Joel Brobecker
2022-03-11 10:08   ` Luis Machado [this message]
2022-03-15 10:37   ` Simon Sobisch

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).