Compilation of syscall.c fails on ARM device

Khem Raj raj.khem at
Sun Sep 6 08:08:14 UTC 2009

On Wed, Aug 19, 2009 at 12:22 PM, Mike Frysinger<vapier at> wrote:
> On Wednesday 19 August 2009 15:02:18 Khem Raj wrote:
>> On Tue, Aug 18, 2009 at 4:23 PM, Mike Frysinger<vapier at> wrote:
>> > On Tuesday 18 August 2009 18:42:36 Khem Raj wrote:
>> >> If we need to revive OABI then we might have to find a way to make it
>> >> work, right now mostly people use EABI and there it should work ok.
>> >
>> > working OABI is still a requirement
>> That would mean that arm will have to have exception to this common
>> syscall stuff that you added.
> i dont see why it would, but i dont know arm asm.  the common syscall stuff is
> designed for ports to completely override the common defines without any
> hacks.

OK I have reverted the patch.

>> What stage do we plan to stop supporting OABI for new releases.
> can EABI be used on all arm parts ?  currently, i would say there are no plans
> to stop supporting it seeing as how linux-2.4 requires OABI, and the OABI
> compat layer in the kernel is always broken (i.e. completely useless).

Well I can think of say 0.9.31 is last OABI supported release but then
we have to maintain 0.9.31.x
releases until 2.4 kernel is maintained. So I guess keeping it alive
on trunk could be less headache

> -mike

More information about the uClibc mailing list