> On 29 Sep 2022, at 16:31, Daniel McGregor <daniel.mcgre...@vecima.com> wrote: > > Sure, I'm actually talking about host binaries, built inside our equivalent > of a poky build appliance. The most obvious example is pseudo-native built on > our newest build servers. GCC decides to use instructions (in particular BMI2 > instructions) that don't exist on our older build machines. Since we use a > common shared state and uninative it was becoming pretty common for old > machines to pull shared state built on a much newer one, leading to build > failures do to invalid opcode exceptions.
Ah, so you build a container with Yocto and then do your Yocto builds inside that container. Got it, thanks. Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171193): https://lists.openembedded.org/g/openembedded-core/message/171193 Mute This Topic: https://lists.openembedded.org/mt/93983396/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
