Graham:
Thank you so much for all your help!!
I am not sure exactly how I cleared up the problem. I ran apache
under gdb and could not reproduce the error. I have successfully run
the test application on Mac OS X Leopard!
I also have built a Fedora server as a backup in case this
installation
Graham:
I could not run the mod_wsgi test because it apparently will not
load. When I restart Apache with mod_wsgi.so loaded, I get
segmentation faults in the error log:
[Fri Feb 11 09:55:04 2011] [notice] child pid 78060 exit signal
Segmentation fault (11)
The results you asked for:
On 12 February 2011 03:02, Michael Bartz michael.ba...@gmail.com wrote:
Graham:
I could not run the mod_wsgi test because it apparently will not
load. When I restart Apache with mod_wsgi.so loaded, I get
segmentation faults in the error log:
[Fri Feb 11 09:55:04 2011] [notice] child pid
I will be more specific :).
The server is a Mac Mini running Mac OS X 10.5.8:
Model Name: Mac mini
Model Identifier: Macmini2,1
Processor Name: Intel Core 2 Duo
I have the 64-bit version of MySQL 5.1 installed as follows:
mysql-5.1.55-osx10.5-x86_64
I downloaded the most recent
On 11 February 2011 00:21, Michael Bartz michael.ba...@gmail.com wrote:
I will be more specific :).
The server is a Mac Mini running Mac OS X 10.5.8:
Model Name: Mac mini
Model Identifier: Macmini2,1
Processor Name: Intel Core 2 Duo
I have the 64-bit version of MySQL 5.1
Graham:
FYI, I rolled everything back to a base install again and started from
scratch just to make sure that I did not have something lurking.
When I built MySQL-python I noticed this warning this time:
In file included from _mysql.c:36:
/usr/local/mysql/include/my_config.h:1069:1: warning:
On 11 February 2011 08:29, Michael Bartz michael.ba...@gmail.com wrote:
Graham:
FYI, I rolled everything back to a base install again and started from
scratch just to make sure that I did not have something lurking.
When I built MySQL-python I noticed this warning this time:
In file
mail:~ bartz$ arch -x86_64 python
arch: posix_spawnp: python: Bad CPU type in executable
mail:~ bartz$ ARCHPREFERENCE=x86_64 python
Python 2.5.1 (r251:54863, Sep 1 2010, 22:03:14)
[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
Type help, copyright, credits or license for more information.
import
On 11 February 2011 10:04, Michael Bartz michael.ba...@gmail.com wrote:
mail:~ bartz$ arch -x86_64 python
arch: posix_spawnp: python: Bad CPU type in executable
That means your Python is fat, ie., supporting both 32bit and 64bit.
Remember now. On Leopard the Apple Python although it provided
Graham:
Thanks for the reply. I realize that the solution is to upgrade to
Snow Leopard, but that is not an option currently.
I certainly may have gotten lost wandering through version levels of
the different components.
I think my problems started when I tried to build the MySQLdb
connector
On 10 February 2011 04:44, Michael Bartz michael.ba...@gmail.com wrote:
Graham:
Thanks for the reply. I realize that the solution is to upgrade to
Snow Leopard, but that is not an option currently.
I certainly may have gotten lost wandering through version levels of
the different
I seem to keep going around in circles :(.
I have to use MacPython 2.6 so that MySQLdb will compile properly.
But I can't seem to create a workable mod_wsgi with a Python updated
from the system version.
The wiki implies that that MacPython will peacefully co-exist with the
System Python, which
What is the specific MySQLdb problem you are trying to resolve? The
one where its standard build scripts only build it for 32 bit and not
for both 32 bit and 64 bit? In other words, tell us clearly the
original problem you are trying to solve and not what you steps you
are taking to try and solve
13 matches
Mail list logo
