#9530: Improve/fix readline workarounds for Arch Linux and openSuSE, again
broken
on OpenSuSE 11.2 and 11.3
------------------------------+---------------------------------------------
Reporter: baechler | Owner: GeorgSWeber
Type: defect | Status: needs_review
Priority: critical | Milestone: sage-4.6
Component: build | Keywords: Arch Linux SuSE readline
Author: Thomas Bächler | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by leif):
Replying to [comment:32 baechler]:
> Replying to [comment:31 leif]:
> > The situation with readline and bash is even more specific, since it's
IMHO a bad idea to dynamically link the system shell against it, which is
only the case on OpenSuSE and Arch.
>
> Linking the shell dynamically, as far as I know, has been readline's
default for a long time - other distributions just still use
libreadline.so.5 for this.
No, at least some ''statically'' link bash against readline, which is much
safer.
> > But it's also the readline developers' fault, because they changed the
library's interface without bumping the version number.
>
> You are wrong, this is standard and expected behaviour, at least in the
GNU ld world. Increasing the library SONAME version is only required when
a binary compiled against an older library version will fail to work with
a newer version.
In principle, the opposite (a binary requiring some newer version) is the
more common use case.
> In this case, a binary (bash) compiled against a newer library version
does not work with an older library version. This is normal and will be
the case with all system libraries, even the C library in some cases.
Yes, and ''that'' should be catched as well, see above. Therefore one
keeps older library versions installed, with a different "name". But here,
both are "6.0", or worse, the soname recorded as required by bash simply
contains the major number, "6".
> The reason is simple: Nobody ever downgrades system libraries.
This will frequently happen when people install dynamically linked
executables (or even libraries) built on newer systems; usually a packet
manager will take care of also installing the needed libraries, but not
all programs come as packages. into which more specific dependencies are
coded.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9530#comment:33>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
