<div dir="ltr">Wow, that looks a lot simpler than I thought that it would be... I was expecting something like this would have to be fixed upstream by gcc, because that is how they handle the GNU vs. NeXT Objective C runtime issues, but if all it takes in this case is this script, it seems like just using this script would be easier... the main thing I worry about would be how the version numbers are hardcoded, but that seems like it should be easy enough to fix.<div>
<br></div><div>(cc-ing macports-dev because this seems like more of a development issue)</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 2, 2014 at 7:29 AM, Akim Demaille <span dir="ltr"><<a href="mailto:akim.demaille@gmail.com" target="_blank">akim.demaille@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
A long long time ago I had started discussing (well, complaining<br>
might be more appropriate :-) about the fact that I could no<br>
longer use g++ to compile my project, because Boost.Python was<br>
compiled with clang++'s libc++.<br>
<br>
Well, since then I managed to wrap a dirty script, g++-libc++,<br>
which does the trick for me: it compiles with g++, but using<br>
libc++. It might be useful for some users. Actually, maybe it<br>
should be shipped with MacPorts' g++ (some distros provide similar<br>
scripts to GNU/Linux to use clang++ on top of libstdc++).<br>
<br>
Cheers.<br>
<br>
<br>_______________________________________________<br>
macports-users mailing list<br>
<a href="mailto:macports-users@lists.macosforge.org">macports-users@lists.macosforge.org</a><br>
<a href="https://lists.macosforge.org/mailman/listinfo/macports-users" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-users</a><br>
<br></blockquote></div><br></div>