On Tue, 2021-11-30 at 23:37 +0100, Jacob Kroon wrote: > Try to make sure that the RUNTIME dynamic entry size is the same for all > binaries produced with the native compiler. This is necessary in order to > produce identical binaries when using differently sized buildpaths. I've > tried using only patchelf, and keeping the linker flags as they are, but > I am unable to produce identical binaries. Has anyone else managed to do > this with patchelf ? If not, maybe we can write a new tool that can handle it > ? > > The build-id also needs to be removed since it is calculated based on > the data present at link time. This includes STAGING_LIBDIR_NATIVE > and STAGING_BASE_LIBDIR_NATIVE. Both will differ and they need to be > temporarily > preserved since some recipes will execute the binaries during do_install() > (for example python3-native). Later on these are removed in chrpath.bbclass. > > This hack is the first step for producing identical native binaries when using > different build paths. 'zstd-native' is a working example. > > Signed-off-by: Jacob Kroon <[email protected]> > --- > meta/classes/chrpath.bbclass | 3 +++ > meta/conf/bitbake.conf | 5 ++++- > 2 files changed, 7 insertions(+), 1 deletion(-)
I'm a little torn on this. Our other option would be to hardcoded a specific dummy path and then edit it later to the correct value. That may be neater than adding the padding. It will change the end binaries but hopefully only after they're installed so should give the same net end result more neatly? If we separate out the build-id patch we could hopefully get that piece merged as that shouldn't be controversial? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#159067): https://lists.openembedded.org/g/openembedded-core/message/159067 Mute This Topic: https://lists.openembedded.org/mt/87415016/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
