@FreeBSDHelp There's a ports bug that's been driving me nuts (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239038 …) – now there's a patch tested and ready to commit, but nobody's committing. Any way to speed this up?
-
-
Replying to @emtiu
Can you check if adding CONFIGURE_ENV+=PTHREAD_LIBS="-pthread" to devel/protobuf also works
2 replies 0 retweets 0 likes -
Replying to @FreeBSDHelp
Sure, I can test that. Does CONFIGURE_ENV go in the main Makefile, or where do I set it?
4 replies 0 retweets 0 likes -
Replying to @emtiu
devel/protobuf/Makefile yep. If a global (non conditional) CONFIGURE_ENV line already exists, append THREAD_LIBS="-pthread" to it (with \ as a line separator if needed)
1 reply 0 retweets 0 likes -
Replying to @FreeBSDHelp @emtiu
Is there a proper analysis of why this is needed? blindly adding -pthread is almost always a mistake
1 reply 0 retweets 0 likes -
Replying to @RhodiumToad @FreeBSDHelp
See the discussion in the bug report and the linked GitHub issue.
1 reply 0 retweets 0 likes -
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
I was right, there is a base system bug here (somewhere between rtld and libthr, again) - further analysis to come
-
-
-
Replying to @FreeBSDHelp @emtiu2 replies 0 retweets 1 like
- 3 more replies
New conversation -
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.
