Date: Wed, 23 Jan 2019 14:32:28 +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@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235158 Bug ID: 235158 Summary: lang/lua53 no longer linked against pthread Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: i+fbsd@amlegion.org CC: russ.haley@gmail.com Flags: maintainer-feedback?(russ.haley@gmail.com) CC: russ.haley@gmail.com Prior to this, maintaining my own package repository, building lua53, apparently it was linked against pthreads. Changes in the FreeBSD 12 ports system may have caused this? The issue is that it *was* previously by default linked against pthreads, so when I did an upgrade to FreeBSD 12 and rebuilt the package repo and upgrad= ed all the packages, all of a sudden some of my lua code stopped working. If it is intended to not by default link against pthreads, then perhaps a package message notifying of this change would be a good idea so people dependent upon the old behaviour will know they need to build their own lua= if they depended on anything that might create new lua states in threads. If this was unintended then fixing the patch files in the ports to patch the makefile again with '-pthread' in ldflags would be sufficient likely to mitigate this issue. For now, the only workaround is to build your own lua. When lua is not linked against pthreads, and a thread is started, and a new= lua state is created in a thread, lua will hang completely. --=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>