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/28500] Failure to find libgmp Date: Sun, 06 Mar 2022 15:52:04 +0000 [thread overview] Message-ID: <bug-28500-4717-DJOLD1RENp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28500-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28500 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW --- Comment #7 from Tom Tromey <tromey at sourceware dot org> --- Ok, I think there was a thread about this on gdb-patches last year. For some reason there are two different sets of GMP flags to configure, and gdb doesn't respect the top-level ones: prentzel. ./configure --help|grep gmp --with-gmp-dir=PATH this option has been REMOVED --with-gmp=PATH specify prefix directory for the installed GMP --with-gmp-include=PATH/include plus --with-gmp-lib=PATH/lib --with-gmp-include=PATH specify directory for installed GMP include files --with-gmp-lib=PATH specify directory for the installed GMP library prentzel. ./gdb/configure --help|grep gmp --with-libgmp-prefix[=DIR] search for libgmp in DIR/include and DIR/lib --without-libgmp-prefix don't search for libgmp in includedir and libdir --with-libgmp-type=TYPE type of library to search for (auto/static/shared) So, I suggest trying the ones that gdb/configure reports. Top-level configure will pass these down despite the fact that it doesn't know about them. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-06 15:52 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 [this message] 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-DJOLD1RENp@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: linkBe 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).