[klibc] Unsupported system calls

H. Peter Anvin hpa at zytor.com
Wed Oct 16 01:02:18 PDT 2013

On 10/16/2013 12:52 AM, Anil Singhar wrote:
> Hi HPA,
> Thanks for your reply. One confusion I have is:
> e.g. 'access' is not supported in aarch64, so should the declaration be:
> <!aarch64> int access(const char *, int);  <-- This is how it is currently
> indicating that only aarch64 doesn't support it.
> OR
> <?> int access(const char *, int); <-- if I do this instead, it will be
> optional for every architecture, right..?

Yes, and that is the right way to do it if there is a generic,
non-architecture specific fallback in terms of another system call.


More information about the klibc mailing list