On Mon, 2020-04-20 at 15:15 +0000, chris.lapla...@agilent.com wrote: > > 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... > > What if we taught uninative how to identify whether it is appropriate > to change the loader for the executable? If not, it could (maybe > configurably) avoid doing so and/or give a warning.
These are all options, I'm mainly worried about significantly complicating an already fragile piece of code. It was implemented as a proof of concept with a plan to go back and put proper hooks into bitbake to drive it. It worked well enough that nobody has gone back and done that work. I worry about performance implications too... Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137329): https://lists.openembedded.org/g/openembedded-core/message/137329 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] -=-=-=-=-=-=-=-=-=-=-=-
