From: Florian Bomers <Florian.Bomers@sun.com>
To: alsa-devel@lists.sourceforge.net
Cc: Tim Goetze <tim@quitte.de>
Subject: Re: Re: alsalib symbol problem
Date: Tue, 17 Sep 2002 08:39:26 -0700 [thread overview]
Message-ID: <3D874CAE.DDA03E51@sun.com> (raw)
In-Reply-To: 87ptvcejnr.fsf@zaphod.blackdown.de
Thanks ! I guess Juergen's suggestion would be of general: a plugin should be
able to link to libasound with -lasound without the need that the plugin itself
is linked/dlopen()'ed with RTLD_GLOBAL. With increasing adoption of ALSA, we'll
see such a scenario more and more...
On the practical side - how can I solve the problem ? I can't change the way my
plugin is linked to the main app, so do I need to manually dlopen() libasound
myself with the RTLD_GLOBAL flag (and not use -lasound ??)
Thanks,
Florian
Juergen Kreileder wrote:
>
> Paul Davis <pbd@op.net> writes:
>
> >>Paul Davis <pbd@op.net> writes:
> >>
> >>> the problem is that libasound itself calls dlopen(), and the
> >>> initial (non-RTLD_GLOBAL) linkage hasn't put libasound's symbol
> >>> into the global namespace. hence, libasound's own dlopen'ed code
> >>> can't access libasound itself.
> >>
> >>I know, that's why I suggested to not do dlopen(NULL, ...) inside
> >>libasound (see the code from my previous mail).
> >
> > how does this help?
>
> You don't have to use RTLD_GLOBAL when dlopening libasound.so or
> libraries linked with libasound.so anymore.
>
> Juergen
>
> --
> Juergen Kreileder, Blackdown Java-Linux Team
> http://www.blackdown.org/java-linux/java2-status/
>
> -------------------------------------------------------
> Sponsored by: AMD - Your access to the experts on Hammer Technology!
> Open Source & Linux Developers, register now for the AMD Developer
> Symposium. Code: EX8664 http://www.developwithamd.com/developerlab
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
--
Florian Bomers
Java Sound
Java Software/Sun Microsystems, Inc.
http://java.sun.com/products/java-media/sound/
-------------------------------------------------------
Sponsored by: AMD - Your access to the experts on Hammer Technology!
Open Source & Linux Developers, register now for the AMD Developer
Symposium. Code: EX8664 http://www.developwithamd.com/developerlab
next prev parent reply other threads:[~2002-09-17 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17rJn3-0005Ec-00@zaphod.blackdown.de>
2002-09-17 15:10 ` alsalib symbol problem Juergen Kreileder
2002-09-17 15:39 ` Florian Bomers [this message]
2002-09-17 18:14 ` Tim Goetze
2002-09-17 18:21 ` Florian Bomers
2002-09-17 14:46 Juergen Kreileder
2002-09-17 14:59 ` Paul Davis
2002-09-17 15:17 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2002-09-17 13:35 Juergen Kreileder
2002-09-17 13:57 ` Paul Davis
2002-09-17 15:32 ` Jaroslav Kysela
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=3D874CAE.DDA03E51@sun.com \
--to=florian.bomers@sun.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tim@quitte.de \
/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.