Home Original page

MySQLdb compile error with AMD64

Keith Burns keith at nekotaku.com
Tue Feb 28 22:43:51 EST 2006 
Found it.

Had to change
Extra_compile_args = config(cflags) to the actual list with -march=athlon64

Now just realized that I didn't download the right RPMs for MySQL for SUSE
on AMD64 (so got lib errors I am assuming cos of that).

Will download and update with what I changed in the setup.py once I get this
working.

Thanks for the pointers and getting me on the right track!

_____________________________________________
From: Keith Burns [mailto:keith at nekotaku.com] 
Sent: Tuesday, February 28, 2006 8:04 PM
To: 'python-list at python.org'
Subject: MySQLdb compile error with AMD64


>> Can anyone offer any assistance on this one?
>
>Look here:
>
>>> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -fmessage-length=0 -Wall
>>> -D_FORTIFY_SOURCE=2 -g -fPIC -I/usr/include/mysql
>>> -I/usr/include/python2.4 -c _mysql.c -o
>>> build/temp.linux-x86_64-2.4/_mysql.o -I/usr/include/mysql -g
>>> -march=i586 -mcpu=i686 -fmessage-length=0
>
>specifically at -march=i586. MySQLdb sets CFLAGS which aren't applicable to
>your processor, and as such the compile barfs. You should probably just run
>it with something like
>
>CFLAGS="-march=athlon-64" python setup.py build
>
>I am positive that MySQLdb works on AMD64, I have it running there. Anyway,
>the CFLAGS fix should work.

Hey there!

Appreciate the help but the CFLAGS did not change the gcc -march (I tried it
as above and with CFLAGS="-march=athlon64" which I found in a GCC flag FAQ).


I realize that the -march is my problem but I can't work out how to change
it.

Any ideas?

Thanks!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20060228/d3bac2f1/attachment.html>
More information about the Python-list mailing list