unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 65323@debbugs.gnu.org, bruno@clisp.org
Subject: bug#65323: build failure on Alpine Linux
Date: Thu, 17 Aug 2023 13:00:28 +0300	[thread overview]
Message-ID: <83pm3m56pv.fsf@gnu.org> (raw)
In-Reply-To: <87a5uq58vd.fsf@gmail.com> (message from Robert Pluim on Thu, 17 Aug 2023 11:13:58 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Bruno Haible <bruno@clisp.org>,  65323@debbugs.gnu.org
> Date: Thu, 17 Aug 2023 11:13:58 +0200
> 
> >>>>> On Thu, 17 Aug 2023 08:44:36 +0300, Eli Zaretskii <eliz@gnu.org> said:
> 
>     >> From: Bruno Haible <bruno@clisp.org>
>     >> Cc: 65323@debbugs.gnu.org
>     >> Date: Thu, 17 Aug 2023 00:59:52 +0200
>     >> 
>     >> Eli Zaretskii wrote:
>     >> 
>     >> > Are we using some feature that is not standard in Awk?
>     >> 
> 
> I think busyboxʼs awk is being more strict about regexp interval
> expressions than eg gawk.
> 
>     Eli> Not sure if the above is at all relevant, since the error message you
>     Eli> quoted comes from the build-aux/make-info-dir script, so maybe you
>     Eli> should ignore everything I wrote above, and look just at that script
>     Eli> and the Awk commands it runs.  (It's a poor-man's install-info.)
> 
> The following works for both gawk 5.2.1 and busybox awk 1.37.

Thanks, please install this on master.





  reply	other threads:[~2023-08-17 10:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 21:54 bug#65323: build failure on Alpine Linux Bruno Haible
2023-08-16 11:51 ` Eli Zaretskii
2023-08-16 14:11   ` Robert Pluim
2023-08-16 22:59   ` Bruno Haible
2023-08-17  5:44     ` Eli Zaretskii
2023-08-17  9:13       ` Robert Pluim
2023-08-17 10:00         ` Eli Zaretskii [this message]
2023-08-17 13:51           ` Robert Pluim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pm3m56pv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65323@debbugs.gnu.org \
    --cc=bruno@clisp.org \
    --cc=rpluim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).