On 2022-03-05, Vagrant Cascadian wrote: > On 2022-02-16, Andrea Pappacoda wrote: >> But if what you are trying to solve is a reproducibility issue then >> CMAKE_BUILD_RPATH_USE_ORIGIN should be enough, and shouldn't even >> break existing workflows. > > That's been my experience so far, I've confirmed this with buidl testing > for many of the ~160 packages documented at: > > > https://tests.reproducible-builds.org/debian/issues/unstable/cmake_rpath_contains_build_path_issue.html
And now well over 360 packages! So far, I think I can count the number of packages on one hand which FTBFS with -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON, while -DCMAKE_SKIP_RPATH=ON seemed to have a few hundred, if I remember correctly. By my understanding in both cases, the actual RPATH is removed from the binary, so it only affects the Build ID... I'm not sure what the advantage of -DCMAKE_SKIP_RPATH=ON is, other than backwards compatibility with older versions of cmake? live well, vagrant
signature.asc
Description: PGP signature
