It has been established that rustc-1.32.0 needs a newrer LLVM than
the current release (various reports of cargo failures on Arch and
probably fedora, nixos).
https://github.com/rust-lang/rust/issues/57762

But if anyone has installed 1.32.0 with the shipped LLVM (I know
Bruce has), rebuilding with the shipped LLVM make rust unusable.  I
first met this on my main dev machine, and could not establish what
had gone wrong.  Blowing away the rust/cargo binaries and rustlib
(also the docs, for cleanliness) allowed me to install the version
with shipped libraries and then use it.

Meanwhile on my haswell which had been using 1.29.2 with system
LLVM, the update to 1.32.0 with its shipped LLVM went fine, used it
to build firefox.

Now I've gone back to another machine where the version of 1.32.0
with system LLVM had appeared to be ok, and installed 1.32.0 with
its shipped LLVM (because I assume that sooner or later the system
version will break, and I have no way of identifying in my scripts
whether or not rustc is using system LLVM.

Bang!  Trying to build firefox (to test if alsa still works) fails
quickly, again it cannot find the 'std' crate compiled for rustc
1.32.0, only versions compiled for 1.25.0, 1.29.0, 1.29.2.

So here too I need to blow away the installed rust and rustlib.

I vaguely remember that there were issues in the past where I ended
up dropping back to the previous version (perhaps 1.23.0 -> 1.22)
and that Bruce had problems doing that which were fixed by blowing
away his installed rust.

Since 1.32.0 with system libs has never been in the book, I do not
intend to mention this on the rustc page - it is long enough
already.

ĸen
-- 
thread 'main' panicked at 'giraffe',
/tmp/rustc-1.32.0-src/src/test/run-fail/while-panic.rs:17:13
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to