[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: include path
From: |
Paul Pluzhnikov |
Subject: |
Re: include path |
Date: |
16 Oct 2004 23:55:17 -0700 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence) |
"John Max Skaller" <skaller@nospam.com.au> writes:
> Is there any why for gcc/g++ (with various options) to find
> out the header search path for <> and "" includes?
$ gcc -v junk.c
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/2.95.3/specs
...
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/usr/lib/gcc-lib/i486-suse-linux/2.95.3/include
/usr/include
End of search list.
Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.
- include path, John Max Skaller, 2004/10/16
- Re: include path,
Paul Pluzhnikov <=