Hey kids! If you’re statically linking OpenSSL on FreeBSD, don’t forget to link in -lthr as otherwise it will crash and simply give you a hard time. This has been a public service announcement by those who sometimes use static linking.
-
-
Replying to @petesh
@RhodiumToad is this the same class of/exact issue as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239038 … or something else?2 replies 0 retweets 0 likes -
Replying to @koobs @RhodiumToad
Pretty much the same issue; it’s a tad non-intuitive when things just crash at random.
1 reply 0 retweets 0 likes -
Replying to @petesh @RhodiumToad
Highly. We've (freebsd) seen plenty of incarnations of this class of issue for a long time. Getting to the root-cause bottom of things for all (most) cases without cludges or workarounds has been tough.
@RhodiumToad's analysis has proven very valuable1 reply 0 retweets 0 likes -
I noticed that fbsd 12's base openssl links with libthr by default (when dynamic linking), but I have not investigated why that is the case or whether it can be fixed. There are many cases where linking libthr has just been blindly added as a workaround
1 reply 0 retweets 0 likes -
In the case of libcrypto, the commit "link libcrypto with pthread" (r338816) has absolutely no explanation of why this was done or why it might be needed.
1 reply 0 retweets 0 likes
However, the bug that @koobs linked to above is only relevant for c++. A number of libthr bugs have been fixed since 12.0 though.
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.