<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 14, 2017 at 2:33 PM, René J.V. Bertin via cfe-dev <span dir="ltr"><<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
I have a question about the commit that should help prevent errors building boost headerfiles (<a href="https://github.com/llvm-mirror/libcxx/commit/6010dc84c66ee4b30b4ffea34b0d1c616d04239b#commitcomment-22132510" rel="noreferrer" target="_blank">https://github.com/llvm-<wbr>mirror/libcxx/commit/<wbr>6010dc84c66ee4b30b4ffea34b0d1c<wbr>616d04239b#commitcomment-<wbr>22132510</a>).<br>
<br>
I'm seeing the issue reported in <a href="http://stackoverflow.com/questions/41050942/clang-modules-interaction-with-std-iterator-and-boost-move-iterator-hpp" rel="noreferrer" target="_blank">http://stackoverflow.com/<wbr>questions/41050942/clang-<wbr>modules-interaction-with-std-<wbr>iterator-and-boost-move-<wbr>iterator-hpp</a> , but (and this may be a bit delicate) I'm seeing it with a gcc 6.3 build I'm adapting (ok, tweaking) to use libc++ and the corresponding headers, on Mac OS X 10.9 .<br></blockquote><div><br></div><div>Just to be clear, You're attempting to build GCC 6.3 using Clang, and you've hacked up the GCC build so that it always uses libc++ instead of libstdc++?</div><div>AFAIK the GCC build doesn't use Boost, so IDK how Boost is getting into the mix.</div><div><br></div><div>If you meant that you're building something else (which uses Boost) using GCC 6.3, that also doesn't make sense because GCC doesn't support Clang Modules.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
If I understand the fix correctly, it addresses an issue that isn't in the system libc++ on that OS version, so how come I'm seeing it?<br></blockquote><div><br></div><div>I would assume the issue *would* be present in the OS X's system libc++ installation, (assuming the system installation hasn't been updated to include the fix, which it likely hasn't)</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Should I not build g++ using the clang 4.0 C++ headers for now, or maybe make that tweak runtime-only and deactivate it while building g++ itself?<br></blockquote><div><br></div><div>Why are you forcing GCC to build against libc++ in the first place? What's the benefit? Doesn't the build default to bootstrapping and using a bootstrapped libstdc++?</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Thanks for any insights,<br>
<br>
R.<br>
______________________________<wbr>_________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/<wbr>mailman/listinfo/cfe-dev</a><br>
</blockquote></div><br></div></div>