Possible rust issue on -current

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

Hi,

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:

RUST_BACKTRACE=full WINIT_UNIX_BACKEND=x11
LD_LIBRARY_PATH=/usr/X11R7/lib:/usr/pkg/lib  ./alacritty
thread 'main' panicked at 'Initializing the event loop outside of the
main thread is a significant cross-platform compatibility hazard. If
you really, absolutely need to create an EventLoop on a different
thread, please use the `EventLoopExtUnix::new_any_thread` function.',
/usr/pkgsrc/wip/alacritty/work/vendor/winit-0.22.2/src/platform_impl/linux/mod.rs:703:9
stack backtrace:
   0:         0x1cf84809 -
<std::sys_common::backtrace::_print::DisplayBacktrace as
core::fmt::Display>::fmt::h696b0c7164c42b89
   1:         0x1ce776ec - core::fmt::write::h3e4f7bb56331df60
   2:         0x1cf7eda6 - std::io::Write::write_fmt::hd6b629b0842160ba
   3:         0x1cf78715 -
std::panicking::default_hook::{{closure}}::h8b30e814058b19b5
   4:         0x1cf7829d -
std::panicking::rust_panic_with_hook::h3062351663ff3949
   5:         0x1cf77f38 - rust_begin_unwind
   6:         0x1cf77ee0 - std::panicking::begin_panic_fmt::h8b1f010f0b35211e
   7:         0x1ccd8d7c -
winit::platform_impl::platform::assert_is_main_thread::h3105b1f3a5f2dee9
                               at
/usr/pkgsrc/wip/alacritty/work/vendor/winit-0.22.2/src/platform_impl/linux/mod.rs:703
   8:         0x1ccd8d7c -
winit::platform_impl::platform::EventLoop<T>::new::h1238e8f8d9d65e9a
                               at
/usr/pkgsrc/wip/alacritty/work/vendor/winit-0.22.2/src/platform_impl/linux/mod.rs:531
   9:         0x1ccd8d7c -
winit::event_loop::EventLoop<T>::with_user_event::h2a9c013754dd7b1e
                               at
/usr/pkgsrc/wip/alacritty/work/vendor/winit-0.22.2/src/event_loop.rs:129
  10:         0x1ccd8d7c - alacritty::main::hde70bbc298dd3f59
                               at alacritty/src/main.rs:81
  11:         0x1cf844b3 -
std::sys_common::backtrace::__rust_begin_short_backtrace::hc4d5a95302ccc82d
  12:         0x1cccfd5e - main
  13:         0x1cc63d3b - ___start

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.

Chavdar




-- 
----