From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Slater, Joseph" <joe.slater@windriver.com>,
Alexander Kanavin <alexander.kanavin@linux.intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"BURTON, ROSS" <ross.burton@intel.com>
Subject: Re: [PATCH 1/1] allarch: do not set baselib
Date: Wed, 03 Jan 2018 21:58:20 +0000 [thread overview]
Message-ID: <1515016700.5525.173.camel@linuxfoundation.org> (raw)
In-Reply-To: <007BD92917A2324FA403BCF9A464CF84D87A7007@ALA-MBC.corp.ad.wrs.com>
On Wed, 2018-01-03 at 21:46 +0000, Slater, Joseph wrote:
> Currently, we do have to provide qemuwrapper with
> LD_LIBRARY_PATH. We could hard-code all possible paths into that and
> not use ${libdir} and ${base_libdir}. (I tried it and it works.) We
> could also create a couple of new variables, like
> original_base_libdir, that don't get clobbered by allarch. Maybe
> qemuwrapper should be smart enough to compute LD_LIBRARY_PATH...
I suspect somehow we therefore need to decouple qemuwrapper from the
target packages and just ensure that a separate script is available in
PATH when the rootfs is generated?
The rootfs should know which multilibs are enabled and be able to
generate the wrapper correctly?
Cheers,
Richard
next prev parent reply other threads:[~2018-01-03 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 20:00 [PATCH 1/1] allarch: do not set baselib Joe Slater
2018-01-02 22:45 ` Richard Purdie
2018-01-03 8:43 ` Alexander Kanavin
2018-01-03 21:46 ` Slater, Joseph
2018-01-03 21:58 ` Richard Purdie [this message]
2018-01-04 17:24 ` Slater, Joseph
2018-01-03 21:56 ` Richard Purdie
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=1515016700.5525.173.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=joe.slater@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox