Hello!
With the current ‘libunistring’ Gnulib module, I’m observing [0] this
during the ‘configure’ run:
--8<---------------cut here---------------start------------->8---
./configure: line 20186: test: -lt: unary operator expected
./configure: line 20187: test: -eq: unary operator expected
./configure: line 20223: test: -lt: unary operator expected
./configure: line 20224: test: -eq: unary operator expected
[...]
--8<---------------cut here---------------end--------------->8---
stemming from these lines:
--8<---------------cut here---------------start------------->8---
test $LIBUNISTRING_VERSION_MAJOR -lt 0 \
|| { test $LIBUNISTRING_VERSION_MAJOR -eq 0 \
&& { test $LIBUNISTRING_VERSION_MINOR -lt 9 \
|| { test $LIBUNISTRING_VERSION_MINOR -eq 9 \
&& test $LIBUNISTRING_VERSION_SUBMINOR -lt 2
}
}
}
--8<---------------cut here---------------end--------------->8---
Before, ‘configure’ reported this:
--8<---------------cut here---------------start------------->8---
checking for libunistring... yes
checking how to link with libunistring... -lunistring
checking for libunistring version... 0.9.3
--8<---------------cut here---------------end--------------->8---
So, two problems here:
1. The tests above are underquoted, they should read:
test "$LIBUNISTRING_VERSION_MAJOR" -lt 0 \
...
2. The version-extraction sed scripts appear to be broken:
--8<---------------cut here---------------start------------->8---
$
gl_libunistring_sed_extract_subminor='/^[0-9][0-9]*[.][0-9][0-9]*[.][0-9]/{s/^[0-9]*[.][0-9]*[.]\([0-9]*\).*/\1/p;q;}
> i\
> 0
> q
> '
$ echo 0.9.3 | sed -n -e "$gl_libunistring_sed_extract_major"
$ sed --version
GNU sed version 4.1.5
--8<---------------cut here---------------end--------------->8---
Ideas?
Thanks,
Ludo’.
[0] http://hydra.nixos.org/build/429165/
