public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sourceware at boris dot nikolaus.name" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/28500] Failure to find libgmp
Date: Thu, 28 Jul 2022 15:40:50 +0000 [thread overview]
Message-ID: <bug-28500-4717-NrUBa1mvc8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28500-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28500
Boris N. <sourceware at boris dot nikolaus.name> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sourceware at boris dot nikolaus.n
| |ame
--- Comment #13 from Boris N. <sourceware at boris dot nikolaus.name> ---
Bug still exists in gdb 12.1.
> So, I suggest trying the ones that gdb/configure reports [i.e. --with-gmp-prefix=DIR].
This only works if includes and libraries can be found in DIR/include and
DIR/lib which is not always the case. E.g. for multi-arch systems the library
path may be in DIR/lib32 or DIR/lib64. It would be nice if the gdb/configure
could support the settings passed from the top configure via
--with-gmp-include/--with-gmp-lib options. (Same applies to libmpfr which can
be specified with --with-mpfr-* configure options but are ignored in
gdb/configure.)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-28 15:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 18:34 [Bug build/28500] New: " 64m at tutamail dot com
2021-10-26 18:50 ` [Bug build/28500] " 64m at tutamail dot com
2021-10-26 18:52 ` 64m at tutamail dot com
2022-02-27 20:54 ` tromey at sourceware dot org
2022-03-06 9:55 ` 64m at tutamail dot com
2022-03-06 10:42 ` 64m at tutamail dot com
2022-03-06 10:44 ` 64m at tutamail dot com
2022-03-06 15:52 ` tromey at sourceware dot org
2022-03-06 15:54 ` tromey at sourceware dot org
2022-03-06 16:09 ` tromey at sourceware dot org
2022-03-06 16:09 ` tromey at sourceware dot org
2022-03-06 16:09 ` tromey at sourceware dot org
2022-05-02 20:13 ` karel.gardas at centrum dot cz
2022-07-28 15:40 ` sourceware at boris dot nikolaus.name [this message]
2022-07-28 16:02 ` simon.marchi at polymtl dot ca
2022-11-08 2:58 ` pinskia at gcc dot gnu.org
2022-11-08 3:01 ` pinskia at gcc dot gnu.org
2022-11-08 7:26 ` pinskia at gcc dot gnu.org
2022-11-08 8:03 ` pinskia at gcc dot gnu.org
2022-11-08 16:30 ` pinskia at gcc dot gnu.org
2022-12-21 16:51 ` cvs-commit at gcc dot gnu.org
2022-12-21 16:55 ` pinskia at gcc dot gnu.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-28500-4717-NrUBa1mvc8@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).