Re: Possible rust issue on -current

2020-08-20 Thread Chavdar Ivanov
On Thu, 20 Aug 2020 at 05:10, Tobias Nygren wrote: > > On Thu, 20 Aug 2020 05:04:37 +0200 > Tobias Nygren wrote: > > > 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

Re: Possible rust issue on -current

2020-08-19 Thread Tobias Nygren
On Thu, 20 Aug 2020 05:04:37 +0200 Tobias Nygren wrote: > 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

Re: Possible rust issue on -current

2020-08-19 Thread Tobias Nygren
On Wed, 19 Aug 2020 22:14:09 +0100 Chavdar Ivanov 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

Possible rust issue on -current

2020-08-19 Thread Chavdar Ivanov
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