Re: Possible rust issue on -current

[Tobias Nygren <tnn%NetBSD.org@localhost>]

On Wed, 19 Aug 2020 22:14:09 +0100
Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:

Hello,

> pkgsrc/wip/alacritty builds fine under -current, only two warnings for
> obsolete constructs. Apart from the issue of not  getting right the
> shared library locations and the need to run it with LD_LIBRARY_PATH,
> one gets on start:

I've fixed this problem in the alacritty package.

> Thread 'main' panicked at 'Initializing the event loop outside of the
> main thread is a significant cross-platform compatibility hazard.
> The suggestion on https://github.com/alacritty/alacritty/issues/2631
> was that for some reason under NetBSD the detection of whether one is
> on a main thread is incorrect. I wonder if there is anything similar
> seen elsewhere.

This doesn't sound like a rust problem but rather some crate is trying
to do something nonportable while attempting to fix a portability
issue. If it is really important to detect at run time if some code
runs on the main thread (doubtful) you should patch the code to mark
the main thread as such on startup with one of the available portable
thread local storage APIs. Alternatively you can patch out the entire
check from the offending create with a pkgsrc patch if you know for
sure it's initialization is running on the main thread.

-Tobias