You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that the .pcfile generated by the pkg-config call in libssh2-sys's build.rs includes absolute paths to the build directory. This causes issues for build systems that check the build output for reproducibility (and my particular case leads to cache misses for prebuilt artifacts).
Would things break if the paths were relative or if the .pc file simply wasn't generated? I'm using this as a workaround for now:
This adds a patch that prevents `libssh2-sys` from generating a `.pc`
file. The pkg-config file includes absolute paths which makes it
non-deterministic.
See: alexcrichton/ssh2-rs#340
This adds a patch that prevents `libssh2-sys` from generating a `.pc`
file. The pkg-config file includes absolute paths which makes it
non-deterministic.
See: alexcrichton/ssh2-rs#340
This adds a patch that prevents `libssh2-sys` from generating a `.pc`
file. The pkg-config file includes absolute paths which makes it
non-deterministic.
See: alexcrichton/ssh2-rs#340
---------
Co-authored-by: IDX GitHub Automation <[email protected]>
Hi,
I've noticed that the
.pc
file generated by thepkg-config
call inlibssh2-sys
'sbuild.rs
includes absolute paths to the build directory. This causes issues for build systems that check the build output for reproducibility (and my particular case leads to cache misses for prebuilt artifacts).Would things break if the paths were relative or if the
.pc
file simply wasn't generated? I'm using this as a workaround for now:The text was updated successfully, but these errors were encountered: