From: Jocelyn Mayer <jocelyn.mayer@netgem.com>
To: linux-kernel@vger.kernel.org
Subject: Fix for include/linux/fs.h in 2.4.0 kernels
Date: Sat, 03 Feb 2001 00:04:16 +0100 [thread overview]
Message-ID: <3A7B3CF0.50327D75@netgem.com> (raw)
I had some problems while compiling some applications
with the 2.4.0 kernel.
The problem was a conflict between string.h from the libc
and the one from the kernel, which is included in fs.h
So, using <string.h> and <linux/fs.h> at the same time
brings some conflicts.
It seems to me that <linux/string.h> should not be apparent
from user mode, so I did this patch:
--- fs.h-orig Fri Feb 2 23:55:35
2001
+++ fs.h Fri Feb 2 21:26:05
2001
@@ -20,7 +20,7
@@
#include
<linux/stat.h>
#include
<linux/cache.h>
#include
<linux/stddef.h>
-#include
<linux/string.h>
+/* #include <linux/string.h>
*/
#include
<asm/atomic.h>
#include
<asm/bitops.h>
@@ -190,6 +190,7
@@
#include
<asm/semaphore.h>
#include
<asm/byteorder.h>
+#include
<linux/string.h>
extern void update_atime (struct inode
*);
#define UPDATE_ATIME(inode) update_atime
(inode)
Like this, the #include <linux/string.h> is "protected"
by a #ifdef __KERNEL__, so I don't have any conflict any more.
I recompiled my kernel without any problem since I did that patch.
Regards.
Jocelyn Mayer.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-02 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 23:04 Jocelyn Mayer [this message]
2001-02-02 23:25 ` Fix for include/linux/fs.h in 2.4.0 kernels Keith Owens
2001-02-03 7:42 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-02-03 2:49 Frédéric L. W. Meunier
2001-02-03 3:03 ` Brian May
2001-02-03 3:10 ` Keith Owens
2001-02-03 4:21 ` Brian May
2001-02-03 4:39 ` Brian Wellington
2001-02-03 4:41 ` Brian May
2001-02-03 8:48 ` Graham Murray
2001-02-03 8:59 ` Keith Owens
2001-02-03 10:09 ` Graham Murray
2001-02-03 11:38 ` Keith Owens
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=3A7B3CF0.50327D75@netgem.com \
--to=jocelyn.mayer@netgem.com \
--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 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.