unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Valtteri Vuorikoski <vuori@notcom.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, van.ly@sdf.org, eggert@cs.ucla.edu,
	64698@debbugs.gnu.org
Subject: bug#64698: 29.0.92; on netbsd 9.3, gmake and "gmake bootstrap" fail to proceed
Date: Fri, 21 Jul 2023 13:13:36 +0300	[thread overview]
Message-ID: <zut7o3ucwyodd4yzttitmbcxno6gqwvoj67347oojjolh73og3@53g3jn4dsk2m> (raw)
In-Reply-To: <83a5vq36kk.fsf@gnu.org>

On Thu, Jul 20, 2023 at 07:12:43PM +0300, Eli Zaretskii wrote:
> > Building emacs with sound enabled but alsa-lib _not_ installed seems
> > to work (= compiles and starts) by using the system OSS library. Since
> > Emacs's audio needs are modest, it may be better to use "bsd-ossaudio"
> > on NetBSD if --with-sound=yes. AFAICT "ALSA" on NetBSD is just a proxy
> > for the native audio system anyway.
> > 
> > The other option is to try and use ALSA if --with-sound=yes, but
> > #ifdef out the ESTRPIPE branch if ESTRPIPE is not defined.
> > 
> > Personally I'd go with the default-to-ossaudio option, since pulling in
> > alsa libraries introduces a pkgsrc dependency into the binary and doesn't
> > seem like it provides a lot of benefit. I'm not quite sure what's the
> > best way to convince configure.ac to act like this, but I can test
> > patches at least on a compiles/doesn't-compile level.
> 
> Thanks.  I went with the #ifdef approach on the release branch, since
> it's simpler and therefore safer.
> 
> Patches are welcome for preferring bsd-ossaudio on NetBSD.

If you want to apply it for -30, this basically implements the
suggestion that was already dnl'd in configure.ac. Emacs will end up
using ossaudio even if the alsa-lib pkgsrc package is installed.

--- a/configure.ac
+++ b/configure.ac
@@ -1797,8 +1797,10 @@ AC_DEFUN
     AC_CHECK_LIB([ossaudio], [_oss_ioctl], [LIBSOUND=-lossaudio], [LIBSOUND=])
     test "${with_sound}" = "bsd-ossaudio" && test -z "$LIBSOUND" && \
       AC_MSG_ERROR([bsd-ossaudio sound support requested but not found.])
-    dnl FIXME?  If we did find ossaudio, should we set with_sound=bsd-ossaudio?
-    dnl Traditionally, we go on to check for alsa too.  Does that make sense?
+    # On NetBSD use the system audio library instead of potentially switching
+    # to ALSA later on, as ALSA on NetBSD appears to just wrap OSS.
+    test "${with_sound}" = "yes" && test "$LIBSOUND" = "-lossaudio" && \
+      with_sound="bsd-ossaudio"
   fi
   AC_SUBST([LIBSOUND])

The emacs28 pkgsrc package doesn't set any sound-related configure
flags. I assume they're building binary packages on an alsa-free
system and have been happy with the result (= -lossaudio is used
because no alsa).

People who want alsa should be able to still get it with
--with-sound=alsa.

 - Valtteri
 





  reply	other threads:[~2023-07-21 10:13 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 [this message]
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=zut7o3ucwyodd4yzttitmbcxno6gqwvoj67347oojjolh73og3@53g3jn4dsk2m \
    --to=vuori@notcom.org \
    --cc=64698@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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).