[OE-core] [oe-core][PATCH 1/1] liberation-fonts: do not inherit allarch

Slater, Joseph joe.slater at windriver.com
Fri Dec 22 00:00:14 UTC 2017


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 it used to be the case that an attempt was made to run native versions of target tools during postinstall, but that seems to have been abandoned in favor of using qemu.  This means that if there is no qemu support, postinstall is deferred to first boot.  This is no problem except for read-only fs's, but they have other problems anyway.

Joe

-----Original Message-----
From: Richard Purdie [mailto:richard.purdie at linuxfoundation.org] 
Sent: Thursday, December 21, 2017 2:28 PM
To: Slater, Joseph; openembedded-core at lists.openembedded.org
Subject: Re: [OE-core] [oe-core][PATCH 1/1] liberation-fonts: do not inherit allarch

On Thu, 2017-12-21 at 13:23 -0800, Joe Slater wrote:
> The fontcache class performs post-installation cache updating and 
> needs target architecture information.

Can you expand a bit on this? Do you mean that the postinstalls written into the packages are arch specific? Can we stop the scripts being arch specific?

Cheers,

Richard


More information about the Openembedded-core mailing list