This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: where is the system call code
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Sasha Sirotkin <demiurg at femtolinux dot com>
- Cc: Amerigo Wang <xiyou dot wangcong at gmail dot com>, libc-help at sourceware dot org
- Date: Sat, 1 May 2010 15:54:49 -0400
- Subject: Re: where is the system call code
- References: <j2t478c82f01004291133m920d2342kc91d060f8c4be837@mail.gmail.com> <20100430023403.GA3989@cr0.nay.redhat.com> <u2h478c82f01005010408q4dd807dclc349ecc59f1845f@mail.gmail.com>
On Sat, May 1, 2010 at 7:08 AM, Sasha Sirotkin > I should have
probably found it myself, but I think that after I spent
> a few hours digging through the code it is OK to ask this on the
> mailing list - how can one add an architecture-specfic system call C
> implementation, for instance something like
> ports/sysdeps/unix/sysv/linux/mips/mips64/recv.c for ARM ?
The build system searches for SYSCALL.c and SYSCALL.S files before
processing the results of the syscalls.list.
IIRC you only need to provide a SYSCALL.[cS] file in any ARM system
dependency directory to override the default. Where SYSCALL is the
syscall name. The new file will be used instead of the default
automatically generated version. This is all part of the automatic
scanning the build system does.
Please feel free to ask any questions on libc-help. The purpose of
this list is to mentor new C library developers :-)
Cheers,
Carlos.