Does not install on Mac OS X Mavericks about ultramemcache

[jskorpan]

Hi
I haven’t got a clue how that argument gets in there, probably is some Python build issue rather than umemcache
//JT

From: Alan Hamlett [mailto:[email protected]]
Sent: den 13 maj 2014 04:03
To: esnme/ultramemcache
Subject: [ultramemcache] Does not install on Mac OS X Mavericks (#30)

running build

running build_ext

building 'umemcache' extension

creating build

creating build/temp.macosx-10.9-intel-2.7

creating build/temp.macosx-10.9-intel-2.7/python

creating build/temp.macosx-10.9-intel-2.7/lib

cc -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 -Wsho

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 'cc' failed with exit status 1

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/30.

[ingmar]

This is due to a change in clang. It'll basically start throwing errors upon seeing unknown (usually GCC specific) command line arguments, while previously it just ignored them. You can temporarily disable the error by setting ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future. So to install something via PIP (this affects pretty much any C extension):

env ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future pip install umemcache