[02:48:19] *** Smithx10 <Smithx10!sid243404@gateway/web/irccloud.com/x-ysnhhfdycmnnzwse> has joined #illumos-rust
[05:04:10] *** sjorge_be <sjorge_be!~sjorge@unaffiliated/sjorge> has joined #illumos-rust
[05:04:13] *** sjorge <sjorge!~sjorge@unaffiliated/sjorge> has quit IRC (Ping timeout: 245 seconds)
[05:04:15] *** sjorge_be is now known as sjorge
[16:54:49] <papertigers> jbk: are you planning on opening an illumos PR against rust-lang sometime soon?
[17:01:36] <jbk> yeah, once https://github.com/rust-lang/rust/issues/57724 is fixed
[17:01:48] <jbk> without it, you must manually patch things for it to build
[17:02:02] <jbk> i just updated the work to the latest master
[17:02:20] <jbk> that was probably 12 hours of work
[17:02:26] <jbk> basically each run is 3+ hours
[17:02:28] <jbk> and if it fails
[17:02:31] <jbk> another 3+ hours
[17:02:35] <jbk> until it builds successfully
[17:04:15] <jbk> ...
[17:04:27] <jbk> and there is an unresolved issue of things apparently not trusting semver
[17:04:58] <jbk> so a few things in rust-lang/rust are locked to specific versions of the libc crate
[17:06:16] <jbk> while most things use '0.2', libstd and librustc_codegen_ssa use '0.2.44'
[17:06:36] <jbk> but when i asked, no one could answer why
[18:26:14] <jbk> i don't know if anyone on the rust team would be interested in the experience of trying to bring up a new target_os
[18:26:27] <jbk> but honestly, it's been pretty bad because of all these papercuts
[18:26:34] <jbk> that take weeks to resolve
[18:27:08] <jbk> like the actual writing of the os-specific code was quick and easy
[18:27:35] <jbk> but then getting it to actually build because of the layers of depdenencies rustc has on things

   March 11, 2019  
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | >