[ https://issues.apache.org/jira/browse/MESOS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930707#comment-13930707 ]
Till Toenshoff commented on MESOS-1079: --------------------------------------- Some more information on this subject. clang 3.4 is now obviously throwing errors on unknown command line parameters where it previously did only warn the user. This is not OS X specific but certainly clang 3.4 and above specific. http://llvm.org/releases/3.4/tools/clang/docs/ReleaseNotes.html#new-compiler-flags > Mesos python egg build failure on OS X Mavericks (Xcode 5.1) > ------------------------------------------------------------ > > Key: MESOS-1079 > URL: https://issues.apache.org/jira/browse/MESOS-1079 > Project: Mesos > Issue Type: Bug > Environment: Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM > 3.4svn), Apple's Python 2.7.5 > Reporter: Till Toenshoff > Assignee: Till Toenshoff > Priority: Critical > Labels: build, clang, failure, python, xcode5.1 > > building '_mesos' extension > gcc -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -g -Os > -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd > -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes > -Wshorten-64-to-32 -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes > -DENABLE_DTRACE -arch x86_64 -arch i386 -pipe > -I/Users/till/Development/mesos-till/build/../include > -I/Users/till/Development/mesos-till/build/include > -I/Users/till/Development/mesos-till/build/src > -I/Users/till/Development/mesos-till/build/src/python/native > -I/Users/till/Development/mesos-till/build/3rdparty/libprocess/3rdparty/protobuf-2.5.0/src > -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 > -c native/mesos_executor_driver_impl.cpp -o > build/temp.macosx-10.9-intel-2.7/native/mesos_executor_driver_impl.o > clang: error: unknown argument: '-mno-fused-madd' > [-Wunused-command-line-argument-hard-error-in-future] > clang: note: this will be a hard error (cannot be downgraded to a warning) in > the future > error: command 'gcc' failed with exit status 1 > make[2]: *** [python/dist/mesos-0.19.0-py2.7-macosx-10.9-intel.egg] Error 1 > make[1]: *** [check] Error 2 > make: *** [check-recursive] Error 1 > The problem (once again) is the fact that the python-egg build-process of > distutils grabs the compiler settings from the settings that python was built > with. > $ python-config --cflags > -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 > -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 > -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -g -Os > -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd > -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes > -Wshorten-64-to-32 -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes > -DENABLE_DTRACE > So that is where "-mno-fused-madd" comes from. > I am currently puzzled on why our configuration phase did not detect this > problem. -- This message was sent by Atlassian JIRA (v6.2#6252)