From c076a2bde406e617ebfeda6b921d1db89eb1a9f6 Mon Sep 17 00:00:00 2001 From: "arnd@arndb.de" Date: Tue, 2 Dec 2003 00:26:46 -0800 Subject: [PATCH] [PATCH] Build failure - missing linux/limits.h include? MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit On Tuesday 25 November 2003 00:12, Chris Larson wrote: > udev fails to compile here unless I'm doing a KLIBC build.  The reason > appears to be that the normal limits.h in the gcc inc dir doesn't pull > in linux/limits.h, whereas the limits.h out in the klibc include dirs > does.  I'd think it'd be best to add a #include to > udev.h directly, since it uses PATH_MAX. No, don't include kernel headers directly if you can avoid it. The problem you are referring to seems to be with old tool chains, I have the same symptom with my s390 gcc-2.95/glibc-2.1.3. Including instead of seems to fix it. --- udev.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/udev.h b/udev.h index 89943074..0c1951ad 100644 --- a/udev.h +++ b/udev.h @@ -24,7 +24,7 @@ #define UDEV_H #include "libsysfs/libsysfs.h" -#include +#include #ifdef DEBUG #include -- 2.39.5