On 12-03-29 11:57 AM, Graydon Hoare wrote:

> Ralph, is the error transient? If you clean and redo it, it fails the
> same way consistently? Are there any other rust artifacts in the build
> dir or local install path?

After some diagnosis this seems to be an atom-specific bug in the
optimizer. This is filed as https://github.com/mozilla/rust/issues/2078
now. I think it's likely just
https://github.com/mozilla/rust/issues/1879 in different clothing, but
either way, atom-specific and with a --disable-optimize workaround makes
for "not a showstopper" to me.

> (I'll fix the text in INSTALL.txt, of course, sigh)

Fixed on trunk, not in that tarball. But I think users will figure it out :)

Thanks for all the diagnostic help! At some point maybe we'll get a
reasonable array of subtargets into our build farm. Mmm, combinatorial
explosion...

-Graydon
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to