From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
Joe Slater <jslater@windriver.com>,
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:56:10 +0000 [thread overview]
Message-ID: <1515016570.5525.171.camel@linuxfoundation.org> (raw)
In-Reply-To: <e3528177-a042-0ac5-2a06-6cb9b279fd89@linux.intel.com>
On Wed, 2018-01-03 at 10:43 +0200, Alexander Kanavin wrote:
> On 01/03/2018 12:45 AM, Richard Purdie wrote:
> >
> > Sorry, but I don't think this can work :/.
> >
> > Do the sstate sig selftests pass with this change?
> >
> > I appreciate this will make some things "work" but it will mean
> > that
> > allarch packages rebuild for each architecture or multilib and that
> > isn't right either.
> >
> > So we need a better solution here. Why do we need libdir paths to
> > run
> > binaries anyway? Is this a libexec issue? Perhaps the things in
> > question shouldn't be allarch?
>
> I think Ross has spent some time developing a fix for this same
> issue, perhaps he can chime in?
I think he did, I think I also pointed him at the sstate signature
tests and that caused some problems. Ross may be able to elaborate
more...
Cheers,
Richard
prev parent reply other threads:[~2018-01-03 21:56 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
2018-01-04 17:24 ` Slater, Joseph
2018-01-03 21:56 ` Richard Purdie [this message]
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=1515016570.5525.171.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.com \
--cc=jslater@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