Closed Timmmm closed 1 day ago
Why is your PKG_CONFIG_PATH changing?
0.053398653s INFO prepare_target{force=false package_id=openssl-sys v0.9.104 target="build-script-main"}: cargo::core::compiler::fingerprint: dirty: EnvVarChanged { name: "PKG_CONFIG_PATH", old_value: Some("/opt/rh/gcc-toolset-12/root/usr/lib64/pkgconfig:/opt/rh/gcc-toolset-12/root/usr/lib64/pkgconfig"), new_value: Some("/opt/rh/gcc-toolset-12/root/usr/lib64/pkgconfig:/opt/rh/gcc-toolset-12/root/usr/lib64/pkgconfig:/opt/rh/gcc-toolset-12/root/usr/lib64/pkgconfig") }
Ah good spot! It's because I have this in my .bashrc
:
source /opt/rh/gcc-toolset-12/enable
I guess it just appends to PKG_CONFIG_PATH
, and for some reason rust-analyzer
and my shell have a different number of nested Bash sessions or something? That is kind of annoying; I can't really think of a good way to solve this so I guess I'll close it & fix my .bashrc
. Would be nice if Cargo had slightly more readable & easy to access output for this at least!
Thanks for the help!
Reopening #543
This is easy to reproduce:
You must have
rust-analyzer
installed in VSCode.You'll see that it rebuilds
openssl-sys
even though nothing changed there.Fingerprint debug log:
It's something to do with
rust-analyzer
, but it still shouldn't happen.rust-analyzer
doesn't cause unnecessary rebuilds of other crates. Potentially a bug withrust-analyzer
but I'm not sure.