On Thu, 7 Apr 2022, George N. White III wrote:
On Thu, 7 Apr 2022 at 19:42, Michael Hennebry <
hennebry(a)web.cs.ndsu.nodak.edu> wrote:
> /usr/bin/ld: cannot find -lmpfr
>
> As mentioned in another thread, I am trying to compile gappa 1.4 .
> ./configure LDFLAGS=-L/usr/lib64 complains
>
>
> From config.log
> configure:4678: checking for mpfr_snprintf in -lmpfr
> configure:4703: g++ -o conftest -g -O2 -L/usr/lib64/ conftest.cpp -lmpfr
> -lgmp
>> &5
> /usr/bin/ld: cannot find -lmpfr
> collect2: error: ld returned 1 exit status
>
> [hennebry@fedora ~]$ ls /usr/lib64/libmpfr*
> /usr/lib64/libmpfr.so.6 /usr/lib64/libmpfr.so.6.1.0
> [hennebry@fedora ~]$
>
> What is going on?
> How do I deal?
When trying to install a newer version of some program than dnf
provides,
it is often
helpful to "borrow" from the source RPM. As already mentioned, you
certainly need
the mpfr-devel package.
Why?
I am not trying to build or edit mpfr.
The error message in config.log says that it was
looking for the symbol mpfr_snprintf in -lmpfr .
It did not even find -lmpfr .
Why not?
Even if I am persuaded to get the mpfr-devel
package and suddenly the build worked,
that would still leave me wondering why ld could
not find a library in a place it was told to look.
Is there an ld flag that will cause it to say where it looks for libraries?
I've been looking, but might have missed it.
I use mpfr, gmp, and boost in Fedora 35 (so already have the -devel
libraries).
Running configure with no options as suggested in the documentation "works
for me":
I tried that first.
Edit configure.in.
A sensible suggestion if I can figure out what to do to it.
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
-- someeecards