[cfe-dev] system includes

Diego Iastrubni diegoiast at gmail.com
Mon Feb 15 12:45:09 PST 2010

So you want to lock the directories to the directories of the compiler which
bootstrapped clang? Not smart, what happens when you change gcc compiler on
your system? clang will fail.

IMHO, the best solution would be to find it on "standard" paths... maybe add
a "--gcc-include-path" parameter or something. What do you think?

On Mon, Feb 15, 2010 at 3:21 PM, Andy Wick <Andy.Wick at corp.aol.com> wrote:

>  Stupid question, if using g++ to compile clang would it be possible to
> discover the system include just by looking at the –v output?  We use non
> standard locations.
> g++ -v t.c
> #include <...> search starts here:
>  /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/i686-pc-linux-gnu/4.3.3/include
>  /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/i686-pc-linux-gnu/4.3.3/include-fixed
>  /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/../../include/g++
>  /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/../../include/g++/i686-pc-linux-gnu
>  /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/../../include/g++/backward
>  /opt/bcs/include
>  /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/../../include
>  /usr/include
> End of search list.
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20100215/ccdf132a/attachment.html>

More information about the cfe-dev mailing list