<div dir="ltr">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.<br><br>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?<br>

<br><div class="gmail_quote">On Mon, Feb 15, 2010 at 3:21 PM, Andy Wick <span dir="ltr"><<a href="mailto:Andy.Wick@corp.aol.com">Andy.Wick@corp.aol.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">





<div>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size: 11pt;">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.<br>


<br>
g++ -v t.c<br>
#include <...> search starts here:<br>
 /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/i686-pc-linux-gnu/4.3.3/include<br>
 /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/i686-pc-linux-gnu/4.3.3/include-fixed<br>
 /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/../../include/g++<br>
 /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/../../include/g++/i686-pc-linux-gnu<br>
 /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/../../include/g++/backward<br>
 /opt/bcs/include<br>
 /opt/bcs/packages/gcc4-4.3.3/bin/../lib/gcc/../../include<br>
 /usr/include<br>
End of search list.<br>
</span></font>
</div>


<br>_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
<br></blockquote></div><br></div>