Re: rust 1.94

[Havard Eidnes <he%NetBSD.org@localhost>]

> I gave it a try by building www/chromium and it failed like this:
>
>    Compiling swc_config v0.1.15
> fatal runtime error: out of TLS keys, aborting
> error: could not compile `sourcemap` (lib)
>
> The build continued if I set PTHREAD_KEYS_MAX=1024 in the environment.
> Not sure why it needs to do so many pthread_key_create(3) calls or
> if this is a new regression as I have not tried to build chromium
> before. (I'm adding aarch64 support to chromium).
>
> The default value of PTHREAD_KEYS_MAX looks to be 128. Annoyingly there
> is no way to bump it from rust runtime code after the pthread
> initializers have ran.

Right, I've seen similar issues trying to build rust itself.
I'll need to dig through my build logs as to where I've seen
this (can't exactly recall), but at least I've seen it more than
once in my testing.

> Open questions right now:
>
> - Is this a new problem?

Yes, it's new in rust 1.94.0.

> - Does on only happen on many-core systems?

I'm a little uncertain about that, ref. above.

> - Should we bump the default in NetBSD?

That's an open question.  Linux default value is apparently 1024,
so there they don't notice the increased usage.

> - Do we need to add PTHREAD_KEYS_MAX to the pkgsrc environment for
>   packages that run rustc?

Probably.  lang/rust/rust.mk?

Regards,

- Håvard