Boost.Python and g++

[Eric Gallager]

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.

(cc-ing macports-dev because this seems like more of a development issue)



On Mon, Jun 2, 2014 at 7:29 AM, Akim Demaille <akim.demaille at gmail.com>
wrote:

> Hi all,
>
> A long long time ago I had started discussing (well, complaining
> might be more appropriate :-) about the fact that I could no
> longer use g++ to compile my project, because Boost.Python was
> compiled with clang++'s libc++.
>
> Well, since then I managed to wrap a dirty script, g++-libc++,
> which does the trick for me: it compiles with g++, but using
> libc++.  It might be useful for some users.  Actually, maybe it
> should be shipped with MacPorts' g++ (some distros provide similar
> scripts to GNU/Linux to use clang++ on top of libstdc++).
>
> Cheers.
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140604/7adffd1f/attachment.html>