On Sep 26, 2006, at 5:48 PM, Ian Lance Taylor wrote:
So I don't understand what the issue is. Can you give an example?
mrs $ cat subdirectory/limits.h
//
// bogus limits.h header should never be included
//
#error "including limits.h from the wrong place"
mrs $ gcc -iquotesubdirectory t.c
I
"Dave Korn" <[EMAIL PROTECTED]> writes:
> Here's one: it doesn't involve -iquote, but I think it illustrates the same
> problem.
The problem which Mike described had to do with #include_next. So I
don't think this is the same problem.
> One of the STL headers finds our user-appplication deb
On 27 September 2006 01:49, Ian Lance Taylor wrote:
> Mike Stump <[EMAIL PROTECTED]> writes:
>> and this can find a user limits.h in a directory named with -iquote
>> whenever -I- isn't used. The user wishes to not so find that file, as
>> it breaks / on the system.
>
> My understanding has alw
Mike Stump <[EMAIL PROTECTED]> writes:
> In gcc's syslimits.h (gsyslimits.h), we do:
>
> /* syslimits.h stands for the system's own limits.h file.
> If we can use it ok unmodified, then we install this text.
> If fixincludes fixes it, then the fixed version is installed
> instead of t
