From: Florian Lohoff <flo@rfc822.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: resources.h patch / RLIM_INFINITY __KERNEL__ depend ?
Date: Fri, 31 Mar 2000 10:29:52 +0200 [thread overview]
Message-ID: <20000331102952.B273@paradigm.rfc822.org> (raw)
In-Reply-To: <20000330184715.A1600@uni-koblenz.de>; from Ralf Baechle on Thu, Mar 30, 2000 at 06:47:15PM +0200
On Thu, Mar 30, 2000 at 06:47:15PM +0200, Ralf Baechle wrote:
> On Thu, Mar 30, 2000 at 02:27:05PM +0200, Florian Lohoff wrote:
>
> > again - short patch - RLIM_INFINITY - This is also defined in
> > both glibc 2.0 and glibc 2.1 headers so it should be __KERNEL__
> > dependend - Shouldnt it ?
>
> Glibc 2.1 doesn't include <asm/resource.h>, and 2.0 shouldn't do as well
> as per convention. So the fix is to copy the necessary definitions from
> kernel headers into glibc headers.
>
> Thanks for reporting this. I'm just cooking a new glibc release ...
My glibc does include asm/resource.h - This is default hardhat (little endian)
resourcebits.h:#include <asm/resource.h>
This is what caused a lot of userspace builts to fail.
Flo
--
Florian Lohoff flo@rfc822.org +49-5241-470566
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."
next prev parent reply other threads:[~2000-03-31 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-30 12:27 resources.h patch / RLIM_INFINITY __KERNEL__ depend ? Florian Lohoff
2000-03-30 16:47 ` Ralf Baechle
2000-03-31 8:29 ` Florian Lohoff [this message]
2000-03-31 11:46 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000331102952.B273@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox