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 <matm@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
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.