Most of my attempts were with version 3.3, though at one point I did install Mercurial and pull the latest from source. No luck there either, though I do not recall whether the error for that one differed. So perhaps I should limit my efforts to the latest from the repository?
Kevin On Wed, May 16, 2012 at 5:29 PM, Graham Dumpleton < [email protected]> wrote: > > > You cannot use mod_wsgi 3.3 source code or precompiled binary, you need to > use 3.X or 4.X branches from mod_wsgi source code repository. What code or > binary were you using? > > Graham > > On 17/05/2012, at 5:47 AM, Abilard <[email protected]> wrote: > > Yesterday I installed Apache 2.4.2 on Mac OS X 10.7.4, creating a plist > file to launch it at boot (Apple's built-in web sharing is turned off). > MySQL and PHP were installed next: > > PHP 5.3.10 with Suhosin-Patch (cli) > mysql Ver 14.14 Distrib 5.5.24, for osx10.6 (i386) > > The PHP module (libphp5.so) is running happily. I then attempted to setup > Apache to handle Python through mod_wsgi.so and am encountering the > following error when I test the config file: > > httpd: Syntax error on line 149 of /usr/local/apache2/conf/httpd.conf: > Cannot load /usr/local/apache2/modules/mod_wsgi.so into server: > dlopen(/usr/local/apache2/modules/mod_wsgi.so, 10): Symbol not found: > _ap_accept_lock_mech\n Referenced from: > /usr/local/apache2/modules/mod_wsgi.so\n Expected in: flat namespace\n in > /usr/local/apache2/modules/mod_wsgi.so > > Searching the web turned up these hypotheses as to what might cause errors > of this kind: > > 1. Mixing 64-bit Apache and 32-bit Python. > 2. Running old versions of Python. > 3. Having multiple versions of Apache. > 4. Not using MacPorts. > 5. Not using HomeBrew. > 6. Not using Linux. > > I've attempted forcing Apache to run in 32-bit mode; putting Python 3.2 in > the path; specifying apxs2 & python during configure; altering the Makefile > to ensure proper architecture; using MacPorts; installing HomeBrew and > running the other way; and half a dozen other things I have forgotten now > to no avail. As for #6, my Ubuntu dev box is running mod_python just fine. > My goal is getting my MacBook Pro to run mod_wsgi.so (which, I gather, is > now preferred over mod_python). > > Any ideas? > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/modwsgi/-/-8UvZJ9UJCoJ. > 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. > > -- > 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. > -- 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.
