<div dir="ltr">Yeah this is one of those "known problems". MinGW never had a proper toolchain implemented, I think Ruben was working on this. Include paths come from hardcoded versions listed in InitHeaderSearch.cpp.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Aug 16, 2014 at 11:12 AM, Edward Diener <span dir="ltr"><<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 8/15/2014 10:23 AM, Craig Tenenbaum wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
On Fri, Aug 15, 2014 at 9:28 AM, Edward Diener<br>
<<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.<u></u>com</a><br></div><div class="">
<mailto:<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@<u></u>tropicsoft.com</a>>> wrote:<br>
<br>
Here is my output:<br>
<br></div>
C:\Programming\VersionControl\<u></u>__bninja_installed_clang\bin>_<u></u>_clang++<div class=""><br>
-E -v -### -x c<br>
++ NUL<br>
<br>
clang version 3.6.0 (215674)<br>
Target: i686-pc-windows-gnu<br>
Thread model: posix<br></div>
"C:\\Programming\\__<u></u>VersionControl\\bninja___<u></u>installed_clang\\bin\\clang++.<u></u>__exe" "-c<div class=""><br>
c1" "-triple" "i686-pc-windows-gnu" "-E" "-disable-free"<br>
"-disable-llvm-verifier<br>
" "-main-file-name" "NUL" "-mrelocation-model" "static"<br>
"-mdisable-fp-elim" "-fm<br>
ath-errno" "-masm-verbose" "-mconstructor-aliases" "-target-cpu"<br>
"pentium4" "-v"<br>
"-dwarf-column-info" "-resource-dir"<br></div>
"C:\\Programming\\__<u></u>VersionControl\\bninja_i<br>
nstalled_clang\\bin\\..\\lib\\<u></u>__clang\\3.6.0"<br>
"-fdeprecated-macro" "-fdebug-compil<br>
ation-dir"<br>
"C:\\Programming\\__<u></u>VersionControl\\bninja___<u></u>installed_clang\\bin"<div class=""><br>
"-ferr<br>
or-limit" "19" "-fmessage-length" "80" "-mstackrealign"<br>
"-fno-use-cxa-atexit" "-<br>
fobjc-runtime=gcc" "-fcxx-exceptions" "-fexceptions"<br>
"-fdiagnostics-show-option"<br>
"-fcolor-diagnostics" "-o" "-" "-x" "c++" "NUL"<br>
<br>
<br>
I do not see header path information anywhere.<br>
<br>
Sorry, my bad, try: clang++ -E -v -x c++ NUL<br>
</div></blockquote>
<br>
Bingo ! That gives me the output I expected.<br>
<br>
But it is looking in all sorts of non-existent directories related to gcc versions 4.7.0 through 4.8.2, which of course don't exist since I used mingw64 gcc-4.9.1 32-bit to build clang. And therefore it does not find the C++ standard libraries of gcc-4.9.1.<br>
<br>
I can switch to mingw gcc-4.8.1 and hopefully that will work after I rebuild the latest clang.<br>
<br>
The moral of the story is that building clang from source on Windows targeting gcc will not work with gcc outside the 4.7.0 to 4.8.2 range. I wish such simple things were documented somewhere in clang documentation.<br>
<br>
Did I miss it ? Is there any clang table which specifies which clang versions depend on which gcc version ranges ?<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">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/<u></u>mailman/listinfo/cfe-dev</a><br>
</div></div></blockquote></div><br></div>