On Wed, 2025-01-29 at 16:58 +0000, Ross Burton via lists.openembedded.org wrote: > On 21 Jan 2025, at 08:55, hongxu via lists.openembedded.org > <[email protected]> wrote: > > The nativesdk multilib support required it to fix multilib headers > > conflict > > So the context here is that luajit apparently needs to be able to > build native code with the same word size as the target. But this > demonstrates nicely that nobody has tried to build a 32-bit luajit on > a 64-bit non-x86 machine, for example: > > > gcc: error: unrecognized command-line option ‘-m32’ > > So if the goal is “build luajit everywhere” then this doesn’t solve > that problem.
I've been giving this a lot of. Part of me does like this solution but equally, it is complicating something which is already quite complex for a comparatively isolated problem. As Ross mentions, it only fixes this for a small subsection there too, it isn't a universal fix. Some of the patches in the series are simple/trivial but others have what looks like quite fragile logic (e.g. the libgcc paths). I'm not convinced merging this and trying to support multilib nativesdk-gcc is in our best interests unfortunately. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#210907): https://lists.openembedded.org/g/openembedded-core/message/210907 Mute This Topic: https://lists.openembedded.org/mt/110730419/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
