Re: limits.h

[Eric G.Miller <egm2@jps.net>]

On Thu, 24 Jan 2002 19:39:39 +0300 (MSK), "Alexey" <lu@nikaa.dnttm.ru> wrote:

> While trying to compile something I get the error message:
> 
> *******************************************************************
> 
> In file included from /usr/include/bits/socket.h:31,
>                  from /usr/include/netinet/in.h:212,
>                  from /usr/include/netdb.h:28,
>                  from pam_access.c:48:
> /usr/include/limits.h:124: No include path in which to find limits.h
> make[2]: *** [dynamic/pam_access.o] Error 1
> make[1]: *** [all] Error 1
> make: *** [modules] Error 2
> 
> *******************************************************************
> 
> Of course, it's not a PAM source bug, because I get the same message
> during the other compilation processes. The 124th line of limits.h is:
> 
> *******************************************************************
> 
> 123: #if defined __GNUC__ && !defined _GCC_LIMITS_H_
> 124: #include_next <limits.h>
> 
> *******************************************************************
> 
> I guess, some of header files were damaged, or removed, or anything else...
> Does anybody know, how to fix it? How does "#include_next" work?

I suspect it's a GCC'ism.  Is your GCC installation fubar'ed?  The limits.h
referred to, should live with gcc at 
/usr/lib/gcc-lib/<arch>/<version>/include/limits.h  There are few important
includes that are in there. "float.h" is another.

-- 
Eric G. Miller <egm2@jps.net>