On Mon, 2020-04-20 at 13:56 +0000, chris.lapla...@agilent.com wrote: > > I suspect uninative assumes all binaries are for the main system > > architecture > > so its probably trying to change the interpreter to a 64 bit one > > which clearly > > won't work in this case. > > > > It would be a question of stopping it for these binaries somehow... > > Maybe a matter of doing something like UNINATIVE_LOADER_pn-my-tool = > "???"
If only life were that simple. > Where "???" would be the loader in a hypothetical i386 uninative. There is a non-hypothetical i386 loader, it already exists. Unfortunately the loader has to be downloaded and extracted in place before anything gets run so it all happens very early. Its done centrally with one uninative, not two or per recipe. I think you might be able to do something like: SSTATEPOSTUNPACKFUNCS_remove_pn-mytool = "uninative_changeinterp" and it may at least stop breaking it... Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137326): https://lists.openembedded.org/g/openembedded-core/message/137326 Mute This Topic: https://lists.openembedded.org/mt/73137039/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
