[mod_python] cannot configure mod_python 3.2.8

J. Jeffrey Close wrote ..
> 
> I thought that this required apache 2.0 & did not allow 2.2 ?

Well spotted, I didn't notice that and just addressed the initial
presenting problem in relation to version of bash being used.
So yes, even once built and installed, they will probably find
that it doesn't work anyway because of Apache 2.0 not being
used.

FWIW, mod_python 3.2.10 which includes Apache 2.2 support
is real close now. We did actually have a mod_python 3.2.9 ready
to release, but some memory leaks were found at the last moment
and we felt it prudent to address them now rather than later.

Graham

> ----- Original Message ----
> From: mvanier <mvanier at cs.caltech.edu>
> To: Graham Dumpleton <grahamd at dscpl.com.au>
> Cc: mod_python at modpython.org
> Sent: Monday, July 17, 2006 7:59:21 PM
> Subject: Re: [mod_python] cannot configure mod_python 3.2.8
> 
> Got it.  It compiles now.  Thanks!  That sets a record for fast fixes ;-)
> 
> Mike
> 
> Graham Dumpleton wrote:
> > See:
> > 
> >   http://issues.apache.org/jira/browse/MODPYTHON-122
> > 
> > Make changes to "configure" script as described therein.
> > 
> > Graham
> > 
> > mvanier wrote ..
> >> I'm trying to compile mod_python 3.2.8 and was surprised to find it
> failing
> >> at 
> >> the configure stage:
> >>
> >> % configure --with-apxs=/usr/local/packages/apache/bin/apxs
> >> checking for gcc... gcc
> >> checking for C compiler default output file name... a.out
> >> checking whether the C compiler works... yes
> >> checking whether we are cross compiling... no
> >> checking for suffix of executables...
> >> checking for suffix of object files... o
> >> checking whether we are using the GNU C compiler... yes
> >> checking whether gcc accepts -g... yes
> >> checking for gcc option to accept ANSI C... none needed
> >> checking for ar... ar
> >> checking for a BSD-compatible install... 
> >> /usr/local/packages/coreutils/bin/install -c
> >> checking whether make sets $(MAKE)... yes
> >> checking for main in -lm... yes
> >> checking for an ANSI C-conforming const... yes
> >> checking your blood pressure... a bit high, but we can proceed
> >> configure: checking whether apxs is available...
> >> checking for --with-apxs... /usr/local/packages/apache/bin/apxs executable,
> >> good
> >> checking Apache version... 2.2.2
> >> checking for Apache libexec directory... /usr/local/packages/apache/modules
> >> checking for Apache include directory... -I/usr/local/packages/apache/include
> >> checking for --with-python... no
> >> checking for python... /usr/local/packages/python/bin/python
> >> checking Python version... 2.4
> >> checking Python install prefix... /usr/local/packages/python
> >> checking checking where python libraries are installed... 
> >> /usr/local/packages/python/lib/python2.4
> >> checking for Py_NewInterpreter in -lpython2.4... yes
> >> checking what libraries Python was linked with... -lpython2.4   -lpthread
> >> -ldl 
> >> -lutil   -lm
> >> checking linker flags used to link Python...
> >> checking where Python include files are... 
> >> -I/usr/local/packages/python/include/python2.4
> >> configure: line 3427: syntax error near unexpected token `('
> >> configure: line 3427: `  as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`'
> >>
> >> My computer is running Debian Linux unstable, and python and apache
> have
> >> been 
> >> compiled from source.  Does anyone know why this might be happening?
> >>
> >> Thanks in advance,
> >>
> >> Mike
> >>
> >>
> >> _______________________________________________
> >> Mod_python mailing list
> >> Mod_python at modpython.org
> >> http://mailman.modpython.org/mailman/listinfo/mod_python
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://mailman.modpython.org/mailman/listinfo/mod_python