This is the mail archive of the
glibc-linux@ricardo.ecn.wfu.edu
mailing list for the glibc project.
Re: Stubs and what they can do
- From: Andreas Jaeger <aj at suse dot de>
- To: george anzinger <george at mvista dot com>
- Cc: "glibc-linux at ricardo dot ecn dot wfu dot edu" <glibc-linux at ricardo dot ecn dot wfu dot edu>
- Date: Sun, 17 Feb 2002 22:11:38 +0100
- Subject: Re: Stubs and what they can do
- References: <3C700846.357D36E7@mvista.com>
- Reply-to: glibc-linux at ricardo dot ecn dot wfu dot edu
george anzinger <george@mvista.com> writes:
> Hi,
>
> I am looking thru the glibc code and trying to understand how to do
> this:
>
> I have a set of new system calls that are currently handled by functions
> in glibc (the POSIX timers calls, i.e. timer_xxx and clock_xxx). These
> calls will be available on a particular linux platform as the patch is
> accepted by the various controlling groups. I would like to modify
> glibc so that it, by checking unistd.h in the kernel tree for the
> existence of the given system call, will build either the system call
> stub or the existing library routine.
>
> Is this sort of thing already in place? If not, how might it be added?
Since ages, check e.g. sysdeps/unix/sysv/linux/i386/lchown.c
> Should it be done at ./configure time or at make time?
>
> Comments?
Please ask on libc-alpha@sources.redhat.com next time,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj