http://llvm.org/bugs/show_bug.cgi?id=11298
Reid <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #10 from Reid <[email protected]> 2011-11-02 15:17:32 CDT --- (In reply to comment #9) > > I'm not intentionally defining it. I'm emerging the default 9999 ebuild. > > Would this be the offending param? > > > > > > --with-cxx-include-root=/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include/g++-v4 > > That sounds quite likely. You should file a bug with Gentoo (or wherever you > got the 9999 ebuild) and have them stop doing that. > > Instead, when a new GCC version comes out that Clang doesn't support, they > should file bugs / patch the Clang source code to support them; specifically > InitHeaderSearch.cpp. We've fixed Clang to automatically detect and use newer > GCC installations when linking, but not the libstdc++ headers. > > I'd love to see us eventually have an easy way to at configure time hard code > all the relevant paths, but more than that I'd like the Clang binary by > default > to Just Work on most distros and even as GCC gets upgraded. Thus, I've focused > most of my efforts there. I've added support to Clang for finding and using > GCC > 4.5.3 headers on Gentoo in r143567. Let me know if you need any additional > paths added. OK -- thanks for your help. i'll continue to work with it tomorrow and see if I can get the above to not be passed. I'll try to get a bug into gentoo bugzilla noting this also. -- Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ LLVMbugs mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
