From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: alsa-driver build problem : no lola dir
Date: Tue, 07 Jun 2011 13:36:40 +1200 [thread overview]
Message-ID: <4DED80A8.5000502@audioscience.com> (raw)
(resend from address subscribed to alsa-devel)
Trying to build alsa-driver git fails:
make[2]: Leaving directory
`/home/eliot/src/alsagit/alsa-driver/pci/korg1212'
make: Entering an unknown directory
make: *** lola: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [prepare] Error 1
make[1]: Leaving directory `/home/eliot/src/alsagit/alsa-driver/pci'
make: *** [dep] Error 1
~/src/alsagit/alsa-driver$
my alsa-kernel links point to a current sound-2.6 git tree.
--
Eliot Blennerhassett
AudioScience Inc.
next reply other threads:[~2011-06-07 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 1:36 Eliot Blennerhassett [this message]
[not found] <4DED623A.3040606@audioscience.com>
2011-06-07 5:17 ` alsa-driver build problem : no lola dir Takashi Iwai
2011-06-07 20:40 ` Eliot Blennerhassett
2011-06-08 5:28 ` Takashi Iwai
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=4DED80A8.5000502@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).