From: Juergen Kreileder Subject: Re: alsalib symbol problem Date: Tue, 17 Sep 2002 16:46:50 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <87vg54ekrp.fsf@zaphod.blackdown.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: (Paul Davis's message of "Tue, 17 Sep 2002 10:22:42 -0400") Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Paul Davis Cc: Tim Goetze , Florian Bomers , alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org Paul Davis 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). 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