Date: Wed, 23 Jan 2019 20:14:20 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 235158] lang/lua53 no longer linked against pthread Message-ID: <bug-235158-7788-AsxpulNGsL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235158-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-235158-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235158 --- Comment #2 from Russell Haley <russ.haley@gmail.com> --- Hi,=20 I'm the Lua53 package maintainer. I'm relatively new to maintaining a packa= ge (and not great at C to be honest) so you'll have to bare with me.=20 I have notes in the review about the decision to remove -pthread: https://reviews.freebsd.org/D13690 I did a fair bit of research, though obviously it wasn't complete:=20 - Conversations on the Lua mailing list indicated that there should be no n= eed to include pthread as Lua itself has no requirement for it. The Lua interpr= eter is not involved in the threading, it's simply a client library. - I found a conversation on a Fedora list where they removed pthread which seemed to validate the conversation above. From memory, I believe the Fedora user in question changed their linking strategy to accommodate threading. - As noted in the review, the -pthread issue seemed to be with a FreeBSD bug and my testing indicated that bug was no longer an issue so pthread was rem= oved (details in the review noted above). In the end, I felt that requiring pthread was outside the use case for a general package and was non-standard enough that it should be removed and l= eft to a developer to build their own.=20 I also assumed that if it becomes an issue, someone would speak up, so here= you are! I see a couple of avenues available: 1) Perhaps you should ask on the lua mailing list about your specific use c= ase and if pthread *should* be required. That would validate this as a FreeBSD issue. 2) A deep dive on a mailing list or IRC to determine what about FreeBSD is causing the problem. 3) If required, an option/flag could be added to the port to toggle pthread= .=20 If a deeper understanding of the problem is required, there is another user that may be able to help but I'll hold off on volunteering him until we get more clarity.=20 I'm happy to help in any way I can. Thoughts? Russ --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235158-7788-AsxpulNGsL>