Hello
When working on it, I found that:
AC_PATH_PROG(BASH, bash)
if test -z "$BASH"; then
AC_MSG_ERROR([bash not found in \$PATH])
fi
AC_SUBST(BASH)
and then,
$ git grep BASH
bin/bash-completion.in:@BASH_COMPLETION_SUFFIXES_CHECKS@
bin/bash-completion.in:@BASH_COMPLETION_OOO_APPS@
bin/generate-bash-completion: if ($line =~
m/\@BASH_COMPLETION_SUFFIXES_CHECKS\@/) {
bin/generate-bash-completion: } elsif ($line =~
m/\@BASH_COMPLETION_OOO_APPS\@/) {
config_host.mk.in:export OOO_SHELL=@BASH@
configure.ac:AC_PATH_PROG(BASH, bash)
configure.ac:if test -z "$BASH"; then
configure.ac:AC_SUBST(BASH)
and
$ git grep OOO_SHELL
config_host.mk.in:export OOO_SHELL=@BASH@
So, is it still useful or could we remove BASH check and OOO_SHELL as well
?
I'll wait for your reply before submitting.
--
Mat M
Le Thu, 21 Mar 2013 00:35:57 +0100, Mat M <m...@gmx.fr> a écrit:
Hello
am the culprit.
I did not check that arrays were not posix :-(
Since we have no spaces in vars and file names, it is simple to provide
a POSIX workaround still allowing us to use the for loops.
Will do that sometimes between tomorrow and next Sunday.
Sorry for the inconvenience.
Regards
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
