On Friday 04 March 2005 17:29, Eljay Love-Jensen wrote:
> >syslimits.h doesn't start and complete: it does...
>
> You did not include the complete inclusion tree in your first
> posting, so I had to make an assumption based on your incomplete
> example.
>
> Try using the -H parameter.
Thank you for suggestion. Here it is (I added the directive used to
include each file):
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/include
/usr/include
End of search list.
. /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/include/limits.h
#include "syslimits.h"
.. /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/include/syslimits.h
#include_next <limits.h>
... /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/include/limits.h
#include_next <limits.h>
.... /usr/include/limits.h
/* snip the rest */
The question is why the #include_next directive in syslimits.h results
in including <gcc-include-dir>/limits.h, not in including limits.h
from the next directory in the search list.
Regards,
Alexey.
--
May your roots always be well watered!
-- Supox, SC2
