Re: firefox-112

[Taylor R Campbell <campbell+netbsd-pkgsrc-users%mumble.net@localhost>]

> Date: Tue, 23 May 2023 15:43:51 +0200
> From: Tobias Nygren <tnn%NetBSD.org@localhost>
> 
> On Wed, 10 May 2023 10:18:01 +0100
> Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
> 
> > Any recent ideas about this? Frankly, this version is next to unusable
> > until this is resolved; perhaps downgrade firefox to the last known
> > working version until a solution is found?
> 
> USE_GLX_TLS should maybe be backed out in xsrc until someone has
> time to investigate it. I unfortunately do not have time to look into
> this in the near future. It might be worthwhile to try to merge this
> fix (please try and report back if it helps):
> 
> https://github.com/NetBSD/pkgsrc/commit/0e33e24256c28aed530eb25e07d1c2f23bdf1e12

I don't think we're even using TLS in pkgsrc Mesa.  If you examine nm
and objdump output, you'll see that it uses the C11 tss(3) fallback
instead.

https://mail-index.netbsd.org/pkgsrc-users/2023/04/24/msg037180.html

It looks like nia@ disabled TLS in Mesa on everything other than
Linux/glibc in mid-2020, with the package option `elf-tls' to enable
it.

Does this affect the libGL ABI or no?  Can we safely just flip the
switch to use the C11 tss(3) fallback in xsrc without having to bump
the .so major?

Side note: It appears the upstream macro has been changed from
GLX_USE_TLS to USE_ELF_TLS (never USE_GLX_TLS!).  We should maybe be
consistent about this!