From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VJmZn-0002nw-6J for qemu-devel@nongnu.org; Wed, 11 Sep 2013 11:43:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VJmZd-00023S-BO for qemu-devel@nongnu.org; Wed, 11 Sep 2013 11:43:31 -0400 Received: from mail-pd0-x236.google.com ([2607:f8b0:400e:c02::236]:62581) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VJmZd-00022d-3m for qemu-devel@nongnu.org; Wed, 11 Sep 2013 11:43:21 -0400 Received: by mail-pd0-f182.google.com with SMTP id r10so9406555pdi.27 for ; Wed, 11 Sep 2013 08:43:20 -0700 (PDT) Sender: Richard Henderson Message-ID: <52308F94.7060208@twiddle.net> Date: Wed, 11 Sep 2013 08:43:16 -0700 From: Richard Henderson MIME-Version: 1.0 References: <1378877909-28518-1-git-send-email-famz@redhat.com> <1378877909-28518-5-git-send-email-famz@redhat.com> <523086EC.1020103@twiddle.net> <66D9B8AB43C372ACE8E41913@Ximines.local> In-Reply-To: <66D9B8AB43C372ACE8E41913@Ximines.local> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v5 4/6] module: implement module loading function List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Bligh Cc: peter.maydell@linaro.org, Fam Zheng , mjt@tls.msk.ru, qemu-devel@nongnu.org, stefanha@redhat.com, pbonzini@redhat.com, vilanova@ac.upc.edu On 09/11/2013 08:23 AM, Alex Bligh wrote: >> But it does suggest the default being DT_RUNPATH, overridable "near" >> the command-line via LD_RUN_PATH. > > Not quite sure what you are suggesting here. DT_RUNPATH is an elf > tag IIRC. Not sure what LD_RUN_PATH does. LD_LIBRARY_PATH affects > more than just this. LD_RUN_PATH was my thinko -- LD_LIBRARY_PATH was what I was thinking. And while it does affect more than this, if set specifically for the qemu executable e.g. by a script then it need not really affect much. > If we are using the dynamic linker and DT_RUNPATH (which I believe > is in the executable) or the normal paths we WILL NEED proper API > versioning etc.; in this case (in the distro example I pulled out), > an upgrade to qemu making an API change will have different API > versioned libs and these can happily coexist, so no need for directories. I don't believe I ever suggested we're stable, or should even pretend to be so at this point. Install multiple qemu to different trees, and use different paths. Or even use the $ORIGIN prefix, which allows paths relative to the main executable, allowing the installed qemu tree to be moved at its root. r~