4:50 p.m.
nm: /usr/lib64/libmpfr.so.6: no symbols
I recently changed to F35 partly in the hope it would have gappa 1.4
instead of F33's gappa 1.3 .
No such luck, so I am trying to build from source.
./configure complains
checking for mpfr_snprintf in -lmpfr... no
configure: error: *** Unable to find MPFR (>=2.4) library
(http://www.mpfr.org/)
hennebry@fedora ~]$ locate mpfr.so
/usr/lib64/libmpfr.so.6
/usr/lib64/libmpfr.so.6.1.0
[hennebry@fedora ~]$ nm -a /usr/lib64/libmpfr.so.6
nm: /usr/lib64/libmpfr.so.6: no symbols
[hennebry@fedora ~]$ nm -a /usr/lib64/libmpfr.so.6.1.0
nm: /usr/lib64/libmpfr.so.6.1.0: no symbols
[hennebry@fedora ~]$
[hennebry@fedora ~]$ strings /usr/lib64/libmpfr.so.6.1.0 | grep mpfr_snprintf
mpfr_snprintf
What is going on?
With no symbols, how is the library ever used?
I'd thought nm -a was supposed to list all of them.
BTW I did eventually realize that libmpfr.so.6 is a soft link to the other.
--
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
4:54 p.m.
On 4/7/22 14:50, Michael Hennebry wrote:
nm: /usr/lib64/libmpfr.so.6: no symbols
I recently changed to F35 partly in the hope it would have gappa 1.4
instead of F33's gappa 1.3 .
No such luck, so I am trying to build from source.
./configure complains
checking for mpfr_snprintf in -lmpfr... no
configure: error: *** Unable to find MPFR (>=2.4) library
(http://www.mpfr.org/)
For compiling, you need to to install the devel package, so "mpfr-devel"
in this case.
4:58 p.m.
On Thu, 7 Apr 2022, Michael Hennebry wrote:
nm: /usr/lib64/libmpfr.so.6: no symbols
What is going on?
With no symbols, how is the library ever used?
I'd thought nm -a was supposed to list all of them.
Never mind.
man nm lied to me.
-D is required for the symbols that matter.
Now all I have to do is figure out why gappa's configure did not find them.
--
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
6:34 p.m.
On Thu, Apr 7, 2022 at 3:50 PM Michael Hennebry
<hennebry(a)web.cs.ndsu.nodak.edu> wrote:
I recently changed to F35 partly in the hope it would have gappa 1.4
instead of F33's gappa 1.3 .
No such luck, so I am trying to build from source.
I did not update F35 and below to gappa 1.4 because of some
incompatibilities. Fedora 36 will have version 1.4.
What is going on?
With no symbols, how is the library ever used?
I'd thought nm -a was supposed to list all of them.
BTW I did eventually realize that libmpfr.so.6 is a soft link to the other.
Did you see Samuel Sieb's message? He pointed you to the issue.
--
Jerry James
http://www.jamezone.org/
9:56 p.m.
On Thu, 7 Apr 2022, Jerry James wrote:
On Thu, Apr 7, 2022 at 3:50 PM Michael Hennebry
<hennebry(a)web.cs.ndsu.nodak.edu> wrote:
> I recently changed to F35 partly in the hope it would have gappa 1.4
> instead of F33's gappa 1.3 .
> No such luck, so I am trying to build from source.
I did not update F35 and below to gappa 1.4 because of some
incompatibilities. Fedora 36 will have version 1.4.
Can you say what they were?
To me, that might be good news.
I gave 1.3 a file that caused apparently infinite recursion.
If 1.4 is that different, it might work better.
Is there a forum, a user group or something for gappa users?
> What is going on?
> With no symbols, how is the library ever used?
> I'd thought nm -a was supposed to list all of them.
As noted in another post, man nm lied to me.
nm needed -D .
> BTW I did eventually realize that libmpfr.so.6 is a soft link to
the other.
Did you see Samuel Sieb's message? He pointed you to the issue.
As noted in another post, it did not make sense to me.
--
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
10:14 p.m.
On Thu, Apr 7, 2022 at 8:57 PM Michael Hennebry
<hennebry(a)web.cs.ndsu.nodak.edu> wrote:
Can you say what they were?
To me, that might be good news.
I gave 1.3 a file that caused apparently infinite recursion.
If 1.4 is that different, it might work better.
I don't see anything in the release notes that suggests that might be
the case. See https://gitlab.inria.fr/gappa/gappa/-/blob/master/NEWS.md.
Honestly, I don't remember what I was worried about now. Maybe it was
the change in precedence of unary minus? I guess it must have been.
The other changes seem innocuous.
In any case, if you think you are triggering infinite recursion, try
filing a bug here: https://gitlab.inria.fr/gappa/gappa/-/issues.
Is there a forum, a user group or something for gappa users?
The gitlab project is the only resource I know about.
Regards,
--
Jerry James
http://www.jamezone.org/
3:51 p.m.
On Thu, 7 Apr 2022, Jerry James wrote:
On Thu, Apr 7, 2022 at 8:57 PM Michael Hennebry
<hennebry(a)web.cs.ndsu.nodak.edu> wrote:
> Can you say what they were?
> To me, that might be good news.
> I gave 1.3 a file that caused apparently infinite recursion.
> If 1.4 is that different, it might work better.
I don't see anything in the release notes that suggests that might be
the case. See https://gitlab.inria.fr/gappa/gappa/-/blob/master/NEWS.md.
Honestly, I don't remember what I was worried about now. Maybe it was
the change in precedence of unary minus? I guess it must have been.
The other changes seem innocuous.
The new unary minus seems to be buggy.
I'm getting an assertation error from what seems to be the parser.
My guess is that it is masking the recursion issue.
If I rename my gappa binary,
is there any reason I could not also install the packaged version?
In any case, if you think you are triggering infinite recursion, try
filing a bug here: https://gitlab.inria.fr/gappa/gappa/-/issues.
I'd planned on that, but had not checked on the mechanism.
I'm not an Inria person and would need an
Inria person (yourself?) to invite me.
A configure comment says to report bugs to the author.
Should I do that instead?
--
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
9:30 p.m.
On Sun, Apr 10, 2022 at 2:52 PM Michael Hennebry
<hennebry(a)web.cs.ndsu.nodak.edu> wrote:
The new unary minus seems to be buggy.
I'm getting an assertation error from what seems to be the parser.
My guess is that it is masking the recursion issue.
If I rename my gappa binary,
is there any reason I could not also install the packaged version?
You should be able to do that, yes.
I'd planned on that, but had not checked on the mechanism.
I'm not an Inria person and would need an
Inria person (yourself?) to invite me.
A configure comment says to report bugs to the author.
Should I do that instead?
The author has responded to email in the past, so that's probably
fine. I'm not an inria person, but the author should be able to
invite you if that seems like the best way to go.
--
Jerry James
http://www.jamezone.org/
1:34 a.m.
On 4/7/22 19:56, Michael Hennebry wrote:
On Thu, 7 Apr 2022, Jerry James wrote:
> On Thu, Apr 7, 2022 at 3:50 PM Michael Hennebry
> <hennebry(a)web.cs.ndsu.nodak.edu> wrote:
>> BTW I did eventually realize that libmpfr.so.6 is a soft link to the
>> other.
>
> Did you see Samuel Sieb's message? He pointed you to the issue.
As noted in another post, it did not make sense to me.
I didn't see any relevant message. What doesn't make sense?
"dnf install mpfr-devel"
1:36 a.m.
On 4/7/22 23:34, Samuel Sieb wrote:
On 4/7/22 19:56, Michael Hennebry wrote:
> On Thu, 7 Apr 2022, Jerry James wrote:
>
>> On Thu, Apr 7, 2022 at 3:50 PM Michael Hennebry
>> <hennebry(a)web.cs.ndsu.nodak.edu> wrote:
>>> BTW I did eventually realize that libmpfr.so.6 is a soft link to the
>>> other.
>>
>> Did you see Samuel Sieb's message? He pointed you to the issue.
>
> As noted in another post, it did not make sense to me.
I didn't see any relevant message. What doesn't make sense?
"dnf install mpfr-devel"
Now I see you created a new thread for it.
783
days inactive
787
days old
9 comments
3 participants
participants (3)
-
Jerry James -
Michael Hennebry -
Samuel Sieb