View previous topic :: View next topic |
Author |
Message |
Darthanubis Tux's lil' helper
Joined: 18 Oct 2002 Posts: 77
|
Posted: Tue Feb 18, 2003 3:09 am Post subject: Life after ALSA-how to needed< |
|
|
I compiled my whole system running Flux and KDE 3.1 with ALSA support. I have since removed ALSA, now all kinds of problems. Mainly with builds looking for libasound, and strings like this:
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lasound
How can I make my system ALSA free for good? Because the way it stands I can't install Gnome 2.2.
This also makes me wonder, If I have say kde or gnome in USE and I ever want to go back to a non-KDE/Gnome/ALSA env.
Will I have to re-compile my whole system?
Example of ebuild failure:
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lasound
collect2: ld returned 1 exit status
make[2]: *** [lavrec] Error 1
make[2]: *** Waiting for unfinished jobs....
gcc -mcpu=i686 -march=i686 -O3 -march=i686 -Wall -Wunused -o lavvideo lavvideo.o
make[2]: Leaving directory `/var/tmp/portage/mjpegtools-1.6.0-r7/work/mjpegtools-1.6.0/lavtools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/mjpegtools-1.6.0-r7/work/mjpegtools-1.6.0'
make: *** [all] Error 2
!!! ERROR: media-video/mjpegtools-1.6.0-r7 failed.
!!! Function src_compile, Line 94, Exitcode 2
!!! (no error message)
In IRC I was told emerge -eup world, this is what I get, because I have some ~x86 apps but I don't have ~x86 in my make, thus my WHOLE system is mainly the stable tree.
emerge -eup world
These are the packages that I would merge, in order:
Calculating world dependencies /
!!! all ebuilds that could satisfy ">=sys-devel/binutils-2.13.90.0.18" have been masked.
!!! (dependency required by "sys-devel/gcc-3.2.2" [ebuild])
I have and use a portage overlay directory as well and don't understand why this is showing up. It seems like I'm in some weird dependency voodoo cycle. |
|
Back to top |
|
|
pilla Bodhisattva
Joined: 07 Aug 2002 Posts: 7729 Location: Underworld
|
Posted: Tue Feb 18, 2003 3:30 am Post subject: |
|
|
Have you tried adding -alsa to your USE flags? _________________ "I'm just very selective about the reality I choose to accept." -- Calvin |
|
Back to top |
|
|
Phreakazoid_ Tux's lil' helper
Joined: 11 Feb 2003 Posts: 76 Location: Sydney, Australia
|
Posted: Tue Feb 18, 2003 5:28 am Post subject: |
|
|
All I can think of is to find all programs that you compiled with ALSA support in them, and remerge them individually.
I'd imagine that would fix the problem. |
|
Back to top |
|
|
Darthanubis Tux's lil' helper
Joined: 18 Oct 2002 Posts: 77
|
Posted: Tue Feb 18, 2003 5:56 am Post subject: |
|
|
Bloody Bastard wrote: | Have you tried adding -alsa to your USE flags? |
Yes |
|
Back to top |
|
|
Darthanubis Tux's lil' helper
Joined: 18 Oct 2002 Posts: 77
|
Posted: Tue Feb 18, 2003 5:57 am Post subject: |
|
|
Phreakazoid_ wrote: | All I can think of is to find all programs that you compiled with ALSA support in them, and remerge them individually.
I'd imagine that would fix the problem. |
That is THE problem, |
|
Back to top |
|
|
sertsa n00b
Joined: 21 May 2002 Posts: 49 Location: High Desert
|
Posted: Tue Feb 18, 2003 6:15 am Post subject: |
|
|
Hmm ....
You were getting an error when using --update, try without. I'm probably not really the one to ask but I believe emerge -e world should just rebuild everything you have at their current versions.
Code: | emerge -epv world | grep alsa |
I believe shows all ebuilds currently installed that are affected by the alsa flag. Could be wrong though. Although this might not necesarily mean all that are linked against alsa. It should be a good starting point. |
|
Back to top |
|
|
|