From: Jonas Petersen <jnsptrsn1@gmail.com>
To: tiwai@suse.de
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Takashi: please help (compiling alsa-driver)
Date: Tue, 12 Feb 2013 22:58:37 +0100 [thread overview]
Message-ID: <511ABB0D.90808@gmail.com> (raw)
Hi Takashi,
I'm talking to you directly because this
ftp://ftp.suse.com/pub/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
is the only alsa-driver source that I'm able to compile so far. I can unpack this and simply run ./configure && make && make install. It works great. (I compile against the kernel-headers from ubuntu).
I spent hours in trying to compile from several other sources.
* The plain1.0.25 release (complains about missing symbols).
* The snapshots fromhttp://www.alsa-project.org/snapshot/ (will complain about missing 'uapi' stuff)
* Btw. where did the snapshots fromhttp://ftp.kernel.org/pub/linux/kernel/people/tiwai/alsa/ go (Advertised here:http://www.alsa-project.org/main/index.php/Download)?
* Checked out alsa-driver from git. But no luck, tried many things. e.g.: Branch release, then autoconf, but not even ./configure succeeds.
Id like to submit some patches and be able to work with the current state from git. How is that supposed to work?
Btw. I often read that the alsa-kernel is needed to compile. But it is not neede with this above mentioned 'unstable-snapshot'. It will just compile against the ubuntu kernel-headers (Lubuntu 12.10).
How do you generate these snapshots?
Thanks and sorry if that's stupid questions..
Jonas
next reply other threads:[~2013-02-12 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 21:58 Jonas Petersen [this message]
2013-02-13 0:31 ` Takashi: please help (compiling alsa-driver) Raymond Yau
2013-02-13 6:53 ` Takashi Iwai
2013-02-14 3:20 ` Raymond Yau
2013-02-14 7:16 ` Takashi Iwai
2013-02-13 6:51 ` Takashi Iwai
2013-02-15 18:37 ` Jonas Petersen
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=511ABB0D.90808@gmail.com \
--to=jnsptrsn1@gmail.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 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.