Re: Proposed patch: configure version number checking

[Mats Bengtsson]

Please take a look a the mailing list archives for bug-lilypond
and lilypond-devel to see what kind of different situations that
the previous version number checks failed on, before proposing
yet another change.

  /Mats

Quoting Matthias Neeracher <address@hidden>:

> I hadn't tried to build 2.9.x in a while, and it seems that there was
>  a change to the version number checking that broke for some of the
> tools used in the fink build on MacOS X. e.g. we run guile-config as
> guile-1.6-config.
>
> The solution is to insist that the version number be at the beginning
>  of a line or after a space (a 1 character patch – does it get any
> more efficient than that?)
>
> Matthias
>
> diff -ruN lilypond-2.9.16-orig/aclocal.m4 lilypond-2.9.16/aclocal.m4
> --- lilypond-2.9.16-orig/aclocal.m4     2006-08-26 20:47:16.000000000  -0700
> +++ lilypond-2.9.16/aclocal.m4  2006-08-26 21:43:45.000000000 -0700
> @@ -34,7 +34,7 @@
>      ## grab the first version number in  --version output.
>      eval _ver=\"\`("$1" --version || "$1" -V) 2>&1 | grep '\(^\| \)
> [0-9][0-9]*\.[0-9]' \
>          | head -n 1 \
> -       | tr ' ' '\n' | grep '[0-9]\.[0-9]' | head -n 1 | sed 's/\
> ([0-9.]*\).*/\1/g'\`\"
> +       | tr ' ' '\n' | grep '^[0-9]\.[0-9]' | head -n 1 | sed 's/\
> ([0-9.]*\).*/\1/g'\`\"
>
>      if test -z "$_ver"; then
>          ## If empty, try date [fontforge]
>
>
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-devel