From: Kang Kai <Kai.Kang@windriver.com>
To: ChenQi <Qi.Chen@windriver.com>, <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [V2][PATCH 0/3] allarch: disable allarch when multilib is used
Date: Wed, 22 Aug 2018 11:17:15 +0800 [thread overview]
Message-ID: <7cd64d13-0010-02e9-a8cd-7760f94a306e@windriver.com> (raw)
In-Reply-To: <c3486f8b-70ae-028b-5208-97f876462c71@windriver.com>
On 2018年08月22日 10:36, ChenQi wrote:
> There's some oe-selftest failures on autobuiler.
>
> https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/1300/steps/Running%20oe-selftest/logs/stdio
>
The patches are to disable allarch when multilib is used. So failure of
test case sstatetests.SStateTests.test_sstate_allarch_samesigs_multilib
is to be expected.
I'll check the other 4 testcase failures.
Regards,
Kai
>
> Best Regards,
> Chen Qi
>
> On 08/21/2018 02:36 PM, kai.kang@windriver.com wrote:
>> From: Kai Kang <kai.kang@windriver.com>
>>
>> V2:
>> * move content of allarch.bbclass to allarch-enabled.bbclass and only
>> inherit allarch-enabled when multilib is not used
>> * update SSTATE_DUPWHITELIST
>>
>> Build pass for following targets on qemux86-64 and qemuarm64 for rpm,
>> ipk and deb.
>>
>> * core-image-sato
>> * core-image-sato -c populate_sdk
>> * world
>> * buildtools-tarball
>>
>> Known issues:
>> There are 2 *existing* multilib related issues which are not caused by
>> this serial of patches:
>>
>> 1 QA warnings of lib32-meta-ide-support and lib32-perf
>>
>> WARNING: lib32-meta-ide-support-1.0-r3 do_configure: Manifest
>> /buildarea1/jkang-taf/WRL1018/OV/0730/host/build/tmp-glibc/sstate-control/manifest-x86_64_x86_64-nativesdk-ncurses.populate_sysroot
>>
>> not found in intel_x86_64 corei7-32 core2-32 i686 i586 x86 allarch
>> x86_64_x86_64-nativesdk (variant '')?
>>
>> WARNING: lib32-perf-1.0-r9 do_install: Manifest
>> /buildarea1/jkang-taf/WRL1018/OV/0730/host/build/tmp-glibc/sstate-control/manifest-x86_64_i686-binutils-cross-x86_64.populate_sysroot
>>
>> not found in x86_64_i686 (variant '')?
>>
>> 2 fails to build lib32-buildtools-tarball
>>
>> ERROR: lib32-buildtools-tarball-1.0-r0 do_populate_sdk: No manifest
>> generated from: qemuwrapper-cross in
>> /buildarea3/kkang/poky-20141111/poky/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb
>>
>>
>> I am working on them.
>>
>>
>> The following changes since commit
>> 99506b0017bdf8dbf42ec5dc048d91a5609dabe3:
>>
>> weston-init: run login before start weston.service (2018-08-20
>> 17:38:23 +0100)
>>
>> are available in the Git repository at:
>>
>> git://git.pokylinux.org/poky-contrib kangkai/allarch-enabled
>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/allarch-enabled
>>
>> Kai Kang (3):
>> cmake.bbclass: fix wrong toolchain flags of nativesdk package
>> allarch: disable allarch when multilib is used
>> sstate.bbclass: update SSTATE_DUPWHITELIST
>>
>> meta/classes/allarch-enabled.bbclass | 52 ++++++++++++++++++++++++++++
>> meta/classes/allarch.bbclass | 51 ++-------------------------
>> meta/classes/cmake.bbclass | 1 +
>> meta/classes/icecc.bbclass | 2 +-
>> meta/classes/multilib.bbclass | 2 +-
>> meta/classes/multilib_global.bbclass | 2 +-
>> meta/classes/package.bbclass | 6 ++--
>> meta/classes/sstate.bbclass | 4 ++-
>> 8 files changed, 64 insertions(+), 56 deletions(-)
>> create mode 100644 meta/classes/allarch-enabled.bbclass
>>
>
>
--
Regards,
Neil | Kai Kang
prev parent reply other threads:[~2018-08-22 3:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 6:36 [V2][PATCH 0/3] allarch: disable allarch when multilib is used kai.kang
2018-08-21 6:36 ` [PATCH 1/3] cmake.bbclass: fix wrong toolchain flags of nativesdk package kai.kang
2018-08-21 6:36 ` [PATCH 2/3] allarch: disable allarch when multilib is used kai.kang
2018-08-21 6:36 ` [PATCH 3/3] sstate.bbclass: update SSTATE_DUPWHITELIST kai.kang
2018-08-22 2:36 ` [V2][PATCH 0/3] allarch: disable allarch when multilib is used ChenQi
2018-08-22 2:46 ` ChenQi
2018-08-22 7:47 ` Kang Kai
2018-08-22 3:17 ` Kang Kai [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=7cd64d13-0010-02e9-a8cd-7760f94a306e@windriver.com \
--to=kai.kang@windriver.com \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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