Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Slater, Joseph" <joe.slater@windriver.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"Burton, Ross" <ross.burton@intel.com>
Subject: Re: [PATCH 1/1] liberation-fonts: do not inherit allarch
Date: Fri, 22 Dec 2017 10:34:07 +0200	[thread overview]
Message-ID: <d3dc9e70-694e-5b41-1583-fa8b18bdc6f4@linux.intel.com> (raw)
In-Reply-To: <007BD92917A2324FA403BCF9A464CF84D87A1EE0@ALA-MBC.corp.ad.wrs.com>

On 12/22/2017 02:00 AM, Slater, Joseph wrote:
> A number of postinstall's run target binaries, whether on the host or
> target.  This means they invoke qemu on the host and try to tell it
> where bits are.  I think it might not be necessary to pass explicit
> information about library locations to qemu, but that is the way it
> is done, and that information is arch dependent.  It might well be
> the case that "confusion" occurs only when multilib is enabled, but
> the point is that it does happen.

I think Ross had a different patch to deal with the multilib-qemu libray 
confusion, so this might not yet be necessary.

Also, if this needs to be fixed, you need to fix it everywhere - 
cantarell-fonts, adwaita-icon-theme, etc. etc.

Alex


  reply	other threads:[~2017-12-22  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 21:23 [PATCH 1/1] liberation-fonts: do not inherit allarch Joe Slater
2017-12-21 22:28 ` Richard Purdie
2017-12-22  0:00   ` Slater, Joseph
2017-12-22  8:34     ` Alexander Kanavin [this message]
2017-12-22 23:50       ` Slater, Joseph

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=d3dc9e70-694e-5b41-1583-fa8b18bdc6f4@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=joe.slater@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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