public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "64m at tutamail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/28500] New: Failure to find libgmp
Date: Tue, 26 Oct 2021 18:34:41 +0000	[thread overview]
Message-ID: <bug-28500-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28500
           Summary: Failure to find libgmp
           Product: gdb
           Version: 11.1
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: 64m at tutamail dot com
  Target Milestone: ---

I have tried to compile GDB 11.1. Libgmp is not found even I specified path to
it. 

Error:
configure: error: GMP is missing or unusable

Configured with:
../../src/gdb-11.1/configure --prefix=/home/mapniv/prog/riscv64-gdb
--target=riscv64-none-elf --with-gmp-include=/home/mapniv/prog/gmp/include
--with-gmp-lib=/home/mapniv/prog/gmp/lib --with-mpc=/home/mapniv/prog/mpc
--with-mpfr=/home/mapniv/prog/mpfr

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

             reply	other threads:[~2021-10-26 18:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 18:34 64m at tutamail dot com [this message]
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
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@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).