Hi Helmut, Helmut Grohne wrote:
> On IRC Steve Langasek pointed out that some part of the difference > resides in the architecture-kernel part. You cannot run a x32 binary on > an arbitrary x86_64 linux kernel Yes, that's true. The kernel needs CONFIG_X86_X32_ABI set. There are all sorts of other dependencies on kernel configuration that an application can have (e.g., requiring a kernel new enough to support the accept4 syscall, or requiring an SMP kernel) that are not reflected in the triplet at all because they do not affect interoperability (i.e., what code can share a process image), so this seems kosher enough. [...] > I therefore suggest sticking with the > x86_64-linux-gnux32 used by yocto. I'm not aware of anything that pays attention to the OS part without the ABI part of GNU triplets in a way that this would break. So it sounds sensible to me. VDSO support means the kernel knows the calling convention on x86 anyway. Thanks for your attention to detail. Jonathan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
