unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Van Ly <van.ly@sdf.org>
Cc: luangruo@yahoo.com, 64698@debbugs.gnu.org
Subject: bug#64698: 29.0.92; on netbsd 9.3, gmake and "gmake bootstrap" fail to proceed
Date: Wed, 19 Jul 2023 14:01:54 -0700	[thread overview]
Message-ID: <abd4dbe8-13f9-6faa-fdbd-cc5108c55c2c@cs.ucla.edu> (raw)
In-Reply-To: <837cqw5bho.fsf@gnu.org>

On 2023-07-19 05:31, Eli Zaretskii wrote:
> Paul, any ideas?  Do we just condition that by ESTRPIPE being defined?

The right way to do it would be to look at the NetBSD source code and 
see how their ALSA libraries deal with the situation. Whoever's 
reporting the problem would be in a better position to investigate this.

In the meantime, conditioning it as you suggest will get Emacs to 
compile (albeit there may be problems if that unusual situation occurs).





  reply	other threads:[~2023-07-19 21:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18  9:31 bug#64698: 29.0.92; on netbsd 9.3, gmake and "gmake bootstrap" fail to proceed Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 10:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 11:35   ` Eli Zaretskii
2023-07-19  3:10     ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-19 12:31       ` Eli Zaretskii
2023-07-19 21:01         ` Paul Eggert [this message]
2023-07-20  4:47           ` Eli Zaretskii
2023-07-20 10:13             ` Valtteri Vuorikoski
2023-07-20 16:12               ` Eli Zaretskii
2023-07-21 10:13                 ` Valtteri Vuorikoski
2023-07-21 11:03                   ` Eli Zaretskii
2023-07-21 12:12                     ` Valtteri Vuorikoski
2023-07-21 12:45                       ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-22 17:08                     ` Valtteri Vuorikoski
2023-07-26 14:05                       ` Eli Zaretskii

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=abd4dbe8-13f9-6faa-fdbd-cc5108c55c2c@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=64698@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=van.ly@sdf.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).