Stream: general

Topic: incremental linker errors


Bastian Kauschke (Apr 17 2020 at 12:28, on Zulip):

I currently run ./x.py test src/test/ui --stage 1 with incremental set to true.

Compilation of state 1 currently fails with :

**  = note: /usr/bin/ld: /home/programming/rust/build/x86_64-unknown-linux-gnu/stage0-rustc/x86_64-unknown-linux-gnu/release/deps/rustc_driver-4b7368d0b3ef4ef3.ec335kezqqkxkzb.rcgu.o: in function `<T as rustc_query_system::dep_graph::dep_node::DepNodeParams<Ctxt>>::to_fingerprint':
          /home/programming/rust/src/librustc_query_system/dep_graph/dep_node.rs:111: undefined reference to `rustc_data_structures::stable_hasher::StableHasher::finish'
          /usr/bin/ld: /tmp/rustc8N4mne/librustc_metadata-1a1dc83ff22fdc9d.rlib(rustc_metadata-1a1dc83ff22fdc9d.4aiayopt0r9irehb.rcgu.o): in function `<T as rustc_query_system::dep_graph::dep_node::DepNodeParams<Ctxt>>::to_fingerprint':
          /home/programming/rust/src/librustc_query_system/dep_graph/dep_node.rs:111: undefined reference to `rustc_data_structures::stable_hasher::StableHasher::finish'
          /usr/bin/ld: /home/programming/rust/build/x86_64-unknown-linux-gnu/stage0-rustc/x86_64-unknown-linux-gnu/release/deps/librustc_driver-4b7368d0b3ef4ef3.so: hidden symbol `_ZN21rustc_data_structures13stable_hasher12StableHasher6finish17hf220c72329c4c00cE' isn't defined
          /usr/bin/ld: final link failed: bad value
          collect2: error: ld returned 1 exit status**

Is this a known issue?

RalfJ (Apr 17 2020 at 16:07, on Zulip):

@Bastian Kauschke no, that's strange. it works for me.

RalfJ (Apr 17 2020 at 16:07, on Zulip):

could your incremental cache be broken? you could try deleting the build/stage* dirs to rebuild that.

Bastian Kauschke (Apr 17 2020 at 16:08, on Zulip):

It is fixed after ./x.py clean

Bastian Kauschke (Apr 17 2020 at 16:08, on Zulip):

could your incremental cache be broken?

I think so

RalfJ (Apr 17 2020 at 16:08, on Zulip):

maybe I dont see it because I tend to aggressively clean

Bastian Kauschke (Apr 17 2020 at 16:18, on Zulip):

how long does a clean build take for you? :ping_pong:

RalfJ (Apr 17 2020 at 16:32, on Zulip):

stage 1? hm, I think around 20min... plus 30min extra if it needs to build LLVM

RalfJ (Apr 17 2020 at 16:32, on Zulip):

by "aggressively" I mean I clean when switching branches or pulling

RalfJ (Apr 17 2020 at 16:33, on Zulip):

basically, when libstd changes, incremental doesnt help anyway, so I clean first and then build

Bastian Kauschke (Apr 17 2020 at 16:35, on Zulip):

stage 1? hm, I think around 20min... plus 30min extra if it needs to build LLVM

uff, seems like my setup kinda sucks then :sweat_smile:

Bastian Kauschke (Apr 17 2020 at 16:36, on Zulip):

by "aggressively" I mean I clean when switching branches or pulling

Jup, this bug came without any changes to libs though. Just between two builds with slight changes in rustc_middle

RalfJ (Apr 17 2020 at 16:39, on Zulip):

Bastian Kauschke said:

by "aggressively" I mean I clean when switching branches or pulling

Jup, this bug came without any changes to libs though. Just between two builds with slight changes in rustc_middle

that should never happen...

Bastian Kauschke (Apr 17 2020 at 16:48, on Zulip):

^ that's why I've asked this here :)

Last update: Jun 05 2020 at 23:10UTC