Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.1.4, 3.2.7
    • Fix Version/s: 3.2.10, 3.3.1
    • Component/s: core
    • Labels:
      None
    • Environment:
      Any platform using bash 3.1.x

      Description

      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 '"'`

        Attachments

          Activity

            People

            • Assignee:
              jgallacher Jim Gallacher
              Reporter:
              jgallacher Jim Gallacher
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: