[ 
https://issues.apache.org/jira/browse/MESOS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827895#comment-13827895
 ] 

Niklas Quarfot Nielsen commented on MESOS-799:
----------------------------------------------

Please refer to: https://issues.apache.org/jira/browse/MESOS-798

Issue is related to:
1) distutils bug which was solved in http://bugs.python.org/issue1222585 (not 
included in Mac OS X stock python2.7)
2) CC/CXX not being passed to python setup.py
3) python needs to be compiled with a GNU GCC as the stdlibc(++) of python and 
the egg will otherwise be incompatible.

So for now, either compile a python your self or disable python during 
configure until we get clang support. So will close ticket for now.

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

Reply via email to