<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
If you check the Clang list (cfe-dev-list) the issue dealing with
atomics for gcc-4.7 has been settled. I can verify this on Debian
Linux using gcc-4.7 that clang/clang++ builds and no long fails when
compiling a simple HelloWorld program. Atomics for c++ are now
recognized as __c11_atomic_* and it builds cleanly from what i've
tested.<br>
<br>
I presently don't have a 10.7 box to test against trunk, but those
errors are now gone from Linux.<br>
<br>
The thread to read:<br>
<a
href="http://lists.cs.uiuc.edu/pipermail/cfe-dev/2012-April/020686.html"><br>
http://lists.cs.uiuc.edu/pipermail/cfe-dev/2012-April/020686.html</a><br>
<br>
- Marc<br>
<br>
On 04/12/2012 10:44 AM, Andrea Bigagli wrote:
<blockquote cite="mid:0A5F9BAC-C985-4E04-B90D-90F20309DAD7@me.com"
type="cite">Hi,
<div>the subject says it all...</div>
<div><br>
</div>
<div>After some experimenting, I got a bit confused as far as what
the proper thing to do might be....</div>
<div><br>
</div>
<div>I build llvm/clang from trunk sources on OSX Lion 10.7.3
(i.e. x86_64-apple-darwin11.3.0 to speak GNU's platform-ese)
where I also have successfully built a fsf-gcc 4.6.2 (and lately
a 4.7 for that matter) from sources.</div>
<div>Now, I think I understand that by playing with clang's
lib/Frontend/InitHeaderSearch.cpp you can have clang use
whatever libstdc++ include files you want.</div>
<div><br>
</div>
<div>Is that really true and fully supported practice, or do you
have, when on OSX, either stick with Apple's (through
Xcode-)provided gcc 4.2.1's libstdc++ or the all-new (but still
a bit immature) libc++?</div>
<div><br>
</div>
<div>I'm aware (after posting <a moz-do-not-send="true"
href="http://llvm.org/bugs/show_bug.cgi?id=12303">http://llvm.org/bugs/show_bug.cgi?id=12303</a>) that
if you build clang with paths tuned for, say, gcc-4.6's
libstdc++, then you have to remember, every time you build
something with clang++, to always make the linker find gcc-4.6's
libstdc++, but as cumbersome as it might seem (if there's some
configure hook that avoids the need of always passing
"-L<wherever gcc-4.6'libstdc++ lives>" I'd really be happy
to use it), it's always worked for me.</div>
<div><br>
</div>
<div>Until lately, when I built the latest gcc-4.7 and since then
clang++ (rebuilt of course with paths updated for the new
compiler) chokes on every cpp file as soon as I start including
something like <iostream> or <vector> etc..</div>
<div><br>
</div>
<div>Is it just a problem with gcc-4.7 libstdc++ headers that for
some reason clang++ is not (yet) able to digest, or have I
always been doing something not supported on OSX and I've just
been lucky that it has been working until now?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Andrea.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a class="moz-txt-link-freetext" href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>
<a class="moz-txt-link-freetext" href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
Marc J. Driftmeyer<br>
Email :: <a href="mailto:mjd@reanimality.com">mjd@reanimality.com</a><br>
Web :: <a href="http://www.reanimality.com">http://www.reanimality.com</a><br>
Cell :: (509) 435-5212
</div>
</body>
</html>