You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mod_python-dev@quetz.apache.org by "Graham Dumpleton (JIRA)" <ji...@apache.org> on 2006/02/07 23:17:59 UTC

[jira] Commented: (MODPYTHON-122) configure fails when using bash 3.1.x

    [ http://issues.apache.org/jira/browse/MODPYTHON-122?page=comments#action_12365490 ] 

Graham Dumpleton commented on MODPYTHON-122:
--------------------------------------------

Or as someone else suggested, maybe:

  MP_VERSION=`echo $MP_VERSION | sed 's/"//g'`

or:

  MP_VERSION=`echo $MP_VERSION | sed 's/["]//g'`

The single quotes should be enough to protect it without needing a slash.


> configure fails when using bash 3.1.x
> -------------------------------------
>
>          Key: MODPYTHON-122
>          URL: http://issues.apache.org/jira/browse/MODPYTHON-122
>      Project: mod_python
>         Type: Bug
>   Components: core
>     Versions: 3.2, 3.1.4
>  Environment: Any platform using bash 3.1.x
>     Reporter: Jim Gallacher
>     Assignee: Jim Gallacher
>     Priority: Minor

>
> A bug in bash 3.1 causes configure to fail. This has been reported on recent versions of Gentoo and and discussed on the mod_python mailing list:
> http://bugs.gentoo.org/show_bug.cgi?id=118948
> http://www.modpython.org/pipermail/mod_python/2006-January/019965.html
> http://www.modpython.org/pipermail/mod_python/2006-January/019969.html
> According to the gentoo bug report, the problem in configure.in is the double backslash escape sequence in the line:
> MP_VERSION=`echo $MP_VERSION | sed s/\\"//g`
> Changing this to:
> MP_VERSION=`echo $MP_VERSION | sed s/\"//g`
> fixes it for bash 3.1.
> I wonder why mod_python is using \\" since the gentoo fix seems to work ok with bash 3.0 (and GNU sed) just as well. Is it there to support other shells, other sed versions, older bash versions... ??
> I suggest mod_python adopts the gentoo fix, or avoids the problem altogether by using tr. eg.
> MP_VERSION=`echo $MP_VERSION | tr -d '"'` 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira