python package using a Fortran library
allbery.b at gmail.com
Wed Jul 17 06:56:32 PDT 2013
On Wed, Jul 17, 2013 at 6:55 AM, Ryan Schmidt <ryandesign at macports.org>wrote:
> On Jul 17, 2013, at 04:28, Michael Wimmer <wimmer.mike at gmail.com> wrote:
> >> If the build does not respect the compiler choice, that is a bug that
> should be fixed.
> > thanks for your answer, I understand that this is how it should be done
> > in general. However, what I run into is a general problem, as this is a
> > python setuptools behavior: By default, they always want to use the
> > compiler that python itself has been compiled with (I assume to avoid
> > inconsistencies).
> If that is how Python in MacPorts behaves, then I would call that a bug in
> Python in MacPorts that needs to be fixed. Ports should use the compiler
> indicated by configure.compiler. Anything else is wrong.
Letting (for forcing!) a language extension use a different compiler from
the base language results in extensions that won't load in the base. (True
of Python, Perl, and Tcl at minimum; also likely GHC.) You are correct in
the general case but not in this particular special case, and the Python
and Perl extension mechanisms force the compiler for very good reasons.
brandon s allbery kf8nh sine nomine associates
allbery.b at gmail.com ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-users