Boost.Python and g++

Eric Gallager egall at
Thu Jul 24 06:27:41 PDT 2014

On Wed, Jun 4, 2014 at 4:18 PM, "René J.V. Bertin" <rjvbertin at>

> 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)?


> 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 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the macports-dev mailing list