Sorry for not replying, but I have lost Internet access at home and may not get it back for a few more days.
Right now you are treating the symptom and not the cause. What you have may still not work reliably because the extension is only linked with single threaded version of MySQL library and not the re entrant _r version. Not linking with _r version would be caused by MySQL config script not being found or not running properly when pip was run to install module. I would like to sort this out properly still when I get my Internet back. Graham On Saturday, 19 November 2011, Simon Kesenci <[email protected]> wrote: > I've solved this with install_name_tool: > > sudo install_name_tool -change libmysqlclient.16.dylib /full/path/to/libmysqlclient.16.dylib {file which can't load dylib} > > --S. > > On Nov 18, 2011, at 16:33, Graham Dumpleton <[email protected]> wrote: > >> This is an issue with how MySQLdb Python module is built. Can you tell >> me how you installed it? >> >> Did you use pip, or did you download package as tar.gz and run setup.py in it? >> >> I have tried twice before to sort this out with people on IRC but they >> would not do what I asked them to help me solve it properly. I am at >> least most of the way along sorting out what the issue is however. :-) >> >> Graham >> >> On 19 November 2011 08:41, mathew davis <[email protected]> wrote: >>> I am trying to run django on osx 10.7 (lion) with apache mod_wsgi and >>> virtualenv. >>> My site works if I use the django testing server: >>> >>>> (baseline)otter:hello mathew$ python manage.py runserver >>> >>> but it doesn't work when I run apache. The core of the error seems to be >>> >>>> Library not loaded: libmysqlclient.16.dylib >>> >>> I think its to do with the path apache is using to locate >>> libmysqlclient.16.dylib >>> >>> when I run otool in the lib directory it looks good >>> >>>> otter:lib mathew$ pwd >>>> /usr/local/mysql/lib >>>> >>>> otter:lib mathew$ otool -L libmysqlclient.16.dylib >>>> libmysqlclient.16.dylib: >>>> libmysqlclient.16.dylib (compatibility version 16.0.0, current >>>> version 16.0.0) >>>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, >>>> current version 125.0.1) >>>> >>> >>> but from outside it can't find it >>> >>>> otter:lib mathew$ cd / >>>> otter:/ mathew$ otool -L libmysqlclient.16.dylib >>>> otool: can't open file: libmysqlclient.16.dylib (No such file or >>>> directory) >>> >>> if i manually set DYLD_LIBRARY_PATH otool works >>> >>>> otter:lib mathew$ DYLD_LIBRARY_PATH=/usr/local/mysql/lib otter:lib >>>> mathew$ otool -L libmysqlclient.16.dylib libmysqlclient.16.dylib: >>>> libmysqlclient.16.dylib (compatibility version 16.0.0, current >>>> version 16.0.0) /usr/lib/libSystem.B.dylib (compatibility version >>>> 1.0.0, current version 125.0.1) >>> >>> When I run the django testing server, my .bash_profile sets up the >>> virtualenv and the path to the mysql dynamic library >>> >>>> export DYLD_LIBRARY_PATH=/usr/local/mysql/lib/:$DYLD_LIBRARY_PATH >>>> export PATH >>> >>> When i run apache it finds my virtualenv paths, but it doesn't seem to find >>> the dynamic library path. >>> >>> I tried adding this path to /usr/sbin/envvars >>> >>>> DYLD_LIBRARY_PATH="/usr/lib:/usr/local/mysql/lib:$DYLD_LIBRARY_PATH" >>>> export DYLD_LIBRARY_PATH >>> >>> and to /private/etc/paths.d/libmysql >>> >>>> /usr/local/mysql/lib >>> >>> then restarted the machine >>> but that has not changed the error message. >>> >>>> Error loading MySQLdb module: >>>> dlopen(/usr/local/python_virtualenv/baseline/lib/python2.7/site-packages/_mysql.so, >>>> 2): >>>> Library not loaded: libmysqlclient.16.dylib >>> >>> >>> I don't think is a permissions issue: >>> >>>> -rwxr-xr-x 1 root wheel 3787328 4 Dec 2010 >>>> libmysqlclient.16.dylib >>>> >>>> drwxr-xr-x 39 root wheel 1394 18 Nov 21:07 / >>>> drwxr-xr-x@ 15 root wheel 510 24 Oct 22:10 /usr >>>> drwxrwxr-x 20 root admin 680 2 Nov 20:22 /usr/local -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
