On Jan 9, 1:16 pm, "David Grant" <[EMAIL PROTECTED]> wrote: > Why are you compiling mysql and python and mysqldb from scratch? You are > using SUSE are you not? Get the binary rpm packages. > > Dave >
Thanks for the response, David. I need to keep 3 or 4 versions of MySQL handy for my regular work. So initially I tried to use Python/Django with one of those and got: __bootstrap__ ImportError: /home/rmazur/.python-eggs/MySQL_python-1.2.2-py2.5-linux- i686.egg-tmp/_mysql.so: undefined symbol: __pure_virtual Upon googling that, I found that can be caused by compiling MySQL with one version of a compiler (gcc in my case) and compiling Python with another. References of that: http://lists.zenoss.org/pipermail/zenoss-users/2006/000930.html http://forums.mysql.com/read.php?50,133711,152705#msg-152705 So I (reluctantly) decided in order to keep things clean, I would build both MySQL and Python from scratch and assure that those two installs are what my PATH uses when installing MySQLdb. But I am still getting this error when I know for sure the file exists: __bootstrap__ ImportError: libmysqlclient_r.so.15: cannot open shared object file: No such file or directory Any more advice? Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
