From: jf84ut@tutamail.com
To: Alsa Devel <alsa-devel@alsa-project.org>
Subject: Problems compiling alsa-utils
Date: Mon, 11 May 2026 00:19:59 +0200 (CEST) [thread overview]
Message-ID: <OsIyOGC--F-9@tutamail.com> (raw)
<html><body><pre>
Dear friends at alsa-project.org,
Thank you for your excellent software. I've been using linux
almost from its beginning. I'm an M.I.T. graduate and professional
computer programmer. I'm having difficulty compiling alsa-utils.
I'm using
- Debian 13.4.0 linux
- gcc 14.2.0
- aclocal 1.17
- gettextize 0.23.1
- autoheader 2.72
- automake 1.17
- autoconf 2.72
- GNU make 4.4.1
I've tried to compile the versions of alsa-utils both from github.com,
and from alsa-project.org .
/-- The procedure that I'm trying, suggested from
https://github.com/alsa-project/alsa-utils/blob/master/INSTALL, is,
cd /usr/src/alsa-utils
cp /usr/share/libtool/build-aux/config.guess .
cp /usr/share/libtool/build-aux/config.sub .
aclocal
gettextize
autoheader
automake --foreign --copy --add-missing
autoconf
./configure
make
\--
Are these the correct config.guess and config.sub that I should
use? Am I running the configuration / compilation commands in the
correct order?
Do you recommend using source code from alsa-project.org, or from
github.com?
After I've figured out how to compile this software, I'd be pleased to make
for you a web page, "How to Compile alsa-utils", that tells exactly how alsa-utils
can be compiled, and that you could put on your web site.
By the way, the link on your site to alsa-compile.sh, "script to
compile latest ALSA sources in an easy way," points to a non-existent
file. I'd be glad to help you with this, as well.
I thank you kindly for your help.
Very truly yours,
Lyman Opie
lyman@alum.mit.edu
</pre></body></html>
reply other threads:[~2026-05-11 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=OsIyOGC--F-9@tutamail.com \
--to=jf84ut@tutamail.com \
--cc=alsa-devel@alsa-project.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.
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.