Gavin Smith wrote:
> AC_PATH_PROGS_FEATURE_CHECK does the job
Nice one; thanks for the lesson.
> although it is slightly complicated to use:
>
> AC_CACHE_CHECK([for awk], [ac_cv_path_TI_AWK],
> [AC_PATH_PROGS_FEATURE_CHECK([TI_AWK], [awk gawk mawk nawk],
> [[$ac_path_TI_AWK 'function
On Mon, Oct 24, 2022 at 08:19:50PM +0200, Bruno Haible wrote:
> does not help here, because nawk and mawk don't implement it. But what
> works, is a test whether $prog supports the function syntax: On this
> platform,
>
> gawk 'function foo () {}' 2>/dev/null
> nawk 'function foo () {}'
Eli Zaretskii wrote:
> > On the system that Bruno was testing, "awk" didn't work so "nawk" was
> > preferred.
>
> So maybe we should verify that the "awk": we found satisfies our
> needs, and not just rely on the name?
Yes, that would be most in line with the Autoconf principles.
> E.g., we
On Mon, Oct 24, 2022 at 06:40:53PM +0300, Eli Zaretskii wrote:
> Why not prefer Gawk if it's installed?
It makes running texi2pdf a little faster.
$ ls -l --si texinfo.??
-rw-rw-r-- 1 g g 94k Oct 24 17:51 texinfo.cp
-rw-rw-r-- 1 g g 21k Oct 24 17:51 texinfo.fn
$ time TEXINDEX_AWK=/usr/bin/gawk
> From: Gavin Smith
> Date: Mon, 24 Oct 2022 18:01:21 +0100
> Cc: br...@clisp.org, bug-texinfo@gnu.org
>
> On Mon, Oct 24, 2022 at 06:40:53PM +0300, Eli Zaretskii wrote:
> > Why not prefer Gawk if it's installed?
>
> It makes running texi2pdf a little faster.
>
> $ ls -l --si texinfo.??
>
> From: Gavin Smith
> Date: Mon, 24 Oct 2022 15:00:53 +0100
> Cc: br...@clisp.org, bug-texinfo@gnu.org
>
> > But why should configure try nawk first? I think it should try awk
> > first, because on system where Gawk is installed, it installs itself
> > as awk as well.
> >
>
> On the system
On Mon, Oct 24, 2022 at 04:22:04PM +0300, Eli Zaretskii wrote:
> > From: Gavin Smith
> > Date: Sun, 23 Oct 2022 19:54:20 +0100
> > Cc: bug-texinfo@gnu.org
> >
> > On Sun, Oct 23, 2022 at 08:36:04PM +0200, Bruno Haible wrote:
> > > Therefore, on this platform, instead of picking the 'awk' that is
> From: Gavin Smith
> Date: Sun, 23 Oct 2022 19:54:20 +0100
> Cc: bug-texinfo@gnu.org
>
> On Sun, Oct 23, 2022 at 08:36:04PM +0200, Bruno Haible wrote:
> > Therefore, on this platform, instead of picking the 'awk' that is found
> > in $PATH, it is a better strategy to look for 'nawk' or 'gawk'
On Sun, Oct 23, 2022 at 04:59:46PM +0200, Bruno Haible wrote:
> Once the compilation error is fixed, "gmake check" fails:
>
> FAIL: tests/ti-helpversion.sh
>
> Find attached the log.
>
> On this platform, awk is /usr/bin/awk. Not GNU awk. If 'texindex' works only
> with GNU awk, it ought to
On Sun, Oct 23, 2022 at 08:36:04PM +0200, Bruno Haible wrote:
> Therefore, on this platform, instead of picking the 'awk' that is found
> in $PATH, it is a better strategy to look for 'nawk' or 'gawk' in $PATH.
Thanks for investigating this. I've made it try nawk as well:
diff --git
Gavin Smith wrote:
> It is not supposed to only run on GNU awk. In fact, it should prefer
> awk to gawk. I prefer not to run texindex with gawk because mawk is
> much faster.
OK.
> Do you have any idea why awk is saying there is a syntax error?
>
> awk: syntax error near line 1
> awk: bailing
11 matches
Mail list logo