From: ChenQi <Qi.Chen@windriver.com>
To: Robert Yang <liezhi.yang@windriver.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] cross-canadian/libgcc: fix aarch64's multilib SDK
Date: Mon, 4 Jan 2016 10:28:57 +0800 [thread overview]
Message-ID: <5689D8E9.4090606@windriver.com> (raw)
In-Reply-To: <5645AC3C.80804@windriver.com>
On 11/13/2015 05:24 PM, Robert Yang wrote:
>
>
> On 11/10/2015 12:27 AM, Burton, Ross wrote:
>>
>> On 4 November 2015 at 13:58, Robert Yang <liezhi.yang@windriver.com
>> <mailto:liezhi.yang@windriver.com>> wrote:
>>
>> The arm toolchain has a "-gnueabi" suffix, but aarch64 doesn't,
>> this makes multilib sdk doesn't work, for example:
>>
>> MACHINE = qemuarm64
>> require conf/multilib.conf
>> MULTILIBS = "multilib:lib32"
>> DEFAULTTUNE_virtclass-multilib-lib32 = "armv7at-neon"
>>
>> $ bitbake core-image-minimal -cpopulate_sdk
>>
>> Then extract SDK, the
>> environment-setup-armv7a-vfp-neon-pokymllib32-linux-gnueabi
>> doesn't work since:
>> * The CC is arm-pokymllib32-linux-gnueabi-gcc
>> which doesn't exist, the patch for cross-canadian.bbclass
>> fixes problem.
>> * Need aarch64-poky-linux/usr/lib/arm-poky-linux-linux-gnueabi
>> which doesn't exist, the patch for libgcc-common.inc fixes the
>> problem.
>>
>> [YOCTO #8616]
>>
>>
>> This breaks the allarch sstate sanity test on the autobuilder which
>> verifies
>> that allarch recipes don't have different hashes for a no-op change
>> to the machine.
>
> Hi Ross,
>
> After more investigations, the different between:
> MACHINE=qemux86 bitbake -Snone meta-toolchain
> MACHINE=qemuarm bitbake -Snone meta-toolchain
>
> is do_extra_symlinks' checksum, there is an ABIEXTENSION for
> nativesdk-libgcc-initial when qemuarm (eabi), and no "eabi" when
> qemux86.
>
> But as the commit said, the "eabi" is a must for qemuarm since its
> compiler
> arm-pokymllib32-linux-gnueabi-gcc contains eabi, otherwise it doesn't
> work.
>
> Maybe let the test case don't compare between qemuarm and qemux86 since
> arm is special ? Or do you have any other suggestions, please ?
>
>
> // Robert
>
Ping ...
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/242/steps/Running%20oe-selftest/logs/stdio
>>
>>
>> Ross
prev parent reply other threads:[~2016-01-04 2:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 13:58 [PATCH 0/1] cross-canadian/libgcc: fix aarch64's multilib SDK Robert Yang
2015-11-04 13:58 ` [PATCH 1/1] " Robert Yang
2015-11-05 1:48 ` Robert Yang
2015-11-09 16:27 ` Burton, Ross
2015-11-10 1:41 ` Robert Yang
2015-11-13 9:24 ` Robert Yang
2016-01-04 2:28 ` ChenQi [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=5689D8E9.4090606@windriver.com \
--to=qi.chen@windriver.com \
--cc=liezhi.yang@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