[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: more header problems - 2.2.2 vs. linux 2.4.1
From: |
Andreas Jaeger |
Subject: |
Re: more header problems - 2.2.2 vs. linux 2.4.1 |
Date: |
20 Feb 2001 06:59:25 +0100 |
User-agent: |
Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.1 (Channel Islands) |
Lynn Winebarger <address@hidden> writes:
> It appears there are conflicts between <string.h> and
> <linux/string.h>
Never include kernel space headers in a user program.
> Why are both of these being included? These confilcts
> have occured in compiling timed, sash, and hdparm (3.9).
> They're including <linux/fs.h> which then includes <linux/string.h>.
That's a bug in hdparm.
> Also, there are conflicts between sys/mount.h and linux/fs.h
>
> Does anyone know how to resolve these conflicts? I don't know if there's
> any special reason why the kernel string implementations should be used
> in general headers.
Don't include those kernel headers - for details read the glibc FAQ.
Andreas
--
Andreas Jaeger
SuSE Labs address@hidden
private address@hidden
http://www.suse.de/~aj