|
Graham Dumpleton
grahamd at dscpl.com.au
Sun Jul 30 03:59:31 EDT 2006
I said to change the "configure" script, not "configure.in". Changing "configure.in" isn't going to help unless you regenerate "configure" using autoconf, which would only be done by developers. I should have been a bit clearer given the bug report mentions "configure.in" as the cause, but a user trying to workaround it should change just "configure" to get it working. Thus, look through "configure" for equivalent line and change it there instead. Graham On 30/07/2006, at 3:58 PM, Vlad Dogaru wrote: > I have changed the text in configure.in, but I still get the same > error. I fail to see how configure.in is used when I run ./configure. > The documentation doesn't seem to help, either. Please excuse my lack > of knowledge, but compiling my own software is a new ground for me. > > Thanks, > Vlad > > On 7/29/06, Graham Dumpleton <grahamd at dscpl.com.au> wrote: >> Known issues. See bug report at: >> >> https://issues.apache.org/jira/browse/MODPYTHON-122 >> >> for a workaround that you can make to the "configure" script. >> >> Graham >> >> On 29/07/2006, at 4:56 PM, Vlad Dogaru wrote: >> >> > Hello, >> > >> > While running ./configure for mod_python 3.2.8 I get the following >> > errors: >> > >> > ./configure: line 3427: syntax error near unexpected token `(' >> > ./configure: line 3427: ` as_lineno_3=`(expr $as_lineno_1 + 1) 2>/ >> > dev/null`' >> > >> > I don't know bash very well and cannot find the syntax error. Is >> > there something I am missing? >> > >> > Thanks, >> > -Vlad >> > _______________________________________________ >> > Mod_python mailing list >> > Mod_python at modpython.org >> > http://mailman.modpython.org/mailman/listinfo/mod_python >> >>
|