On Thu, 10 Oct 2019, Eric Noulard wrote: ... > with patchelf is works with an intriguing warning: > warning: working around a Linux kernel bug by creating a hole of 2093056 > bytes in ‘/path/to/executable’ > > which seems to be a resolved issue: > https://github.com/NixOS/patchelf/issues/92 > > after that on the modified executable, > chrpath is printing weird output when asking to read rpath. > patchelf does properly print modified rpath. > > I think the SO article gives enough reference for this: > https://stackoverflow.com/questions/13769141/can-i-change-rpath-in-an-already-compiled-binary > > So I was wrong, thank you for your honest question Jakub. > I learned something usefull thanks to you. ...
Thanks both! Great news - being unable to grow rpath was always really irritating. Mark -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
