| To: | Peter Hartley <PDHartley@sonicblue.com> |
|---|---|
| Subject: | Re: Does e2fsprogs-1.26 work on mips? |
| From: | "H . J . Lu" <hjl@lucon.org> |
| Date: | Mon, 25 Mar 2002 09:07:17 -0800 |
| Cc: | Andrew Morton <akpm@zip.com.au>, tytso@thunk.org, linux-mips@oss.sgi.com, linux kernel <linux-kernel@vger.kernel.org>, GNU C Library <libc-alpha@sources.redhat.com> |
| In-reply-to: | <37D1208A1C9BD511855B00D0B772242C011C7F13@corpmail1.sc.sonicblue.com>; from PDHartley@sonicblue.com on Mon, Mar 25, 2002 at 02:52:24AM -0800 |
| References: | <37D1208A1C9BD511855B00D0B772242C011C7F13@corpmail1.sc.sonicblue.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Mon, Mar 25, 2002 at 02:52:24AM -0800, Peter Hartley wrote:
> H J Lu wrote:
> > I look at the glibc code. It uses a constant RLIM_INFINITY for a given
> > arch. The user always passes (~0UL) to glibc on x86. glibc will check
> > if the kernel supports the new getrlimit at the run time. If it
> > doesn't, glibc will adjust the RLIM_INFINITY for setrlimit. I
> > don't see
> > how glibc 2.2.5 compiled under kernel 2.2 will fail under 2.4 due to
> > this unless glibc is misconfigureed or miscompiled.
>
> It's not a question of which kernel glibc is compiled under, it's a question
> of which version of the kernel headers (/usr/include/{linux,asm}) glibc is
> compiled against.
>
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.
H.J.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | EJTAG Debug Exceptions and LL/SC, Kevin D. Kissell |
|---|---|
| Next by Date: | Documentation, Gopakumar.C.E |
| Previous by Thread: | RE: Does e2fsprogs-1.26 work on mips?, Peter Hartley |
| Next by Thread: | RE: Does e2fsprogs-1.26 work on mips?, Peter Hartley |
| Indexes: | [Date] [Thread] [Top] [All Lists] |