[Pythonmac-SIG] MySQLdb on OS X?

David Warde-Farley dwf at cs.toronto.edu
Thu Oct 30 21:39:25 CET 2008


On 30-Oct-08, at 3:35 PM, Joe Strout wrote:

> building '_mysql' extension
> creating build/temp.macosx-10.5-i386-2.5
> gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused- 
> madd -fno-common -dynamic -DNDEBUG -g -Os -Wall -Wstrict-prototypes - 
> DMACOSX -I/usr/include/ffi -DENABLE_DTRACE -pipe - 
> Dversion_info=(1,2,2,'final',0) -D__version__=1.2.2 -I/usr/local/ 
> mysql/include -I/System/Library/Frameworks/Python.framework/Versions/ 
> 2.5/include/python2.5 -c _mysql.c -o build/temp.macosx-10.5-i386-2.5/ 
> _mysql.o -Os -arch i386 -fno-common
> In file included from /usr/local/mysql/include/mysql.h:47,
>                 from _mysql.c:40:
> /usr/include/sys/types.h:92: error: duplicate ‘unsigned’
> /usr/include/sys/types.h:92: error: two or more data types in  
> declaration specifiers
> error: command 'gcc' failed with exit status 1

Whatever this is, it's specific to the system python. MySQLdb builds  
fine for me with the python.org release, but fails in exactly the same  
manner using Apple's python (which in my experience is chronically  
broken in one way or another, but there are now those among us who  
feel more positively about it.

I'm guessing the system python's headers are doing something that  
conflicts with mysql's headers. If installing/using python.org python  
is an option, I'd recommend doing that.

David


More information about the Pythonmac-SIG mailing list