From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: Library versioning issues. Date: Wed, 10 Feb 2010 08:34:42 +0100 Message-ID: <20100210073442.GH2777@one.firstfloor.org> References: <20100209214830.GA23942@pendragon.3leafnetworks.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20100209214830.GA23942@pendragon.3leafnetworks.com> Sender: linux-numa-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Scott Lurndal Cc: linux-numa@vger.kernel.org On Tue, Feb 09, 2010 at 01:48:30PM -0800, Scott Lurndal wrote: > > Hi, > > I've a third-party application that's designed to be NUMA aware when > running on a NUMA system, but since this application also runs on non-NUMA > systems and a wide variety of operating systems, they don't link the > application directly with the libnuma shared object. Instead, they use > dlopen() to open the library at run-time, if it exists. I think you really need to ask this question the dlopen() developers. I don't think it's a problem that should be somehow kludged around in libnuma. Simply dlsym() et.al. need a way to specify the expected version. Otherwise it's a don't do that if it hurts(tm). -Andi