| To: | Alan Cox <alan@lxorguk.ukuu.org.uk> |
|---|---|
| Subject: | Re: errno assignment in _syscall macros and glibc |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Sun, 25 Jun 2000 23:21:39 +0200 |
| Cc: | Andreas Jaeger <aj@suse.de>, Mike Klar <mfklar@ponymail.com>, linux-mips@oss.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu |
| In-reply-to: | <E136I3I-0002yR-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Jun 25, 2000 at 08:26:42PM +0100 |
| References: | <20000625204334.E1572@bacchus.dhis.org> <E136I3I-0002yR-00@the-village.bc.nu> |
On Sun, Jun 25, 2000 at 08:26:42PM +0100, Alan Cox wrote: > > Andreas - I think the syscall interface should finally officially be > > declared a private interface between libc and the kernel, that is nobody > > except these two should use it. Many of the other attempts to use it > > have been quite problematic - portabilitywise and worse. > > Don't make it too private. glibc is still worryingly large for some embedded > applications. Between a libc and the kernel yes, between glibc and the kernel > no. Sure; these days glibc is more or less synonym with libc and I was using it in that sense. What small, portable libcs do we have available anyway? Some mipers will want one. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: errno assignment in _syscall macros and glibc, Alan Cox |
|---|---|
| Next by Date: | Re: errno assignment in _syscall macros and glibc, Alan Cox |
| Previous by Thread: | Re: errno assignment in _syscall macros and glibc, Alan Cox |
| Next by Thread: | Re: errno assignment in _syscall macros and glibc, Alan Cox |
| Indexes: | [Date] [Thread] [Top] [All Lists] |