Rust-0.8 : compilation fails

[eliovir]

Hi,

Whereas I installed Rust-0.7 few days ago without problem, I can't install (./configure; make) the last 0.8 version.

This is where the make process fails:

[..]
...
llvm[3]: Compiling WinCOFFStreamer.cpp for Release+Asserts build
llvm[3]: Building Release+Asserts Archive Library libLLVMMC.a
make[3] : on quitte le répertoire « /var/tmp/portage/dev-lang/rust-0.8/work/rust-0.8/x86_64-unknown-linux-gnu/llvm/lib/MC »
make[2] : on quitte le répertoire « /var/tmp/portage/dev-lang/rust-0.8/work/rust-0.8/x86_64-unknown-linux-gnu/llvm/lib »
make[2] : on entre dans le répertoire « /var/tmp/portage/dev-lang/rust-0.8/work/rust-0.8/x86_64-unknown-linux-gnu/llvm/tools/llvm-config »
llvm[2]: Constructing LLVMBuild project information.
Usage: llvm-build [options]

llvm-build: error: invalid native target: 'x86_64' (not in project)
llvm[2]: Building llvm-config BuildVariables.inc file.
llvm[2]: Compiling llvm-config.cpp for Release+Asserts build
/var/tmp/portage/dev-lang/rust-0.8/work/rust-0.8/src/llvm/tools/llvm-config/llvm-config.cpp:45:35: erreur fatale: LibraryDependencies.inc : Aucun fichier ou dossier de ce type
compilation terminée.
/bin/rm: impossible de supprimer « /var/tmp/portage/dev-lang/rust-0.8/work/rust-0.8/x86_64-unknown-linux-gnu/llvm/tools/llvm-config/Release+Asserts/llvm-config.d.tmp »: Aucun fichier ou dossier de ce type

This message llvm-build: error: invalid native target: 'x86_64' (not in project) is strange.

I tried with GCC-4.6.3 and GCC-4.7.3, with the same result.

I remove Rust-0.7, tried to compile Rust-0.8 : same result.

Finally, I built again Rust-0.7, with success.

[alexcrichton]

Would you mind gisting an entire transcript of the make/configure logs?

[cnd]

This bug on overlay with some additional info: https://github.com/Heather/gentoo-rust/issues/3

[eliovir]

I've just tried to build (with the Gentoo emerge tool) rust-0.8 on an fresh updated system (and faster xeon machine instead of amd64x2). Same result.

This is the build.log : https://gist.github.com/eliovir/6760286

Thanks for your help.

[alexcrichton]

That's interesting... I've seen problems like that when updating an already used rust workspace, but never with a fresh one. It also looks like it's using emake instead of make, and I'm not entirely sure what the difference between the two are.

Do you know if this is building with -jN for some N > 1?

[cnd]

@eliovir trying with -j1 could also be helpful. also if you build with clang then try to build without it... Seems like we just currently have no idea what is happening there for now :S

[eliovir]

I've tried typing

tar zxvf /usr/portage/distfiles/rust-0.8.tar.gz;
cd rust-0.8/;
mkdir dl/;
ln -s /usr/portage/distfiles/rust-stage0-2013-09-23-348d844-linux-x86_64-47906010eb676cbf9e0caa0773d9ef2dce89e9f8.tar.bz2 dl/;
./configure;
make -j1

, the result still is the same.

cfg: build triple x86_64-unknown-linux-gnu
cfg: host triples x86_64-unknown-linux-gnu
cfg: target triples x86_64-unknown-linux-gnu
cfg: enabling more debugging (CFG_ENABLE_DEBUG)
cfg: host for x86_64-unknown-linux-gnu is x86_64
cfg: os for x86_64-unknown-linux-gnu is unknown-linux-gnu
cfg: using gcc
cfg: no pandoc found, omitting docs
cfg: no node found, omitting docs
cfg: no llnextgen found, omitting grammar-verification
cfg: no pandoc found, omitting library doc build
fetch: x86_64-unknown-linux-gnu/stage0/bin/rustc
determined most recent snapshot: rust-stage0-2013-09-23-348d844-linux-x86_64-47906010eb676cbf9e0caa0773d9ef2dce89e9f8.tar.bz2
got download with ok hash
opening snapshot dl/rust-stage0-2013-09-23-348d844-linux-x86_64-47906010eb676cbf9e0caa0773d9ef2dce89e9f8.tar.bz2
extracting rust-stage0/bin/rustc
extracting rust-stage0/lib/libstd-6c65cf4b443341b1-0.8.so
extracting rust-stage0/lib/libextra-a7c050cfd46b2c9a-0.8.so
extracting rust-stage0/lib/librustc-d3cb8c2ccd84a7a7-0.8.so
extracting rust-stage0/lib/libsyntax-64629f7f0c6a9bc-0.8.so
extracting rust-stage0/lib/librustrt.so
extracting rust-stage0/lib/librustllvm.so
compile: x86_64-unknown-linux-gnu/rt/stage0/sync/lock_and_signal.o
compile: x86_64-unknown-linux-gnu/rt/stage0/sync/rust_thread.o
compile: x86_64-unknown-linux-gnu/rt/stage0/rust_builtin.o
compile: x86_64-unknown-linux-gnu/rt/stage0/rust_rng.o
compile: x86_64-unknown-linux-gnu/rt/stage0/rust_upcall.o
compile: x86_64-unknown-linux-gnu/rt/stage0/rust_uv.o
compile: x86_64-unknown-linux-gnu/rt/stage0/miniz.o
compile: x86_64-unknown-linux-gnu/rt/stage0/memory_region.o
compile: x86_64-unknown-linux-gnu/rt/stage0/boxed_region.o
compile: x86_64-unknown-linux-gnu/rt/stage0/arch/x86_64/context.o
compile: x86_64-unknown-linux-gnu/rt/stage0/arch/x86_64/gpr.o
compile: x86_64-unknown-linux-gnu/rt/stage0/rust_android_dummy.o
compile: x86_64-unknown-linux-gnu/rt/stage0/rust_test_helpers.o
compile: x86_64-unknown-linux-gnu/rt/stage0/linenoise/linenoise.o
compile: x86_64-unknown-linux-gnu/rt/stage0/linenoise/utf8.o
compile: x86_64-unknown-linux-gnu/rt/stage0/sundown/src/autolink.o
compile: x86_64-unknown-linux-gnu/rt/stage0/sundown/src/buffer.o
compile: x86_64-unknown-linux-gnu/rt/stage0/sundown/src/stack.o
compile: x86_64-unknown-linux-gnu/rt/stage0/sundown/src/markdown.o
compile: x86_64-unknown-linux-gnu/rt/stage0/sundown/html/houdini_href_e.o
compile: x86_64-unknown-linux-gnu/rt/stage0/sundown/html/houdini_html_e.o
compile: x86_64-unknown-linux-gnu/rt/stage0/sundown/html/html_smartypants.o
compile: x86_64-unknown-linux-gnu/rt/stage0/sundown/html/html.o
cfg: build triple x86_64-unknown-linux-gnu
cfg: host triples x86_64-unknown-linux-gnu
cfg: target triples x86_64-unknown-linux-gnu
cfg: enabling more debugging (CFG_ENABLE_DEBUG)
cfg: host for x86_64-unknown-linux-gnu is x86_64
cfg: os for x86_64-unknown-linux-gnu is unknown-linux-gnu
cfg: using gcc
cfg: no pandoc found, omitting docs
cfg: no node found, omitting docs
cfg: no llnextgen found, omitting grammar-verification
cfg: no pandoc found, omitting library doc build
cfg: including dist rules
cfg: including snap rules
cfg: including clean rules
make[1]: Entering directory `/tmp/rust-0.8'
make[2]: Entering directory `/tmp/rust-0.8/x86_64-unknown-linux-gnu/llvm'
llvm[2]: Constructing LLVMBuild project information.
Usage: llvm-build [options]

llvm-build: error: invalid native target: 'x86_64' (not in project)
make[3]: Entering directory `/tmp/rust-0.8/x86_64-unknown-linux-gnu/llvm/lib/Support'
llvm[3]: Constructing LLVMBuild project information.
Usage: llvm-build [options]

[thestinger]

@eliovir: are you using the unmodified Rust sources?

[eliovir]

@thestinger: Yes, downloaded from the website.

[eliovir]

I've just tried with the current git sources (master), the result still is the same.

[alexcrichton]

It doesn't look your most recent post has the build failure. The llvm-build: error messages probably mean something's going wrong, but they're not stopping the build from what it looks like, could you post the full transcript?

[eliovir]

@alexcrichton : it is always the same. The llvm-build: error yet appeared at https://gist.github.com/eliovir/6760286#file-gistfile1-txt-L799. This error message does not appear during the build of rust-0.7.

[alexcrichton]

Is that the same log where you ran make -j1 explicitly? At the end it says stuff about emake so I just wanted to make sure.

[eliovir]

@alexcrichton : Thanks for you time.

emake is a function for Gentoo ebuild. The gist comes from a Gentoo emerge failure.

Exactly the same output is generated (path excepted) with manual command ./configure; make. The argument -j1 does not change anything.

[alexcrichton]

Out of curiosity, what is the main version of the python command? Also, if you re-run make in the same directory, does it work the second time (sometimes we've seen that).

[eliovir]

The version used by the Makefile is 2.7.5.

If I run another time make in the same directory, the same fatal error about LibraryDependencies.inc stops the build.