alsa-plugins emerge failure
On Fri, Apr 18, 2008 at 01:50:22PM +0200, Alan McKinnon wrote
> On Friday 18 April 2008, Walter Dnes wrote:
> > checking for ALSA... yes
> > checking for snd_pcm_ioplug_create in -lasound... no
> > configure: error: *** libasound has no external plugin SDK
> libasound comes from package alsa-lib. So, what's the output from these
> commands (assuming you have eix installed):
> eix alsa-lib
> eix alsa-plugins
> emerge --info
> I don't have alsa-plugins myself and have never needed it. Are you sure
> you need it?
Thanks for the pointer to eix. I did the spelunking you suggested,
and more. First item is that I re-emerged alsa-lib, and got the
* Messages for package media-libs/alsa-lib-1.0.16:
* You haven't selected _any_ PCM plugins. Either you set it to
* something like the default
* (which is being set in the profile UNLESS you unset them) or alsa
* based applications
* are going to *misbehave* !
Note that after running into some "helpful defaults" a few years ago
(*hack* *kaff* IPV6 *hack* *kaff*) I ended up inserting "-*" at the
beginning of my USE variable. I have quite a bit of stuff in the USE
variable, but it's there only because it provides features I want/need
or because an app I want/need complains about missing something. Is
this one of those cases? I should probably solve this first.
About alsa-plugins... is it required for MP3 or streaming MP3? If
not I'll consider unmerging it.
Walter Dnes <email@example.com>
Stop the Squeegee Kids in Pinstripe Suits
Fight SAC's Canadian internet tax http://walterdnes.wordpress.com
firstname.lastname@example.org mailing list