Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#57083 - [boost-libs] boost-libs soname contains full version instead of just major version
Attached to Project:
Arch Linux
Opened by Thomas (tomtix) - Saturday, 13 January 2018, 12:30 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 13 January 2018, 15:59 GMT
Opened by Thomas (tomtix) - Saturday, 13 January 2018, 12:30 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 13 January 2018, 15:59 GMT
|
DetailsDescription:
(The following describe a problem with libboost_system.so but is not specific just to libboost_system.so, rather to all libraries in boost-libs package) Since the last update of the boost-libs package, some applications I compiled previous to the update stopped working because they were "hard-linked" against the library with the full version name: [tmijieux@satsuki ~]$ ./resolver ./resolver: error while loading shared libraries: libboost_system.so.1.65.1: cannot open shared object file: No such file or directory Also, there is no symlink "libboost_system.so.1". The solution adopted by a lot of library is to have "library.so" symlinked to the last version installed, "library.so.X" symlinked to the last "major version X" installed and the soname of "library.so.X.Y.Z" should be "library.so.X" Therefore, when a minor or patch version bump occurs, all applications that were linked against the "library.so" used the soname instead, and does not require any intervention at all the used the new version. Additional info: * version: 1.65.1, 1.66.0 Even if this problem should maybe be addressed in boost build system, I believe the could be addressed here faster because this is more of a distribution problem. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 13 January 2018, 15:59 GMT
Reason for closing: Not a bug
Additional comments about closing: This is how upstream works
Saturday, 13 January 2018, 15:59 GMT
Reason for closing: Not a bug
Additional comments about closing: This is how upstream works
Comment by loqs (loqs) -
Saturday, 13 January 2018, 13:04 GMT
https://abi-laboratory.pro/tracker/timeline/boost/ 1.65.1 is ABI incompatible with 1.65.0 and 1.66.0 so the binaries linked against 1.65.1 needed rebuilding anyway https://www.archlinux.org/todo/boost-1660-rebuild-1/