all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65323@debbugs.gnu.org
Subject: bug#65323: build failure on Alpine Linux
Date: Thu, 17 Aug 2023 00:59:52 +0200	[thread overview]
Message-ID: <6532976.9BJzLoJf6C@nimes> (raw)
In-Reply-To: <83r0o38atg.fsf@gnu.org>

Eli Zaretskii wrote:
> I think it goes without saying that every program invoked by the build
> must be "decent".

You are assuming more knowledge on my side than I actually had:

  * I've built many packages on Alpine Linux. None of these failed
    due to 'awk', as far as I remember. I know that configure
    scripts invoke 'awk', and this 'awk' program was always sufficient
    for configure's purposes.

  * I don't know which are the programs that are invoked by the Emacs
    build. I thought that all the utilities listed in
    https://www.gnu.org/prep/standards/html_node/Utilities-in-Makefiles.html
    — except for 'diff' — are good enough in Alpine Linux.

> Are we using some feature that is not standard in Awk?

I don't know, since I am not familiar with the Emacs build system. But if
you show me the Awk script(s) that the build executes, I might look whether
it only uses POSIX features [1] and, if so, report a bug to the Alpine
Linux people.

Bruno

[1] https://pubs.opengroup.org/onlinepubs/9699919799/utilities/awk.html








  parent reply	other threads:[~2023-08-16 22:59 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 [this message]
2023-08-17  5:44     ` Eli Zaretskii
2023-08-17  9:13       ` Robert Pluim
2023-08-17 10:00         ` Eli Zaretskii
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

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

  git send-email \
    --in-reply-to=6532976.9BJzLoJf6C@nimes \
    --to=bruno@clisp.org \
    --cc=65323@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.