From: Daniel Jacobowitz <dan@debian.org>
To: Carsten Langgaard <carstenl@mips.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>, "H. J. Lu" <hjl@lucon.org>,
linux-mips@oss.sgi.com
Subject: Re: Personality
Date: Tue, 16 Jul 2002 09:40:14 -0400 [thread overview]
Message-ID: <20020716134014.GA19350@nevyn.them.org> (raw)
In-Reply-To: <3D33DAB2.353A4399@mips.com>
On Tue, Jul 16, 2002 at 10:34:58AM +0200, Carsten Langgaard wrote:
> The include/linux/personality.h file has changed between the 2.4.3 and
> the 2.4.18 kernel.
> Now there is a define of personality (#define personality(pers) (pers &
> PER_MASK), but that breaks things for the users, if they include this
> file.
> The user wishes to call the glibc personality function (which do the
> syscall), and not use the above definition.
>
> So I guess we need a "#ifdef __KERNEL__" around some of the code in
> include/linux/personality.h (at least around the define of personality),
> which then has to go into the glibc kernel header files.
>
> Any comments ?
Why is the user program including <linux/personality.h> in the first
place?
The right thing to do here is to provide the necessary bits in a glibc
header, probably in bits/personality.h or so.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-07-16 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 8:34 Personality Carsten Langgaard
2002-07-16 10:36 ` Personality Ralf Baechle
[not found] ` <20020716090728.A22128@lucon.org>
2002-07-16 19:16 ` PATCH: Add sys/personality (Re: Personality) Carsten Langgaard
2002-07-17 2:08 ` H. J. Lu
2002-07-17 7:14 ` Carsten Langgaard
2002-07-16 13:40 ` Daniel Jacobowitz [this message]
2002-07-16 13:57 ` Personality Carsten Langgaard
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=20020716134014.GA19350@nevyn.them.org \
--to=dan@debian.org \
--cc=carstenl@mips.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.