Resolving libc #includes

James Antill james@and.org
Tue Nov 16 17:50:00 GMT 2004


Earl Chew <earl_chew@agilent.com> writes:

> Roland McGrath wrote:
>> If you are using -I options you are getting what you asked for.
>> If not, that's why #include <...> or different from #include "...".
>
> Say I use:
>
> 	% cat foo.c
> 	...
> 	#include <stdio.h>
> 	...
>
> 	% gcc -I application/includes -c foo.c

 Use gcc -I application/includes -I- -c foo.c

> and I happen to have a file named application/includes/features.h.

 Then it won't be picked up with #include <features.h> only
with #include "features.h"

-- 
# James Antill -- james@and.org
:0:
* ^From: .*james@and\.org
/dev/null



More information about the Libc-alpha mailing list