See the discussion in the bug report and the linked GitHub issue.
-
-
Replying to @emtiu @FreeBSDHelp
I don't see there any proper analysis of why linking against libthr is either required or desirable. In my experience adding it blindly because it seems to work that way is just hiding a bug elsewhere.
1 reply 0 retweets 0 likes -
Replying to @RhodiumToad @FreeBSDHelp
If you're in a position to provide such an analysis, I'm sure it will be welcome. I most certainly am not.
1 reply 0 retweets 0 likes -
Replying to @emtiu @FreeBSDHelp
I was right, there is a base system bug here (somewhere between rtld and libthr, again) - further analysis to come
1 reply 0 retweets 1 like -
-
Replying to @FreeBSDHelp @emtiu2 replies 0 retweets 1 like
-
Replying to @RhodiumToad @emtiu
Nice! Not limited to FreeBSD 11 per original bug report (incorrect?) ?
1 reply 0 retweets 0 likes -
Replying to @FreeBSDHelp @emtiu
The real bug is in all versions (at least 11 and current), the original only manifests on 11 because on 12+, openssl pulls in libthr itself, hiding the issue in this case
2 replies 0 retweets 0 likes -
-
So workaround until base issue fixed/release in all branches is add -pthread or is there a better way in the meantime?
1 reply 0 retweets 0 likes
Best workaround I can think of is to ensure that libprotobuf itself is linked to libthr, yes. As it stands it will not work without libthr (even though it creates no threads).
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
