Stream: t-compiler

Topic: more tools errors?


nagisa (Dec 06 2018 at 16:57, on Zulip):

Has anybody seen this one yet?

nagisa (Dec 06 2018 at 16:57, on Zulip):
error[E0133]: initializing type with `rustc_layout_scalar_valid_range` attr is unsafe and requires unsafe function or block
   --> /home/nagisa/.cargo/registry/src/github.com-1ecc6299db9ec823/rustc-ap-rustc_target-297.0.0/abi/mod.rs:830:1
    |
830 | / newtype_index! {
831 | |     pub struct VariantIdx { .. }
832 | | }
    | |_^ initializing type with `rustc_layout_scalar_valid_range` attr
    |
    = note: initializing a layout restricted type's field with a value outside the valid range is undefined behavior
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
nagisa (Dec 06 2018 at 16:58, on Zulip):

this is while "building stage2 tool rustfmt"

kennytm (Dec 06 2018 at 17:48, on Zulip):

this is expected https://github.com/rust-lang/rust/pull/55635#issuecomment-444224734

nagisa (Dec 06 2018 at 17:49, on Zulip):

Is thereā€¦ a way to work around this??

nagisa (Dec 06 2018 at 17:49, on Zulip):

god, I never expected working on whatever x.py dist does would be such a chore :D

kennytm (Dec 06 2018 at 18:00, on Zulip):

you'll need to wait for RLS update its rustc-ap-rustc_target dependency... or just don't build the extended tools :P

nagisa (Dec 06 2018 at 18:02, on Zulip):

@kennytm alas, working on the processes that produce tarballs involves exactly that :frown:

Last update: Nov 21 2019 at 13:45UTC