This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Resolving libc #includes
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