Arch Linux

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!
Tasklist

FS#22471 - [boost-libs] no libboost_thread.so

Attached to Project: Arch Linux
Opened by Mr.Magne (Mr.Magne) - Monday, 17 January 2011, 18:36 GMT
Last edited by Ionut Biru (wonder) - Friday, 04 March 2011, 13:11 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Kevin Piche (kpiche)
Ionut Biru (wonder)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,
Would it be possible to have a symbolic link from libboost_thread-mt.so to libboost_thread.so, to ease compatibility when compiling/linking projects developed with another configuration ?
Every other boost lib has the two variants, and even if it makes no sense to use thread without mt, some people compile without suffix...
This task depends upon

Closed by  Ionut Biru (wonder)
Friday, 04 March 2011, 13:11 GMT
Reason for closing:  Fixed
Additional comments about closing:  boost 1.46. now in testing
Comment by Thomas Dziedzic (tomd123) - Monday, 17 January 2011, 19:34 GMT
wouldn't this be more of an upstream issue with either boost, or with the projects that use the wrongly named .so?
Comment by Greg (dolby) - Monday, 17 January 2011, 19:47 GMT
The applications looking for -mt.so are the broken ones, not vice versa.
Comment by Thomas Dziedzic (tomd123) - Monday, 17 January 2011, 20:29 GMT
so boost is wrong?
Comment by Greg (dolby) - Monday, 17 January 2011, 20:48 GMT
The boost libraries are multithreaded even without the -mt suffix.
Applications looking specifically for -mt in the .so are broken IMO.
Anyway this is mostly offtopic.
Comment by Jan de Groot (JGC) - Monday, 17 January 2011, 22:19 GMT
It seems we build boost for singlethreaded and multithreaded environments, so that means that all -mt libs are threadsafe, and the ones without -mt aren't. As there's no libboost_thread.so library for non-threadsafe builds, we're missing that library.
Is there any reason why we build threadsafe and non-threadsafe libraries and use layout=tagged? Isn't it easier to just build threadsafe by default and use layout=system? That way we get rid of the -mt suffix.
Comment by Thomas Dziedzic (tomd123) - Sunday, 27 February 2011, 05:11 GMT
I spoke with #boost and they said there really isn't any reason why we should build with singlethreaded/multithreaded as opposed to just multithreaded, so I'm all for this. I'm currently working on a PKGBUILD to update boost, fix this and add mpi libs.

Loading...