Summary: | emerge of of alsa-0.9 fails (referenced from kdemultimedia-3.0.1) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kevyn Shortell (RETIRED) <trance> |
Component: | Current packages | Assignee: | Dan Armak (RETIRED) <danarmak> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kain, kurisu, mguertin, trance |
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kevyn Shortell (RETIRED)
![]() http://www.moongroup.com/pipermail/lunar/2002-April/000409.html this seems to shed some light on the subject, maybe a simple patch would fix things up? included proposed workaround by gerk: Ok, if I untar kdemultimedia and change the two include statements for the alsa headers to; #include </usr/include/alsaasoundlib.h> make will complete without errors. For some reason just having #include <alsa/asoundlib.h> does not work but the full path does. So how would the BUILD be changed to delete these two include statements in /usr/src/kdemultimedia-2.2.2/kmidi/alsa_a.cpp and change them to "#include </usr/include/alsa/asoundlib.h>"? You don't mind if I take it? kdemm is my responsibility really. Um, I missed the ppc tag when I took the ebuild. But n/m that, because I know the solution :-) So, Gerk, I'm ccing you as my ppc liason :-) This is basically the same as the infamous bug #2324. In other words, kdemm does NOT support alsa 0.9* and cannot be made to link against it. And it's up to the kde devs to fix it, and I don't know when they will do that. The problem here is that the 3.0.1 ebuild doesn't explicitly disable alsa support. The newer 3.0.1.20020604 ebuild explicitly says, regardless of any use flags, myconf="$myconf --disable-alsa --without-alsa". And that should do it. I don't know how exactly x86/general ebuilds move into the ppc profile, but this newer ebuild (which otherwise only adds bugfixes) should fix the problem. Please try it. Sorry, my comment was misled by the topic that said 3.0.1. I now understand that this bug exists in 3.0.1.20020604 but NOT in 3.0.1. That's very odd because as I've said, the difference between 3.0.1 and 3.0.1.20020604 is that one line that disables alsa support (which is right). I'd like at the output of the ./configure section of emerge kdemultimedia, and at $T/eclass-debug.log (to see the parameters passed to configure). Dan: Sorry I am unable to test that, it works perfectly on this box, and the box where I had the problems died under the wrath of a kernel yesterday (filesystems completely toast). trance 9the bug reporter) can probably get you this stuff thogh, I'll work with him later on today and try and get you the info you need. Incidentily if you export USE="-alsa" and emerge it works ok. If that is so something is deeply wrong. Please read the ebuild, it does NOT depend on the alsa use flag in any way and is supopsed to always disable alsa support regardless of anything at all. Ok, it seems this was my fault all along :-( I've committed the correct ebuild, please update and try gain and this time it really should build correctly and without alsa support. *** Bug 3512 has been marked as a duplicate of this bug. *** Closing with both ppc and x86 confirmation from Gerk. |