The configure error was caused by latest upgrade to Bash 3.1. I
switched back to Bash 3.0 and the compile completed.
- Casey
Casey McGinty wrote:
I'm having problems getting mod_python to work in Apache. When running
a python script from a web page I get the message:
"Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request."
Checking the apache logs I see the message:
"[error] make_obcallback: could not import mod_python.apache.\n"
From here I checked the Arch Bug Tracker. I found a matching
issue.
"FS#3738 — mod_python [error] make_obcallback: could not import
mod_python.apache.\n"
"
recently discovered the following error in my apache 2.0.55-1 log
[error] make_obcallback: could not import mod_python.apache.\n
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 24,
in ?
import pdb
File "/usr/lib/python2.4/pdb.py", line 11, in ?
from repr import Repr
File "/usr/lib/python2.4/repr.py", line 6, in ?
from itertools import islice
ImportError: /usr/lib/python2.4/lib-dynload/itertools.so: undefined
symbol: _PyArg_NoKeywords
[notice] caught SIGTERM, shutting down
Solved it by removing mod_python ( pacman -R ) and downloading sources
from http://httpd.apache.org/modules/python-download.cgi
./configure --with-apxs=/usr/sbin/apxs && make && make
install and error gone.
Both mod_python versions used are 3.1.4"
I tried compiling mod_python from the ABS system, but I now get
the following compile error when running the configure script:
"checking linker flags used to link Python...
checking where Python include files are... -I/usr/include/python2.4
./configure: line 2951: syntax error near unexpected token `('
./configure: line 2951: `as_me=`(basename "$0") 2>/dev/null ||'
make: *** No targets specified and no makefile found. Stop."
So, I don't have any other ideas accept mailing mod_python group
(which I did). Does any arch user have mod_python work successfully
after updating to most recent packages?
