public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/27762] configure does not honor --with-mpfr=
Date: Sun, 06 Mar 2022 16:00:48 +0000	[thread overview]
Message-ID: <bug-27762-4717-dDo30Zuibf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27762-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27762

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
I don't think gdb uses mpc.

For mpfr, it seems to be the same issue as bug#28500: gdb
has a different set of options from the top level.

prentzel. ./configure --help|grep mpfr
  --with-mpfr-dir=PATH    this option has been REMOVED
  --with-mpfr=PATH        specify prefix directory for installed MPFR package.
                          Equivalent to --with-mpfr-include=PATH/include plus
                          --with-mpfr-lib=PATH/lib
  --with-mpfr-include=PATH
  --with-mpfr-lib=PATH    specify directory for the installed MPFR library
prentzel. ./gdb/configure --help|grep mpfr
  --with-mpfr             include MPFR support (auto/yes/no)
  --with-libmpfr-prefix[=DIR]  search for libmpfr in DIR/include and DIR/lib
  --without-libmpfr-prefix     don't search for libmpfr in includedir and
libdir
  --with-libmpfr-type=TYPE     type of library to search for
(auto/static/shared)


Try using the ones reported by gdb - I think that may work.
I tend to think standardizing the options here would be good,
but there are some caveats & problems in this thread

https://sourceware.org/pipermail/gdb-patches/2020-November/173301.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2022-03-06 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 15:26 [Bug build/27762] New: " Mario.Klebsch@ime-actia.de
2022-03-06 16:00 ` tromey at sourceware dot org [this message]
2022-03-06 16:00 ` [Bug build/27762] " tromey at sourceware dot org
2022-03-06 16:09 ` tromey at sourceware 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-27762-4717-dDo30Zuibf@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).