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
Buildhost Hard coded library paths are being included in binaries and libraries (guessing -rpath in some binaries)
To Reproduce
Steps to reproduce the behavior:
Do a make image
boot the image
Run the following in the bin and lib directories find /usr/lib /usr/bin -type f -exec ldd -v {} \; 2>&1 | grep -v -e "not a dynamic executable" -e "you do not have execution permission for" | grep -e storage -e "\t/" > /tmp/ld-errors
This was discovered by accident when I rebooted my system (which is the buildhost) with glib2.32 in the build...-Generic directory after doing a test build of HEAD. My dev tree (thus my runtime glibc is normally 2.33) - systemd refused to complete and GLIB_2.33 errors were on the console. A reboot using a recovery image and doing make glibc In the docker container got every thing going again, and set me down the path of checking the hardcoded paths in the /usr/lib and /usr/bin
I believe it only impacts when the build host directories match the runtime environment and the libraries are older in the build host directories.
The text was updated successfully, but these errors were encountered:
Describe the bug
Buildhost Hard coded library paths are being included in binaries and libraries (guessing -rpath in some binaries)
To Reproduce
Steps to reproduce the behavior:
make image
find /usr/lib /usr/bin -type f -exec ldd -v {} \; 2>&1 | grep -v -e "not a dynamic executable" -e "you do not have execution permission for" | grep -e storage -e "\t/" > /tmp/ld-errors
Informations
Log file
Additional context
This was discovered by accident when I rebooted my system (which is the buildhost) with glib2.32 in the build...-Generic directory after doing a test build of HEAD. My dev tree (thus my runtime glibc is normally 2.33) - systemd refused to complete and GLIB_2.33 errors were on the console. A reboot using a recovery image and doing
make glibc
In the docker container got every thing going again, and set me down the path of checking the hardcoded paths in the /usr/lib and /usr/binI believe it only impacts when the build host directories match the runtime environment and the libraries are older in the build host directories.
The text was updated successfully, but these errors were encountered: