Message ID | 20120502153933.GD547@mudshark.cambridge.arm.com |
---|---|
State | New |
Headers | show |
On 05/02/2012 11:39 AM, Will Deacon wrote: > On Wed, May 02, 2012 at 03:48:10PM +0100, Eric Paris wrote: >> I'm fine with not supporting things. But I'm pretty stupid here. Is >> this just not supporting some old chip? Or is this some ABI that a new >> chip could have both and can switch at run time? If the latter, we need >> to support it. If the former, and hints on how to make sure you can't >> build audit with OABI? > > My current hack in the kernel is to change the Kconfig entries for audit. As > for userspace, I guess you have to check the toolchain triplet somehow. v6 > onwards makes use only of EABI and it's becoming increasingly more difficult > to find distributions supporting OABI (required for CPUs prior to v4t). I'll followup with an email explaining ARM ABIs to help out - might take me a bit of time to get to it. Jon.
Index: lib/libaudit.c =================================================================== --- lib/libaudit.c (revision 693) +++ lib/libaudit.c (working copy) @@ -1327,6 +1327,10 @@ if (bits == __AUDIT_ARCH_64BIT) return -6; break; + case MACH_ARMEB: + if (bits == __AUDIT_ARCH_64BIT) + return -6; + break; case MACH_86_64: /* fallthrough */ case MACH_PPC64: /* fallthrough */ case MACH_S390X: /* fallthrough */