All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Jos Hulzink <josh@stack.nl>
Cc: alsa-devel@alsa-project.org
Subject: Re: XMMS ALSA extension problems
Date: Fri, 15 Feb 2002 09:34:56 -0500	[thread overview]
Message-ID: <20020215143456.GF13853@jesus> (raw)
In-Reply-To: <20020215142830.ZLJO1211.amsfep11-int.chello.nl@there>

On Fri, 15 Feb 2002, Jos Hulzink wrote:

> Hi,
> 
> The xmms ALSA extension doesn't work. It returns errors in the ALSA lib:
> 
> ALSA lib dlmisc.c:97:(snd_dlsym_verify) unable to verify version for symbol 
> snd_config_hook_load
> ALSA lib conf.c:2285:(snd_config_hooks_call) symbol snd_config_hook_load is 
> not defined inside (null)
> ALSA lib conf.c:2671:(snd_config_update) hooks failed, removing configuration
> xmms: pcm_params.c:2084: snd_pcm_hw_refine: Assertion `pcm && params' failed.
> Aborted
> 
> Can anybody tell if this is a problem in the ALSA lib, or is it the XMMS 
> plugin that causes this problem ?

both really. as i understand it alsa-lib uses dlopen(3) to resolve some
of its internal symbols. these are not properly resolved if the xmms
plugin isn't loaded RTLD_GLOBAL. you need to get xmms to open the alsa
plugin RTLD_GLOBAL for it to work.

regards,

wingo.

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

  reply	other threads:[~2002-02-15 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 10:20 2.5.5-pre1: Deadlocks and ALSA driver problems Jos Hulzink
2002-02-15 12:12 ` Jaroslav Kysela
2002-02-15 12:53   ` Jos Hulzink
2002-02-15 12:53     ` Jos Hulzink
2002-02-15 14:28   ` XMMS ALSA extension problems Jos Hulzink
2002-02-15 14:34     ` Andy Wingo [this message]
2002-02-15 14:42       ` Jos Hulzink

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=20020215143456.GF13853@jesus \
    --to=wingo@pobox.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=josh@stack.nl \
    /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.