<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Sat, Jan 5, 2013 at 5:59 PM, 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="im">On 01/05/2013 01:11 PM, Dmitri Gribenko wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Sat, Jan 5, 2013 at 7:48 PM, Edward Diener<br>
<<a href="mailto:eldlistmailingz@tropicsoft.com" target="_blank">eldlistmailingz@tropicsoft.<u></u>com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I actually found out that llvm/configure will choose clang if it is<br>
found in the path. This contradicts what is written at<br>
<a href="http://llvm.org/docs/GettingStarted.html#requirements" target="_blank">http://llvm.org/docs/<u></u>GettingStarted.html#<u></u>requirements</a>, where it says it<br>
will use the first GCC it finds. Perhaps that explanation needs to be<br>
updated.<br>
</blockquote>
<br>
Updated docs in r171630.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Finally I found that if llvm/configure uses clang instead of gcc, it<br>
invariably fails on my Linux distros because it is using the gcc<br>
distributed included directories and an earlier version of clang will<br>
often fail with these gcc header files. Once I force llvm/configure to<br>
use gcc, building llvm/clang succeeds again.<br>
</blockquote>
<br>
Right. Maybe we need to skip old clang versions in this case.<br>
</blockquote>
<br></div>
I think this should be done until clang can use its own header files and libraries, when it is installed as a binary, rather than the ones that gcc installs. In fact I am a bit amazed that clang does not already have its own header files and libraries for use when one tries llvm/configure and it sets up llvm's build system to use clang as its compiler. Is this the fault of clang or is it the fault of the llvm/configure system ?</blockquote>
<div><br></div><div style>There is no complete solution for LLVM-only headers/libraries yet on Linux. For C++, you can use libc++, but you still need some GCC libraries (or alternatives). And you will at least need glibc or another compatible C runtime.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/<u></u>mailman/listinfo/llvmdev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><br><div>Thanks,</div><div><br></div><div>Justin Holewinski</div>
</div></div>