Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] latest update makes alsa screwy!

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: "Eric Sandall" <eric AT sandall.us>
  • To: <sm-discuss AT lists.ibiblio.org>
  • Subject: Re: [SM-Discuss] latest update makes alsa screwy!
  • Date: Wed, 11 Sep 2002 06:22:15 -0700 (PDT)

alsa-driver already removes this file, though alsa-driver-virmidi does not
(will fix rn).

-One of Four
a.k.a. sandalle

Piero Ottuzzi said:
>
>
>
> From the alsa front page:
>
> " Note for compiling alsa-driver-0.9.0rc3: Please remove the file -
> alsa-driver-0.9.0rc3/include/linux/isapnp.h - before running the
> configure script. "
>
> More Info on www.alsa-project.org
>
> Apiero
>
> mercoledì 11 settembre 2002 13.29
> To: eric AT sandall.us, <sm-discuss AT lists.ibiblio.org>
> cc:
> Subject: Re: [SM-Discuss] latest update makes alsa screwy!
>
> On Monday 09 September 2002 06:43, Eric Sandall wrote:
>> Jeremy Kolb said:
>> > ok, just sorcery updated and now when i cast alsa-driver i get a
>> whole bunch of undefined symbols in my
>> > /lib/modules/2.4.19-preempt-3/kernel/sound/*.o files. then i go to
>> cast alsa-lib and it decides to uninstall alsa-driver and install
>> > alsa-driver-virmidi instead (which is at rc2 where as the rest of
>> the alsa spells are rc3). then it finally gets to compiling alsa-lib
>> and then dies because halfway through the /usr/src/alsa-lib-0.9-rc3
>> (something like that) directory mysteriously disappears. just posted
>> to bugzilla bug 919.
>> >
>> > Jeremy
>> >
>> > P.S. and what is the difference between alsa-driver and
>> > alsa-driver-virmidi? that should be clearly defined in the DETAILS
>> section, but i see no difference between the two. is this "better"
>> then the plane old alsa-driver?
>>
>> Are your linux modules installed into /lib/modules/2.4.19-preempt-3/,
>> or does the alsa-driver spell create that? If so, then I believe the
>> problem is that the alsa-driver spell is misreading the kernel version
>> of where to put it (it's set to go to /lib/modules/`installed_version
>> linux-new`/).
>>
>> And I have no idea what the difference is, though I've been asked a
>> few times already. :)
>>
>> -One of Four
>> a.k.a. sandalle
>
> I have got the same problem with the plain-vanilla linux kernel. After
> alsa updated I get the undefined symbols.
>
> The problem, IMHO, is that alsa keeps pace with the kernel releases. So
> eg. after 2.4.19-rc3, you also get a alsa-rc3.
>
> Now, we don't do kernel rc's (I hope), so we probably shold hold off on
> alsa updates until the next kernel release. I would suggest you revert
> to the previous alsa version.
>
> --
> Lyon Lemmens
> redlemon AT knoware.nl
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss


--
Eric Sandall | Source Mage GNU/Linux Developer
eric AT sandall.us | http://www.sourcemage.org
http://www.sandall.us/~sandalle | SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org #196285 | http://www.shock.wsu.edu/






Archive powered by MHonArc 2.6.24.

Top of Page