Created attachment 8716 [details] Readelf after package installation Hello, We're experiencing runtime issues with buildroot version 2020.02.8 when we make several builds in a row (development environment). When this issue is triggered, some binaries will not work at all after the second image generation (see below) After investigation, the modifications in patch 0003-Add-option-to-make-the-rpath-relative-under-a-specif.patch between BR 2019.02 and BR 2020.02 versions triggers this problem. (using the 0003 patch from BR2019.02.x in BR2020.02.8 will make the problem go away). Up to now, we only saw this issue with binaries located in /usr/local/bin, and are quite huge. We're still trying to find a way to reproduce this issue with public packages. e.g. with our internal chromium package : $ make chromium-reconfigure # Using the chromium binary at this stage is OK. $ make # Using the chromium binary here is still OK $ make From here the chromium binary does not work anymore, no error printed, but the executable exits without doing anything. I'll attach the result of the readelf -a command on the binary during those 3 steps.
Created attachment 8721 [details] readelf -a command result after 1st make (ie 1st image generation)
Created attachment 8726 [details] readelf -a command after 2nd make (i.e. 2nd image generation)
Thank you for your report. The issue tracker for the Buildroot project has been moved to the Gitlab.com issue tracker: https://gitlab.com/buildroot.org/buildroot/-/issues We are taking this opportunity to close old issues in this old tracker. If you believe your issue is still relevant, please open one in the new issue tracker. Thank you!