Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ael <witwall3@disroot.org>
To: alsa-devel@alsa-project.org
Subject: Re: building aplay / arecord
Date: Wed, 2 Nov 2022 15:15:42 +0000	[thread overview]
Message-ID: <Y2KJntHXy19DEBck@shelf.conquest> (raw)
In-Reply-To: <CAG74igXPJjnQF6-nbXn2bXywWA0cKpR3cDhYPwg=fKN6J_yZZA@mail.gmail.com>

On Mon, Oct 31, 2022 at 06:04:26PM -0700, David Jaffe wrote:
> Newbie question...
> 
> I downloaded the alsa-utils source and it says to run ./configure.  But no
> such file exists.  And if I go to aplay and type “make aplay” it can’t find
> a file called “aconfig.h”, which is presumably written by
> ./configure.  What am I missing?

I think that you need to run autoconf on the configure.ac file which
you should have: it is there in the git directory.

Perhaps read 
 man autoconf ?

The INSTALL file does indeed say run ./configure without explaining that
you need autoconf if ./configure is not present.

ael


  parent reply	other threads:[~2022-11-02 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  1:04 building aplay / arecord David Jaffe
2022-11-02 14:29 ` Geraldo Nascimento
2022-11-02 15:15 ` ael [this message]
2022-11-02 21:52   ` aitor

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=Y2KJntHXy19DEBck@shelf.conquest \
    --to=witwall3@disroot.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox