public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "bldenton at buffalo dot edu" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/28625] New: Can't find libgmp during Configure
Date: Thu, 25 Nov 2021 01:04:57 +0000 [thread overview]
Message-ID: <bug-28625-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28625
Bug ID: 28625
Summary: Can't find libgmp during Configure
Product: gdb
Version: 11.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: bldenton at buffalo dot edu
Target Milestone: ---
Created attachment 13804
--> https://sourceware.org/bugzilla/attachment.cgi?id=13804&action=edit
Build Configuration lob
I have an 'unusal' libgmp location. I've specified the directory with /include
and /lib via --with-gmp=/path/to/gmp/directory. I can see in the config.log
file that the correct location is being used in the compilation options but I
still receive the
GMP is missing or unusable error.
It looks like the locations for MPC and MPFR are correctly located via the GCC
dependencies but GMP is not.
I have GCC 11.2 installed with GMP v6.2.1, MPC v1.2.1 and MPFR v4.1.0. Each
installed in their own location.
OS :: Ubuntu 20.04
Thoughts on how I can get GDB v11.1 to install?
configuration log file is attached
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-11-25 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 1:04 bldenton at buffalo dot edu [this message]
2022-02-27 20:53 ` [Bug build/28625] " 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-28625-4717@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).