From: Gary Hade <garyhade@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] C++ doesn't like asm/atomic.h
Date: Mon, 08 Apr 2002 19:33:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905416@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905396@msgid-missing>
On Mon, Apr 08, 2002 at 01:13:29PM -0700, David Mosberger wrote:
> >>>>> On 08 Apr 2002 12:23:14 -0700, Ulrich Drepper <drepper@redhat.com> said:
>
> Uli> On Mon, 2002-04-08 at 12:00, David Mosberger wrote:
> >> So you're OK with glibc providing the syscall stubs for
> >> module*(), but not the header files required to use them?
>
> Uli> Yes. There is no fundamental problems with this.
>
> I guess I don't really see the harm in having glibc provide a header
> for these system call, but as long as the syscall stubs are there,
> it's probably not a huge issue in practice.
David, did you mean to say "... in having glibc not provide ..."?
^^^
I notice that the *_module(2) man pages which advocate the use of
#include <linux/module.h> are installed as part of the modutils
package. Is is possibly "modutils" that should provide the header
file that avoids sucking in the possibly problematic kernel-only
code.
Gary
next prev parent reply other threads:[~2002-04-08 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 21:40 [Linux-ia64] C++ doesn't like asm/atomic.h Gary Hade
2002-04-05 21:54 ` David Mosberger
2002-04-08 16:00 ` Gary Hade
2002-04-08 17:26 ` David Mosberger
2002-04-08 17:51 ` Ulrich Drepper
2002-04-08 19:00 ` David Mosberger
2002-04-08 19:23 ` Ulrich Drepper
2002-04-08 19:33 ` Gary Hade [this message]
2002-04-08 20:13 ` David Mosberger
2002-04-08 20:23 ` Ulrich Drepper
2002-04-08 20:40 ` David Mosberger
2002-04-08 22:59 ` Keith Owens
2002-04-08 23:27 ` Gary Hade
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=marc-linux-ia64-105590701905416@msgid-missing \
--to=garyhade@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
/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