This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Does e2fsprogs-1.26 work on mips?
- From: "H . J . Lu" <hjl at lucon dot org>
- To: Peter Hartley <PDHartley at sonicblue dot com>
- Cc: linux kernel <linux-kernel at vger dot kernel dot org>,GNU C Library <libc-alpha at sources dot redhat dot com>
- Date: Mon, 25 Mar 2002 11:11:17 -0800
- Subject: Re: Does e2fsprogs-1.26 work on mips?
- References: <37D1208A1C9BD511855B00D0B772242C011C7F15@corpmail1.sc.sonicblue.com>
On Mon, Mar 25, 2002 at 11:00:05AM -0800, Peter Hartley wrote:
> H J Lu wrote:
> > What are you talking about? It doesn't matter which kernel header
> > is used. glibc doesn't even use /usr/include/asm/resource.h nor
> > should any user space applications.
>
> It's not about /usr/include/asm/resource.h, it's about
> /usr/include/asm/unistd.h, where the syscall numbers are defined.
>
> This is presumably what the "#ifdef __NR_ugetrlimit" in
> sysdeps/unix/sysv/linux/i386/getrlimit.c is meant to be testing against --
> nothing in the glibc-2.2.5 distribution itself defines that symbol. Surely a
> Linux glibc doesn't compile without the target system's linux/* and asm/*
> headers?
>
> 2.4's /usr/include/asm/unistd.h defines __NR_ugetrlimit but 2.2's doesn't.
>
I see. I think glibc should either require 2.4 header files under
<asm/*.h> and <linux/*.h>, or define __NR_ugetrlimit if it is not
defined.
H.J.