On Sun, Nov 25, 2018 at 09:32:33PM -0800, Philip Guenther wrote: > On Sun, Nov 25, 2018 at 1:57 AM 岡本健二 <keokn...@gmail.com> wrote: > > > I have to use thread on the perl5 of OpenBSD 6.4. > > However, it was disabled on the distribution. > > > > Hmm, is this something that worked in previous releases, or is something > that you've only tried in OpenBSD 6.4? > > Off-hand, it's still disabled by default in the Configure script that perl > people ship, and I don't see anything in the OpenBSD bits to override their > choice. > > > > > I tried to make the thread active to recompile the perl5 with -Dusethreads, > > which led me to many test fails. > > > > Were there tests that failed with -Dusethreads that passed when that wasn't > used? If so, which, and what was their output? > > To put it another way: if you're suggesting that we build the base perl > with -Dusethreads, what are the consequences of that? Test failures? > Bigger binary? pkg_add is slower? > > > Why the thread function was disabled in this release? > > Is it security reason? > > > > Upstream has it off by default, nothing so far has needed it, and it makes > things slower (or at least that's why upstream says). Why would we enable > it?
No, perl threads is generally considered to be unreliable. Unless this changed recently, there's zero reason to activate it by default. As far as I know, the only reason it still exists is because of less endowed operating systems that do not have fork.