public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sergey.belyashov at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug server/28764] New: Configure should check for libmpc and libmpfr before isl Date: Tue, 11 Jan 2022 14:12:02 +0000 [thread overview] Message-ID: <bug-28764-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28764 Bug ID: 28764 Summary: Configure should check for libmpc and libmpfr before isl Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: sergey.belyashov at gmail dot com Target Milestone: --- I try to configure whole binutils-gdb project. configure succeed, but show following warning: checking for isl 0.15 or later... no required isl version is 0.15 or later *** This configuration is not supported in the following subdirectories: gdbserver (Any other directories should still work fine.) I have installed libisl-0.22 developer files. So I check config.log: configure:6240: checking for isl 0.15 or later configure:6253: gcc -o conftest -g -O2 -lisl -lmpc -lmpfr -lgmp conftest.c -lisl -lgmp >&5 /usr/bin/ld: cannot find -lmpc /usr/bin/ld: cannot find -lmpfr collect2: error: ld returned 1 exit status So there are no libmpc and libmpfr, but warning is about ISL. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-01-11 14:12 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-11 14:12 sergey.belyashov at gmail dot com [this message] 2022-01-11 15:38 ` [Bug server/28764] " schwab@linux-m68k.org 2022-01-11 15:40 ` [Bug build/28764] " schwab@linux-m68k.org 2022-01-11 16:42 ` sergey.belyashov at gmail dot com 2022-01-11 16:43 ` sergey.belyashov at gmail dot com 2022-03-06 16:11 ` tromey at sourceware dot org 2022-03-06 16:13 ` sergey.belyashov at gmail dot com
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-28764-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: 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).