From: Konstantin Volckov <goldhead@altlinux.ru>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: Sat, 16 Jun 2001 16:47:03 +0400 [thread overview]
raw)
[-- Attachment #1: Type: text/plain, Size: 273 bytes --]
Hi!
There're a problem in <linux/capatibility.h>. In this file included
<linux/fs.h>, but this include is'nt ifdef'ed with __KERNEL__ and (for
example) samba can't be compiled with kernel 2.4 headers. Here is the
patch, that solve this problem.
--
Good luck,
Konstantin
[-- Attachment #2: linux-2.4.5-ac15-lcap.patch --]
[-- Type: application/octet-stream, Size: 481 bytes --]
--- linux/include/linux/capability.h_old Thu Jun 14 13:19:08 2001
+++ linux/include/linux/capability.h Thu Jun 14 20:46:07 2001
@@ -14,7 +14,6 @@
#define _LINUX_CAPABILITY_H
#include <linux/types.h>
-#include <linux/fs.h>
/* User-level do most of the mapping between kernel and user
capabilities based on the version tag given by the kernel. The
@@ -278,6 +277,7 @@
#define CAP_LEASE 28
#ifdef __KERNEL__
+#include <linux/fs.h>
/*
* Bounding set
*/
reply other threads:[~2001-06-16 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010616164703.22d0a90f.goldhead@altlinux.ru \
--to=goldhead@altlinux.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).