Closed Alessandro-Barbieri closed 1 year ago
This has been seen before in some way at #690 - have you re-installed gap-core with the new libtool already? If yes, we'll have to see where in io
there is hard-coding. My main dev machine is off and I won't be able to touch replacements before later today so it may take me until tomorrow before getting to the bottom of it if re-installing gap-core doesn't fix it.
Isn't a way to properly fix this? Maybe using some :=
Using :=
on what? libtools
? One of the issue is of course that upstream wants to use the libtool
used for installing gap
. If I could make that go away, there would not be an issue. I would have to look, there are a number of gap packages that use a proper configure that may be fixable by just adding the required stuff in configure.ac
.
OK, I had to go and look back at it, gac
is the component that wants libtools
. Changing stuff there will require changes to every package using it. Exactly like I said in your commit comment. The only other serious option is to refuse to ship it.
I may have enough freedom to move thing to something like /usr/lib/gap
similar to what R
does. I'll look into that.
In any case, I am expecting re-installing gap-core
would/has fixed your original issue. Right?
Using
:=
on what?libtools
?
Yes
One of the issue is of course that upstream wants to use the
libtool
used for installinggap
. If I could make that go away, there would not be an issue. I would have to look, there are a number of gap packages that use a proper configure that may be fixable by just adding the required stuff inconfigure.ac
.
Isn't possible to use the autotools/libtool eclass to force our libtool version?
It is not that simple. libtools
has to be configured - as far as my understanding goes - so you would have to add it to configure.ac
(LT_INIT
) and then, yes, use the autotools eclass to regenerate things. Going that way suppose that all concerned packages have a configure.ac
and if not, to provide a minimal one somehow.
In any case, I am expecting re-installing
gap-core
would/has fixed your original issue. Right?
Yes
Using
:=
on what?libtools
?Yes
For the record, I just had a quick look. There is no adequate sublot on libtool to make it work. It also would prevent using slibtool instead (we'd probably need a virtual for that anyway).
Things may not be as bad as I think. But that would require an "artful" upgrade path - again.
gac
is not using libtool
anymore in current GAP versions (4.12.0 and upwards)
So I'd hope this issue here is resolved.
This definitely can be closed. Nice to know those mismatch will not happen anymore.