CMake/CTest shared library requirements difference cmake.org and apt.kitware.com
Comparing the shared libraries required by the CMake/CTest binaries shipped in context of the tar package on the download page, for example https://github.com/Kitware/CMake/releases/download/v3.20.1/cmake-3.20.1-linux-x86_64.tar.gz, and the ones required by the CMake 3.20.1 debian package installed from https://apt.kitware.com repository. It seems there is a clear difference noticeable in their shared library requirements, which I would like to better understand why this is the case? Specially if you would for example execute ctest
in context of for example a Conan recipe with a LD_LIBRARY_PATH
declared containing paths to a different set of libcrypto.so/libssl.so libraries than you could be confronted with relocation errors.
Observed differences:
tar.gz
linux-vdso.so.1 (0x00007fff1bab9000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f62494a3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f6249284000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6249080000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6248ce2000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f62488f1000)
/lib64/ld-linux-x86-64.so.2 (0x00007f62496ab000)
debian package:
linux-vdso.so.1 (0x00007ffd201f9000)
libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007ff5d7c1d000)
libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007ff5d77d9000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff5d75d5000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007ff5d73cd000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff5d71ae000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007ff5d6e25000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff5d6a87000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ff5d686f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff5d647e000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff5d7e85000)
NOTE: when trying to execute locally bootstrap, followed by make and cpack -G TGZ
the resulting tar.gz doesn't seem to match in terms of shared requirements with the one mentioned above. Not sure if you should be specifying any particular flags to the bootstrap process to achieve the same result.