[
https://issues.apache.org/jira/browse/MESOS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816808#comment-13816808
]
Niklas Quarfot Nielsen commented on MESOS-799:
----------------------------------------------
The issue was solved in distutils: http://bugs.python.org/issue1222585.
Distutils which comes with stock Mac OS X Python 2.7 does not seem to have this
patch in, which makes custom compiler choice (as in our case) hard.
Fortunately, the python 2.7 which comes with brew does and should work.
> Mesos python egg is faulty on OS X Mavericks
> --------------------------------------------
>
> Key: MESOS-799
> URL: https://issues.apache.org/jira/browse/MESOS-799
> Project: Mesos
> Issue Type: Bug
> Environment: Mac OS X Mavericks, GCC 4.7 & 4.8
> Reporter: Niklas Quarfot Nielsen
> Assignee: Niklas Quarfot Nielsen
>
> The Python framework test (and I suspect other Python frameworks) breaks on
> OS X Mavericks. From a quick study, this is what I found:
> 1) The chosen compiler in $(CC) is not propagated in src/Makefile.am to
> setup.py during python binding compilation.
> 2) When compiler is chosen, compiler flags in distutils are picked up from
> the ones used to compile Python (which most likely was clang). The effect of
> this is hard to pick up; Clang is able to bundle both 32bit and 64bit
> executable into one with multiple "-arch" flags. AFAIK GCC picks only one
> architecture (the last one) which in this case leaves a 32bit image only,
> which then is incompatible with the other binaries.
> Distutil can be configured by setting environment variables to overwrite for
> example linker and compiler flags. LDSHARED and CCSHARED are some, but
> additional need to be set to deal with the 32bit/64bit bundle issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
