From: Eli Zaretskii <eliz@gnu.org>
To: Bruno Haible <bruno@clisp.org>
Cc: 65323@debbugs.gnu.org
Subject: bug#65323: build failure on Alpine Linux
Date: Thu, 17 Aug 2023 08:44:36 +0300 [thread overview]
Message-ID: <83fs4i6x4r.fsf@gnu.org> (raw)
In-Reply-To: <6532976.9BJzLoJf6C@nimes> (message from Bruno Haible on Thu, 17 Aug 2023 00:59:52 +0200)
> 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 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.
I can only help with something that is obvious:
. The following command will find all references to Awk in the
configure script:
fgrep -wi awk configure
. The following command, if invoked from the top-level directory of
the Emacs source tree, will find several Makefile's in the Emacs
tree which invoke Awk as part of the build process:
fgrep -wiR awk . --include="Makefile.in"
Typically, the couple of directories whose Makefile.in invokes Awk
also have Awk scripts in them.
Not sure if the above is at all relevant, since the error message you
quoted comes from the build-aux/make-info-dir script, so maybe you
should ignore everything I wrote above, and look just at that script
and the Awk commands it runs. (It's a poor-man's install-info.)
HTH
next prev parent reply other threads:[~2023-08-17 5:44 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 [this message]
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
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=83fs4i6x4r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65323@debbugs.gnu.org \
--cc=bruno@clisp.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 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).