klibc - Oct 2013 - Mailing list fixed

It seems the mailing list has been broken for several days.  It should
now be temporarily fixed, but because the fix is temporary I can't
promise it won't happen again until the permanent fix is available.

Sorry for that.

	-hpa

Hi HPA,

Regarding the architecture un-supported system calls, I wrapped them with
#ifndef __NR_<foo> .. #endif /* __NR_<foo> */ switches. I have
already done
that. But you also mentioned that in SYSCALLS.def all these calls should be
present and marked with '?'.. Is that right..? Could you please give
little
more detail about the change you want.

Thanks and Regards,
Anil


On 15 October 2013 23:25, H. Peter Anvin <hpa at zytor.com> wrote:
> It seems the mailing list has been broken for several days.  It should
> now be temporarily fixed, but because the fix is temporary I can't
> promise it won't happen again until the permanent fix is available.
>
> Sorry for that.
>
>         -hpa
> _______________________________________________
> klibc mailing list
> klibc at zytor.com
> http://www.zytor.com/mailman/listinfo/klibc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.zytor.com/pipermail/klibc/attachments/20131016/291e6e49/attachment.html>

On 10/16/2013 12:42 AM, Anil Singhar wrote:
> Hi HPA,
> 
> Regarding the architecture un-supported system calls, I wrapped them with
> #ifndef __NR_<foo> .. #endif /* __NR_<foo> */ switches. I have
already done
> that. But you also mentioned that in SYSCALLS.def all these calls should be
> present and marked with '?'.. Is that right..? Could you please
give little
> more detail about the change you want.
> 
It's very simple: if the system call has <?> before it, it will simply
be omitted if it isn't present on a specific architecture.  If it
*doesn't* have <?> in front of it, then it is an error for it to not
exist.

	-hpa