From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] C++ doesn't like asm/atomic.h
Date: Mon, 08 Apr 2002 22:59:50 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905418@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905396@msgid-missing>
On Mon, 8 Apr 2002 12:33:40 -0700,
Gary Hade <garyhade@us.ibm.com> wrote:
>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.
Old man pages (1996). They date from the time that the kernel and
glibc shared the kernel headers via a symlink. Linus has changed his
mind since then but the modutils man pages were never updated.
modutils provides include/module.h as part of the source package. That
file is not installated anywhere, nobody outside modutils has required
it. If you want to invoke the modutils syscalls yourself, take a copy
of include/module.h from modutils into your source tree. But don't be
surprised if the interface changes under you. modutils will know about
any interface changes, other packages will have to cope with the
version skew themselves.
next prev parent reply other threads:[~2002-04-08 22:59 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
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 [this message]
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-105590701905418@msgid-missing \
--to=kaos@ocs.com.au \
--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