From: Lee Revell <rlrevell@joe-job.com>
To: tsw@johana.com
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Simple suggestion for a make target
Date: Tue, 13 Sep 2005 15:37:34 -0400 [thread overview]
Message-ID: <1126640254.13893.37.camel@mindpipe> (raw)
In-Reply-To: <20050913192422.73152.qmail@web60825.mail.yahoo.com>
On Tue, 2005-09-13 at 12:24 -0700, Tom Watson wrote:
> Since it appears that frequently the kernel source has older versions of alsa
> when released, wouldn't it be wise to have a target in the alsa-driver-xx.yy.z
> directory that finds the kernel sources, and updates them. Then one could
> re-compile the kernel and all would be well with the world.
>
> For those who don't wish to do this, the "./configure;make;make install"
> sequence would work as well.
>
> I suspect that the kernel configuration would pass thru, so one wouldn't need
> to configure before "transferring" sources, but not being an expert, I don't
> know.
>
> Maybe this would encourage distrubutions that diddle with the kernel source to
> have an up-to-date alsa.
What would be the point? It's already simpler than that.
Just ./configure && make && make install in alsa-driver directory to
install a newer ALSA. It just overwrites the old ALSA modules that came
with the kernel with the newer ones. You don't even need to reboot.
Lee
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next prev parent reply other threads:[~2005-09-13 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050913175247.9B2BD895B2@sc8-sf-spam1.sourceforge.net>
2005-09-13 19:24 ` Simple suggestion for a make target Tom Watson
2005-09-13 19:37 ` Lee Revell [this message]
2005-09-14 10:19 ` 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=1126640254.13893.37.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tsw@johana.com \
/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.