From: Khem Raj <raj.khem@gmail.com>
To: poky@yoctoproject.org
Subject: Re: GCC-4.6.0 not ready for prime time?
Date: Thu, 09 Jun 2011 15:54:59 -0700 [thread overview]
Message-ID: <4DF14F43.4020904@gmail.com> (raw)
In-Reply-To: <4DF0F9E7.6020806@mlbassoc.com>
On 06/09/2011 09:50 AM, Gary Thomas wrote:
> I'm not convinced switching to GCC-4.6.0 is a good choice at this time.
at some point we have to and we have time to harden it until next
release. Compiler upgrades are a bit of work
> Not only did I have problems getting a working kernel, there are a
> lot of applications that don't build with this new compiler. Some
> of those that do, don't work :-(
>
> I have a local recipe to build Mozilla FireFox which has been working
> fine, but with GCC-4.6.0, it no longer runs correctly. Given the magnitude
> of FireFox, it may take me a while to figure out why.
yes there are always some issues that need resolving. If you are able to
narrow down the problem a bit it would be easier to pin point the problem.
>
> Even some core programs no longer build, e.g. web-webkit (I was looking
> for an alternate web browser). This was probably not obvious as it is
> no longer being built by your test images (it used to be included in
> core-image-sato but was dropped by
> 9d7aa1090c407ac0da6154c481f1c787fd7efbfc)
>
> I guess I'll be sticking with GCC-4.5.x for now
>
For something that you would like to release soon it may be a sane choice
-Khem
prev parent reply other threads:[~2011-06-09 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 16:50 GCC-4.6.0 not ready for prime time? Gary Thomas
2011-06-09 22:54 ` Khem Raj [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=4DF14F43.4020904@gmail.com \
--to=raj.khem@gmail.com \
--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 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.