From: Eli Zaretskii <eliz@gnu.org>
To: Valtteri Vuorikoski <vuori@notcom.org>
Cc: luangruo@yahoo.com, van.ly@sdf.org, eggert@cs.ucla.edu,
64698-done@debbugs.gnu.org
Subject: bug#64698: 29.0.92; on netbsd 9.3, gmake and "gmake bootstrap" fail to proceed
Date: Wed, 26 Jul 2023 17:05:54 +0300 [thread overview]
Message-ID: <83jzumoji5.fsf@gnu.org> (raw)
In-Reply-To: <x4pmyfbxh4ucs63w4sadpwao4jdpcilqbwoktggrf4pxynkqid@oqmd2qdrabai> (message from Valtteri Vuorikoski on Sat, 22 Jul 2023 20:08:42 +0300)
> Date: Sat, 22 Jul 2023 20:08:42 +0300
> From: Valtteri Vuorikoski <vuori@notcom.org>
> Cc: eggert@cs.ucla.edu, van.ly@sdf.org, luangruo@yahoo.com,
> 64698@debbugs.gnu.org
>
> Based on an investigation of source trees, libossaudio exists on
> NetBSD and OpenBSD. Comments (diff below) have been updated to reflect
> this. FreeBSD (going back from current to 4.x) and DragonflyBSD (from
> current to 1.2) don't have it.
>
> configure.ac --with-sound=yes cannot have picked bsd-ossaudio if
> -lossaudio is not found, so this change should not have any effect on
> FreeBSD/DragonflyBSD: LIBSOUND has always ended up empty on those and
> hence the LIBSOUND=-lossaudio test will always fail.
>
> Meanwhile OpenBSD appears to have behaved the same as NetBSD: use ALSA
> if it exists, otherwise ossaudio. OpenBSD binary packages seem to be
> built with --without-sound
> (https://github.com/openbsd/ports/blob/master/editors/emacs/Makefile)
> so this change won't affect their package builds in any case.
>
> Updated diff (comment update only):
Thanks, installed on the master branch, and closing the bug.
> > This should probably be mentioned in NEWS, then.
>
> How about this for a NEWS entry:
Thanks, I used it with a few minor changes.
prev parent reply other threads:[~2023-07-26 14:05 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
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 [this message]
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=83jzumoji5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64698-done@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=luangruo@yahoo.com \
--cc=van.ly@sdf.org \
--cc=vuori@notcom.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).