public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "Mario.Klebsch@ime-actia.de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/27762] New: configure does not honor --with-mpfr=
Date: Wed, 21 Apr 2021 15:26:51 +0000	[thread overview]
Message-ID: <bug-27762-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27762
           Summary: configure does not honor --with-mpfr=
           Product: gdb
           Version: 10.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: Mario.Klebsch@ime-actia.de
  Target Milestone: ---

I built mpc and libmpr as static libraries and installed them into a temprary
location.

I passed --with-mpfr=/... and  --with-mpc=/... to configure.

I expected the build process to pick up the static libraries provided at the
given locations.

But the resulting binary uses the shared libraries insalled in /lib64. 

gdb/Makefile was written with this line:

LIBMPFR = -lmpfr -lgmp

I configured and build gcc with the same options, and gcc uses the static
libraries. In the gcc build directory gcc/Makefile contains the following line:

GMPLIBS = -L/.../lib -L/.../lib -L/.../lib -lmpc -lmpfr -lgmp

The difference is, that gcc's configure added -L options with the path of the
static libraries.

The config.log does contain a setting with -L options:
gmplibs='-L/.../lib -L/.../lib -L/.../lib -lmpc -lmpfr -lgmp'

but this setting is not used when building gdb. :-(

I just found, that there also is a config.log in the gdb subdirectory. I see,
that  '--with-gmp=/...' '--with-mpfr=/...' were passed tot he sub-configure.

But I see, that this path is not used:

configure:10086: checking whether to use MPFR
configure:10088: result: /...
configure:10521: checking for libmpfr
configure:10541: gcc -o conftest -g -O2    conftest.c -ltinfow -lncursesw -lm
-ldl  -lmpfr -lgmp >&5
configure:10541: $? = 0
configure:10551: result: yes
configure:10558: checking how to link with libmpfr
configure:10560: result: -lmpfr -lgmp

It just detects the system-supplied mpfr and don't use the one, that I selected
on configures command line. :-(

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

             reply	other threads:[~2021-04-21 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 15:26 Mario.Klebsch@ime-actia.de [this message]
2022-03-06 16:00 ` [Bug build/27762] " tromey at sourceware dot org
2022-03-06 16:00 ` 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-27762-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).