Patch for limits.h and RTEMS
Jeffrey A Law
law@upchuck.cygnus.com
Wed Mar 31 00:51:00 GMT 1999
In message < 19990329163940.7423.qmail@comton.airs.com >you write:
> gcc can build two different versions of limits.h. If there is a
> system limits.h, it builds a limits.h which includes the system one
> and then ensures that certain values are set correctly.
>
> gcc checks whether there is a system limits.h by looking in a specific
> directory, normally /usr/include. When building a cross compiler, it
> looks in $(tooldir)/sys-include; the user is expected to preinstall
> the appropriate header files in that directory.
>
> This works fine, except for a couple of environments which are
> normally build in conjunction with gcc. For these environments,
> limits.h does exist, but it is not yet installed in
> $(tooldir)/sys-include; it lives in a directory parallel to the gcc
> source directory.
>
> The two environments I know of which have this problem are cygwin and
> RTEMS. For cygwin, I fixed the problem over a year ago:
>
> Wed Jan 28 20:04:43 1998 Ian Lance Taylor <ian@cygnus.com>
>
> * i386/t-cygwin32 (LIMITS_H_TEST, LIBGCC2_INCLUDES): Define.
>
> Here is the appropriate patch for RTEMS. Since gcc includes some
> RTEMS configuration information, it should include this as well.
>
> Ian
>
>
> Mon Mar 29 11:37:49 1999 Ian Lance Taylor <ian@zembu.com>
>
> * t-rtems (LIMITS_H_TEST, LIBGCC2_INCLUDES): Define.
Ironic -- Joel and I were just discussing this recently. I suggested we
copy whatever cygwin was doing :-) :-)
Thanks, I've installed this patch.
Joel -- can you give it a spin and see if it works for you?
jeff
More information about the Gcc-patches
mailing list