On Sun, Aug 20, 2017 at 05:11:52PM +1000, Wayne Blaszczyk wrote: > On Fri, 2017-08-18 at 21:18 +0100, Ken Moffat wrote: > > Following my previous mail to -dev, I've spent some more time > > looking at rust, but I cannot bootstrap *any* newer release than > > what is in the book (all die within a few seconds of starting to try > > to build things). > > > > Hi Ken, > > I have not been following this thread, but seeing this email, > I thought I'd give it a try, and eventually succeed. > Prior to this build, the environment did not have an older version of > rust or cargo installed. The environment was based on LFS-8.0 and not dev. > > ./configure --prefix=/usr \ > --docdir=/usr/share/doc/rustc-1.19.0 \ > --release-channel=stable \ > --llvm-root=/usr \ > --enable-llvm-link-shared > ./x.py build > ./x.py install > > llvm version was 4.0.1 > > If you like, I can post you my logs. Where is it breaking for you? > > Regards, > Wayne. > Hi Wayne, thanks for responding.
I've just given it some more tries, and all failed the same way. Your configure differs from mine by pointing to llvm in /usr, so I have also tried with llvm in /opt/llvm3 (and /opt/llvm3 at the front of the PATH), not specifying llvm (that should use the shipped llvm and probably cross-compile for all possible targets), and also your commands above (this is on LFS-8.1-rc2, so I too have llvm-4.0.1 in /usr). Here is the full output from ./x.py on the version where I didn't mention llvm in the configure, but as I say, all failed the same way: :--begin ken@ac4tv /tmp/rust-1.19.0 $time ./x.py build 2>&1 downloading https://static.rust-lang.org/dist/2017-06-08/rust-std-1.18.0-x86_64-unknown-linux-gnu.tar.gz ######################################################################## 100.0% extracting /tmp/rust-1.19.0/build/cache/2017-06-08/rust-std-1.18.0-x86_64-unknown-linux-gnu.tar.gz downloading https://static.rust-lang.org/dist/2017-06-08/rustc-1.18.0-x86_64-unknown-linux-gnu.tar.gz ######################################################################## 100.0% extracting /tmp/rust-1.19.0/build/cache/2017-06-08/rustc-1.18.0-x86_64-unknown-linux-gnu.tar.gz downloading https://static.rust-lang.org/dist/2017-06-08/cargo-0.19.0-x86_64-unknown-linux-gnu.tar.gz ######################################################################## 100.0% extracting /tmp/rust-1.19.0/build/cache/2017-06-08/cargo-0.19.0-x86_64-unknown-linux-gnu.tar.gz error: failed to read `/tmp/rust-1.19.0/src/tools/rust-installer/Cargo.toml` Caused by: No such file or directory (os error 2) failed to run: /tmp/rust-1.19.0/build/x86_64-unknown-linux-gnu/stage0/bin/cargo build --manifest-path /tmp/rust-1.19.0/src/bootstrap/Cargo.toml Build completed unsuccessfully in 0:00:21 :--end My md5sum for rust-1.19.0.tar.gz is 4583d5810db608dbe315099fe8cefaac I've just downloaded a second copy in case mine was borked, but it has the same md5sum. I do know how to get past that first error of the missing src/tools/rust-installer.Cargo.toml (use rust-installer-master.zip from github, the src/tools/rust-installer directory in the shipped 1.19.0 is empty). But after doing that last week my attempts then failed to read src/tools/cargo/Cargo.toml (again that directory is empty). And after that I tried installing current cargo (worked, but didn't help) and then playing with the toplevel config.toml but got nowhere. Along the way, on that system I renamed the installed rustc and cargo on that system, but that made no difference. So obviously you and I have some other difference in what we are doing, and it is probably soemthing wrong at my end (because people appear to be able to bootstrap 1.19.0 on gentoo). ĸen -- I live in a city. I know sparrows from starlings. After that everything is a duck as far as I'm concerned. -- Monstrous Regiment -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
