Hi,
On Thu, Feb 22, 2018 at 08:42:51PM +0100, Sander Maijers
wrote:
> I must say autogen.sh being a Perl script surprised, even dismayed me.
Look at the git history of the file
(1e5339ec9209a5c89851f79adb1c49f169b6d3e5), especially the part that
reads arguments from autogen.input and (currently
Perl is great.
--tml
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
I must say autogen.sh being a Perl script surprised, even dismayed me.
Problems suchs as the one you describe are only to be expected when
bolting on Perl for this purpose.
Have any arguments been made against getting rid of Perl, in this instance?
On 22-02-18 19:29, Jan-Marek Glogowski wrot
Am 22.02.2018 um 18:36 schrieb Sander Maijers:
> Note that checkbashisms 2.17.12-1 failed to catch this when I debugged
> this issue.
>
> https://www.archlinux.org/packages/community/any/checkbashisms/
>
> Also note that on Arch Linux, I used dash 0.5.9.1-1, whereas Debian only
> has various olde
Thanks!
Note that checkbashisms 2.17.12-1 failed to catch this when I debugged
this issue.
https://www.archlinux.org/packages/community/any/checkbashisms/
Also note that on Arch Linux, I used dash 0.5.9.1-1, whereas Debian only
has various older versions
https://packages.debian.org/search?
Hi Sander,
On Wednesday, 2018-02-21 14:03:49 +0100, Sander Maijers wrote:
> I have set dash as /bin/sh.
"Funny", because Debian has dash there as well and no problem.
Anyway.. this
> ./configure fails due a syntax error, since `${PRODUCTNAME// /}` not a
> portable syntax.
has been changed to
Linux Host 4.15.3-2-ARCH #1 SMP PREEMPT Thu Feb 15 00:13:49 UTC 2018
x86_64 GNU/Linux
LSB_VERSION=1.4
DISTRIB_ID=Arch
DISTRIB_RELEASE=rolling
DISTRIB_DESCRIPTION="Arch Linux"
Build script:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=libreoffice-slim-git
I have set dash as /bin/sh.
On what OS is this? If Linux, what distro? Debian has dash as /bin/sh, but
there are plenty of people building LibreOffice on Debian that haven't
reported this issue. What configuration parameters do pass to autogen.sh
(or ./configure)? Is this related to what PRODUCTNAME_WITHOUT_SPACES ends
up con
