Re: Boost.Python and g++
On Wed, Jun 4, 2014 at 4:18 PM, René J.V. Bertin rjvber...@gmail.com wrote: On Jun 04, 2014, at 20:21, Eric Gallager wrote: 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. Does gcc still support spec files (cf. gcc -dumpspecs)? Yes. If so, one could probably patch in the information via that mechanism, and not add a series of library specifications regardless of whether you're linking or not ... In any case I'd invoke the system clang compiler. ...this is just to get the version number, right? If we include this script in a port (such as the one ryandesign is working on in https://trac.macports.org/ticket/44413 for example), we could avoid having to actually invoke the compiler by just using the `configure.compiler` setting, and then `reinplace`-ing that into the script. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Boost.Python and g++
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.demai...@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-us...@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
