From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Disagreement about versions following CVS update
Date: Fri, 19 Aug 2005 15:11:39 -0600 [thread overview]
Message-ID: <43064B0B.9080402@redfish-solutions.com> (raw)
In-Reply-To: <1124483804.25424.50.camel@mindpipe>
Lee Revell wrote:
>On Fri, 2005-08-19 at 13:33 -0600, Philip Prindeville wrote:
>
>
>>Stupid question: did a version number get changed somewhere? And if
>>so, what's the fix? I did a:
>>
>>% make -C alsa-driver clean
>>
>>and a rebuild, but I'm still seeing these. What did I miss?
>>
>>
>
>Your kernel sources probably do not match the running kernel.
>
>Lee
>
>
>
No, that's not the issue:
[root@media alsa]# make
...
checking for kernel version... 2.6.12-1.1372_FC3
...
checking for directory to store kernel modules...
/lib/modules/2.6.12-1.1372_FC3/kernel/sound
...
make -C /lib/modules/2.6.12-1.1372_FC3/source
SUBDIRS=/root/Downloads/alsa/alsa-driver
O=/lib/modules/2.6.12-1.1372_FC3/build modules
...
install: cannot create regular file `/sbin/init.d/alsasound': No such
file or directory
...
ALSA modules were successfully compiled.
...
/sbin/depmod -a -F /lib/modules/2.6.12-1.1372_FC3/source/System.map
2.6.12-1.1372_FC3
...
[root@media alsa]# uname -a
Linux media 2.6.12-1.1372_FC3 #1 Fri Jul 15 00:55:23 EDT 2005 x86_64
x86_64 x86_64 GNU/Linux
[root@media alsa]#
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-19 21:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 19:33 Disagreement about versions following CVS update Philip Prindeville
2005-08-19 20:36 ` Lee Revell
2005-08-19 21:11 ` Philip Prindeville [this message]
2005-08-19 21:14 ` Lee Revell
2005-08-19 22:17 ` Philip Prindeville
2005-08-19 22:25 ` Lee Revell
2005-08-19 23:20 ` Philip Prindeville
2005-08-19 23:28 ` Lee Revell
2005-08-19 23:43 ` Philip Prindeville
2005-08-19 23:47 ` Lee Revell
2005-08-19 23:53 ` Philip Prindeville
2005-08-19 23:56 ` Lee Revell
2005-08-20 0:06 ` Philip Prindeville
2005-08-22 12:12 ` Takashi Iwai
2005-08-22 16:30 ` Philip Prindeville
2005-08-22 16:33 ` Takashi Iwai
2005-08-20 7:17 ` Raymond
2005-08-20 21:06 ` Lee Revell
2005-08-21 0:55 ` Raymond
2005-08-22 12:09 ` Takashi Iwai
2005-08-22 15:13 ` Raymond
2005-08-22 15:29 ` Takashi Iwai
2005-08-22 12:14 ` Takashi Iwai
2005-08-22 16:27 ` Philip Prindeville
2005-08-22 16:29 ` 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=43064B0B.9080402@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.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.