[Bug 235158] lang/lua53 no longer linked against pthread

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235158

--- Comment #14 from i+fbsd at amlegion.org ---
First thing:

Could we be sure to test this against FreeBSD 12 as well? I'm unsure as to why
it apparently worked just fine in an 11.2 jail under 12, but it did. I probably
can bring up an 11.1 jail too. If you need someone to help when checking
against 12, I volunteer (I keep seeing you both ref 11.* and it sort of seems
as if neither of you have a 12 system to easily test against). That said, tell
me what exactly to test and how, and I'll jump to and get back to you with
results ASAP.

(comment #9)
Sorry as to the test, I apparently depended on a race condition. Glad you found
a way to make it fully deterministic. Threading is hard. Creating a threading
test is harder.

(comment #10)
I really would like at least a workaround for the bug in base in the port until
base is fixed, otherwise we'll be waiting on a patch release or FreeBSD 13 no?

I can understand the reason as to lua-5.3.so now. Is there perhaps a way to
build the lua cli only with pthread, and the rest without?

I would be more than willing to try out any test cases you wish. Do note I'm
running FreeBSD 12 as a host system and can likely get any 11.* jail up you
wish (latest patch only though). So if you wish I can run the tests under
*each* release you deem needed so long as you specify.

(comment #13)
I'll run that test soon and get you the results. I will by default run tests
you specify under FreeBSD 12 only. If you specify other FreeBSD releases to
attempt (probably 11+, I might can even do 10, but no guarantee there) I'll
make every effort to get you the results across ASAP. Also, please note if
something needs to be done outside of a jail (in which case... only FreeBSD 12
is available to me at this time for non-jail cases, although I might can get a
VM going of other releases just that would delay things).

-- 
You are receiving this mail because:
You are the assignee for the bug.