🚀 go-pugleaf

The gcc generated limits.h file should do an #include_next <limits.h>
if it has been already included once.

This situation occurs when you are trying to compile gcc-2.3.1 with
an already installed version of gcc-2.3.1. During the compile of 
protoize.c you have the include path set to :

  -I/gnu/src/gcc-2.3.1 -I/gnu/src/gcc-2.3.1/config

so a #include <limits.h> will do the following:

  - include /usr/local/lib/gcc-lib/i386-aix/2.3.1/include/limits.h
    - include /gnu/src/gcc-2.3.1/syslimits.h
      - include /usr/local/lib/gcc-lib/i386-aix/2.3.1/include/limits.h
        This will stop here instead of including /usr/include/limits.h

This problem happen only under aix ps/2 where some system headers expect
values to be defined in the system /usr/include/limits.h.

Here is a possible fix to the file limity.h.

Minh Tran-Le.
---------------------------------------------------------------------------
*** limity.h-	Sat Aug  1 19:53:10 1992
--- limity.h	Sun Nov  1 11:12:25 1992
***************
*** 1,4 ****
  /* This administrivia gets added to the end of limits.h
     if the system has its own version of limits.h.  */
  
! #endif /* not _LIMITS_H_ */
--- 1,6 ----
  /* This administrivia gets added to the end of limits.h
     if the system has its own version of limits.h.  */
  
! #else /* not _LIMITS_H_ */
! #include_next <limits.h>
! #endif
-------