Re: [Qemu-devel] [RFC PATCH v5 4/6] module: implement module loading function

[Richard Henderson <rth@twiddle.net>]

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~