-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 20 April 2001 22:02, Olaf Marc Zanger wrote: Hi,
hi there,
after updating a SuSE 7.1 installation (mysql 3.22.32 to 3.32.30) i get the error message at the bottom of this email. Zope 2.3.0 (binary release, python 1.5.2, linux2-x86) ZMySQLDA-1-2-0 MySQLdb-0.1.2
the crazy thing is, 1. if i access the database with the mysql command line client i have no trouble (about 200 rows) on both win and SuSE, 2. if i access the old database on a win system i can do that, but i get no rows back (through the test tab) 3. if i downgrade the mysql on the SuSE system to the old one i have the same trouble as in (2).
i also tried to upgrade to build MySQL-python-0.3.5 and get errors i have no clue about what they are saying (on the bottom of this message.
i tried to fix this for about 100 hours over time and should really get that fixed so help is very appreciated :-)
thanks in before
olaf
error message --------------------------------------- Remarks for Errortracking
[trace deleted]
mysql-python 0.3.5 build log ------------------------------------------- ..py build running build running build_py not copying MySQLdb.py (output up-to-date) not copying CompatMysqldb.py (output up-to-date) not copying _mysql_const/__init__.py (output up-to-date) not copying _mysql_const/CR.py (output up-to-date) not copying _mysql_const/FIELD_TYPE.py (output up-to-date) not copying _mysql_const/ER.py (output up-to-date) not copying _mysql_const/FLAG.py (output up-to-date) not copying _mysql_const/REFRESH.py (output up-to-date) not copying _mysql_const/CLIENT.py (output up-to-date) running build_ext building '_mysql' extension gcc -O2 -m486 -fpic -I/usr/include/mysql -I/usr/include/python2.0 -c ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Seems like suse7.1 has python 2.0 installed. before starting to build you need to set your path to setenv PATH /wherever/zope/lives/bin:${PATH} (in csh - do a rehash after that) in bash export PATH=/wherever/zope/lives/bin:${PATH} when typing which python you should get the python binary installed in your zope/bin directory NOT the one from /usr/bin.
_mysqlmodule.c -o build/temp.linux-i686-2.0/_mysqlmodule.o In file included from /usr/include/bits/posix1_lim.h:126, from /usr/include/limits.h:144, from /usr/lib/gcc-lib/i486-suse-linux/2.95.2/include/limits.h:117, from /usr/lib/gcc-lib/i486-suse-linux/2.95.2/include/syslimits.h:7, from /usr/lib/gcc-lib/i486-suse-linux/2.95.2/include/limits.h:11, from /usr/include/python2.0/Python.h:27, from _mysqlmodule.c:29: /usr/include/bits/local_lim.h:36: linux/limits.h: Datei oder Verzeichnis nicht gefunden In file included from /usr/include/errno.h:36, from /usr/include/python2.0/Python.h:48, from _mysqlmodule.c:29: /usr/include/bits/errno.h:25: linux/errno.h: Datei oder Verzeichnis nicht gefunden
It also looks like you're missing some header files. I'm not very familiar with Suse distribution, but my bet would be on "kernel headers" - however this package is called in the weired naming scheme on the suse CD's. you should see the package descriptions when installing packages with yast (os is it yast2 now ? ) Hope that helps Uwe C. Schröder - -- Uwe C. Schröder ConTrada Consultants Lindenstrasse 15 Tel/Fax: +49 8294 80070 D-86477 Adelsried Mobil: +49 172 8532352 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE64TywTJbO78VG0aIRAsJuAKCFNAka+/DgE0z8xM5AB3IVHi1BrgCgn9q+ 9dD4npTxpIrg+lxW2qDW8zY= =f/G7 -----END PGP SIGNATURE-----