When uninative runs on a go -native executable, we end up with a broken binary which always core dumps. A log of a manual/devshell run follows: build [/opt/poky/...ners/umoci]> ./umoci --version umoci version 0.4.7+dev~git758044fc26ad65eb900143e90d1e22c2d6e4484d build [/opt/poky/...ners/umoci]> patchelf-uninative --set-interpreter /opt/poky/build/tmp/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2 umoci build [/opt/poky/...ners/umoci]> ./umoci --version Segmentation fault (core dumped) This has been an issue for ~2 years with patchelf, as can be seen in these upstream bug reports: https://forum.snapcraft.io/t/patchelf-broke-my-binary/4928 https://github.com/NixOS/patchelf/issues/146 The workaround (for now) is to statically link the -native application to avoid the patchelf corruption.
Created attachment 4797 [details] executable before patchelf
Created attachment 4798 [details] executable after patchelf
Bulk move of 64 bugs to 4.3 M3 after a quick review. If a bug is actually fixed, please add a commit link and resolve it. -- Randy for YP bug team.
Moved to M4.
Bulk move to 5.0 M1. -- Randy
Upstream bugs still open, moving to M3.
Upstream bugs still open, moving to M4.
Wasn't this fixed by: https://git.openembedded.org/openembedded-core/commit/?id=f0499b58d1dd149300a349dde8f6664679df13e6 included in uninative since 4.1: https://git.openembedded.org/openembedded-core/commit/?id=1c5c8ff97ba0a7f9adc592d702b865b3d166a24b
No one has seen this in ages.