bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-12-03 Thread Mike Frysinger
On 02 Dec 2023 21:55, Paul Eggert wrote: > -if test -z "$PERL"; then > +case $PERL in AS_CASE ? -mike signature.asc Description: PGP signature

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-12-02 Thread Paul Eggert
On 2023-12-02 19:29, Zack Weinberg wrote: `grep -q` *is* in POSIX, but I seem to recall tripping over a system that didn't have it (probably either a Solaris successor, or AIX) during the run-up to Autoconf 2.71. Solaris 10 /usr/bin/grep does not support -e, -E, -f, -F, -q, or -x. Solaris 10

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-12-02 Thread Zack Weinberg
On Sat, Dec 2, 2023, at 9:08 PM, Mike Frysinger wrote: > On 02 Dec 2023 15:53, Karl Berry wrote: >> Exit status yes, but at least historically, grep -q has been >> considered non-portable, in favor of grep ... >/dev/null. > > i get that `grep -q` is something historically we've avoided, but i > thi

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-12-02 Thread Mike Frysinger
On 02 Dec 2023 15:53, Karl Berry wrote: > also, can we really not trust the exit status of grep ? > if echo "$PERL" | grep -q '[\t ]'; then > > Exit status yes, but at least historically, grep -q has been considered > non-portable, in favor of grep ... >/dev/null. i get that `grep

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-12-02 Thread Karl Berry
echo "$PERL" | grep '[ \t]' I don't think there's any portable way to use \t to insert a tab in a shell string, besides literally. There's something like tab=`printf '\t'` .. "$tab" ... but I don't see a need to go that far here. I just used a literal tab char. also, can we really not

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-12-02 Thread Mike Frysinger
On 27 May 2023 19:12, Karl Berry wrote: > I (finally) installed this patch to quit early if the perl path has > spaces. Thanks. > > As for MKDIR_P and INSTALL, I guess it is somewhere in the > prerequisite/autoconf stuff. I suppose it would be rare that they would > be found in a path with spaces

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-05-27 Thread Karl Berry
I (finally) installed this patch to quit early if the perl path has spaces. Thanks. As for MKDIR_P and INSTALL, I guess it is somewhere in the prerequisite/autoconf stuff. I suppose it would be rare that they would be found in a path with spaces while perl was not, so I think it's ok to let that g

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-04-23 Thread Karl Berry
But anyway, patch for the Perl path attached. Thanks. Your method seems as good as any to me. I thought about using 'grep -q' and checking the exit code, but maybe this version is more portable. Indeed, grep -q is not portable. It's necessary to >/dev/null instead. --thanks ag

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-04-23 Thread Bogdan
Karl Berry , Fri Apr 21 2023 23:57:12 GMT+0200 (Central European Summer Time) Thanks for the report, Dan, and for looking into this, Bogdan. #!User bins/perl Apart from anything else, this cannot be solved. Shebang lines do not support quoting. Thus I think what we should do is ha

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-04-21 Thread Karl Berry
Thanks for the report, Dan, and for looking into this, Bogdan. #!User bins/perl Apart from anything else, this cannot be solved. Shebang lines do not support quoting. Thus I think what we should do is have configure give a better error message when the Perl path contains whitespace,

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-04-21 Thread Bogdan
Hello. Thank you for the bug report. The problem is a bit more complicated, unfortunately. At least from my point of view. I did a bit of an analysis. The problem can be replicated on current master on a Linux - just do ln -s /usr/bin 'User bins' export PATH='User bins':$PAT

bug#62896: [Configure] Bug with check for PERL when path has spaces (i.e. Windows)

2023-04-16 Thread Dan Rosser
VER=1.16.4 Building "automake" checking whether make supports nested variables... no checking build system type... x86_64-pc-mingw64 checking host system type... x86_64-pc-mingw64 checking for a BSD-compatible install... ./lib/install-sh -c checking whether build environment is sane... yes checki