public inbox for
 help / color / mirror / Atom feed
From: Simon Sobisch <>
Subject: Re: --with-gmp and --with-libgmp-prefix
Date: Tue, 15 Mar 2022 11:37:26 +0100	[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-
 >> gdbconfigure 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. [...]
 >> 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 
 > 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.

Hm, maybe in this case one can opt for the binutils style with keeping 
the GDB one "for compat"?
In theory this would add one additional "feature" - the possibility to 
specify the header and library path independently.

In this case the help for -with-libgmp-prefix could just say something 
like "alias for --with-gmp".

Just saying...


      parent reply	other threads:[~2022-03-15 10:37 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
2022-03-15 10:37   ` Simon Sobisch [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:

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