CygWin and LIMITS.H

[Stephan.Wilms at CWA.de (Stephan Wilms)]

Hi,

I did some research concerning CygWin and "limits.h". There seems to be a 
conceptual problem. The "bit" script for Unix (pre)copies a "limits.h" 
file into the "${targte}/sys-include" directory (in 
"preinstall_header_files()"), where the Makefile for EGCS finds it and 
properly processes it.

Problem: The process for building the RTEMS tools with CygWin does
         not use the bit script and therefore aparently does
         *NOT* (pre)copy "limits.h". The directory
         "${targte}/sys-include" is never created (AFAICS).

The result is that the EGCS which I create on CygWin (on WinNT 4) does 
not have the correct "limits.h" file. My target type is "i386-rtemself". 
After completing the "make cross" and "make -k install", the  cross 
compiler finds "limits.h" at:
   \i386-rtemself\lib\gcc-lib\i386-rtemself\egcs-2.91.57\include\limits.h
and this file does *not* include the special POSIX extensions or macros 
like "NAME_MAX" (from NEWLIB). Not directly and not indirectly. Nor does 
the "configure" or "make" process indicate in any way how this should be 
achieved (and I did link in NEWLIB this time!).

SUMMARY: The Makefile for EGCS looks at "${tooldir}/sys-include" for any
         preinstalled header files (especially limits.h), but this
         is (AFAICS) only created in the "bit" script by
         "preinstall_header_files()".
         The instructions for CygWin do not create "sys-include" nor do
         they pay special attention to "limits.h", which leaves me with
         the wrong "limits.h" file.

Do I make some stupid mistake or did I miss some important step in the 
process of building the tools for CygWin ?

Stephan




--
Stephan Wilms (stephan.wilms at cwa.de) 
CWA-GmbH, Aachen, Germany