From: Mark Hatle <mark.hatle@windriver.com>
To: Luo Zhenhua <zhenhua.luo@freescale.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Multilib build support by single toolchain generated by Yocto
Date: Tue, 15 Sep 2015 08:04:31 -0500 [thread overview]
Message-ID: <55F8175F.6050709@windriver.com> (raw)
In-Reply-To: <BN3PR03MB1367C0B9D89AD811CC625D7CE45C0@BN3PR03MB1367.namprd03.prod.outlook.com>
On 9/15/15 3:23 AM, Luo Zhenhua wrote:
> Hello all,
>
>
>
> Currently to support 32b and 64b build for same core in Yocto, two separated
> compilers need to be generated. Is there plan to support multilib build(32b and
> 64b) by single toolchain which is generated by Yocto in future?
>
The requirements for multilib compilers depend on architecture, configuration
and GNU GCC limitations. Some architects will work fine with a single compiler,
others may require multiple compilers.
If you can assist with this effort, I believe the work would be appreciated.
--Mark
>
>
>
> Best Regards,
>
>
>
> Zhenhua
>
>
>
next prev parent reply other threads:[~2015-09-15 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 8:23 Multilib build support by single toolchain generated by Yocto Luo Zhenhua
2015-09-15 13:04 ` Mark Hatle [this message]
2015-09-16 9:42 ` Luo Zhenhua
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=55F8175F.6050709@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=zhenhua.luo@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.