From: Saul Wold <saul.wold@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: poky@yoctoproject.org,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [poky] [PATCH 0/1] switch to gcc 4.6.0 for x86 x86-64 & arm
Date: Fri, 20 May 2011 17:10:51 -0700 [thread overview]
Message-ID: <4DD7030B.909@intel.com> (raw)
In-Reply-To: <4DD6FEC2.9030503@linux.intel.com>
On 05/20/2011 04:52 PM, Darren Hart wrote:
>
>
> On 05/17/2011 11:07 AM, Nitin A Kamble wrote:
>> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>>
>> gcc 4.6.0 is good enough to switch for x86, x86-64& arm now.
>>
>> I could build core-sdk images and run them through the qemu machines
>> when compiled with gcc 4.6.0.
>
> Has all of meta-intel been built using 4.6.0? If not, that would be a
> good test-case for the x86* architectures. Perhaps we could get a manual
> scheduler up on the autobuilder for that to make it easy to kick off?
>
> What do you think Beth?
>
Maybe after M1 RC1 gets built
Sau!
>>
>> mips& ppc are still not ready, mainly the kernel compilation issues
>> with gcc 4.6.0. These kernel issues are being worked on by Bruce.
>>
>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>> Branch: nitin/misc
>> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc
>>
>> Thanks,
>> Nitin A Kamble<nitin.a.kamble@intel.com>
>> ---
>>
>>
>> Nitin A Kamble (1):
>> tcmode-default: switch to gcc 4.6.0 for x86, x86-64& arm
>>
>> meta/conf/distro/include/tcmode-default.inc | 8 ++++++--
>> 1 files changed, 6 insertions(+), 2 deletions(-)
>>
>
prev parent reply other threads:[~2011-05-21 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 18:07 [PATCH 0/1] switch to gcc 4.6.0 for x86 x86-64 & arm Nitin A Kamble
2011-05-17 18:07 ` [PATCH 1/1] tcmode-default: switch to gcc 4.6.0 for x86, " Nitin A Kamble
2011-05-20 15:06 ` [PATCH 0/1] switch to gcc 4.6.0 for x86 " Saul Wold
2011-05-20 23:52 ` Darren Hart
2011-05-21 0:10 ` Saul Wold [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=4DD7030B.909@intel.com \
--to=saul.wold@intel.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.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