On 10/23/07, Andrew Lentvorski <[EMAIL PROTECTED]> wrote:
>
> The fact that there is path coupling between internal and external
> files. The fact that the preprocessor does textual substitution rather
> than syntactic substitution.
>
> What does:
> #include <stdio.h>
>
> mean? Which stdio.h? From where? In what order?
Is this a rhetorical question? If not, see below:
- - - - - - -
2.3 Search Path
GCC looks in several different places for headers. On a normal Unix
system, if you do not instruct it otherwise, it will look for headers
requested with #include <file> in:
/usr/local/include
libdir/gcc/target/version/include
/usr/target/include
/usr/include
- - - - - - -
If you want more, there is a page full at
<http://gcc.gnu.org/onlinedocs/gcc-4.1.1/cpp/Search-Path.html#Search-Path>
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
