Re: Non-portable configure.ac

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 wrote:
> 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 older versions
> >
> > https://packages.debian.org/search?keywords=dash
> >
> > Running shellcheck and checkbashisms regularly is advisable even for
> > autoconf generated scripts.
> On my Ubuntu I also have sh -> dash. But I guess, like most people, I
> use autogen.sh to run configure with flags from autogen.input.
>
> And autogen.sh is really a Perl script, and Perls system call runs
> configure by calling "bash ./configure …". That's probably why nobody
> caught this yet. Now I have no idea why Perls system function uses bash
> as shell…
>
> Jan-Marek