On 01/07/2016 06:57 PM, Richard Purdie wrote:
On Wed, 2016-01-06 at 23:45 -0800, Robert Yang wrote:
The dependencies chain:
run-postinsts -> update-rc.d.bbclass -> initscripts -> update
-alternatives.
The update-alternatives is provided by opkg-utils which is not
allarch.
This caused a problem:
$ bitbake lib32-core-image-minimal
Both lib32-opkg-utils and opkg-utils would be built, but opkg-utils
shouldn't, this patch can fix the problem.
[YOCTO #8879]
Signed-off-by: Robert Yang <[email protected]>
---
.../run-postinsts/run-postinsts_1.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Removing allarch isn't the correct way to fix this, we need to figure
out what is going wrong and fix multilib.
After more investigations, the problem is for allarch recipe such as
run-postinsts:
$ bitbake lib32-run-postinsts
No lib32 recipes was built, but 64bit python, flex, openssl and
others are built since lib32-allarch recipe is the same as allarch
one. (the dependencies chain:
run-postinsts -> update-rc.d.bbclass -> initscripts ->
update-alternatives-opkg-utils)
I think that SIGGEN_EXCLUDERECIPES_ABISAFE is for recipes which depend on
the abisafe ones, not for abisafe ones depend on otheres.
I'm still thinking how to fix it, any suggestions is appreciated.
// Robert
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
