This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc's limits.h vs POSIX
- From: Ian Lance Taylor <ian at wasabisystems dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: 21 Jan 2004 20:26:43 -0500
- Subject: Re: gcc's limits.h vs POSIX
- References: <200401220116.i0M1G5Ps019902@greed.delorie.com>
DJ Delorie <dj@redhat.com> writes:
> POSIX defines a list of macros that are to be found in <limits.h> (for
> example, PATH_MAX).
>
> The <limits.h> that gcc generates does not include these.
>
> DJGPP's <limits.h>, for example, does.
>
> How does one get the system's <limits.h> ?
If there is a system limits.h, then the limits.h which gcc installs
should have the line
#include "syslimits.h"
That file should either be the fixed version of <limits.h> installed
by fixincludes, or, if <limits.h> does not need to be fixed, it should
have the line
#include_next <limits.h>
See the xlimits.h and stmp-int-hdrs targets in gcc/Makefile.in.
Perhaps config/i386/t-djgpp needs to define LIMITS_H_TEST.
Ian