From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: gcc default version change (and qt4)
Date: Fri, 27 Apr 2012 14:58:28 +0200 [thread overview]
Message-ID: <20120427125827.GC3635@jama.jama.net> (raw)
In-Reply-To: <D68D089B-A0F5-4CE3-9124-4DA8AD02287E@dominion.thruhere.net>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On Fri, Apr 27, 2012 at 02:02:19PM +0200, Koen Kooi wrote:
>
> Op 27 apr. 2012, om 13:39 heeft Richard Purdie het volgende geschreven:
>
> > I'd like to warn people that I'm pretty close to throwing the version
> > switch to default to gcc 4.7 at the same time as merging in Khem's
> > patches. I don't think this will surprise anyone, we've talked about
> > doing it post release for long enough.
> >
> > It also appears that qt 4.7.4 has issues with gcc 4.7 and 4.8.1 is fixed
> > so I'm going to change the default version on that at the same time.
> >
> > Since the tests on the autobuilder are looking pretty good now, I'll
> > probably do this sooner than later, maybe on Monday.
> >
> > I'll probably then give it a week, then assuming no reason to change
> > back to the older version, I'll remove gcc 4.6 and qt 4.7.4 from
> > OE-Core. They may get added to meta-oe's toolchain layer at that point
> > but that is up to the appropriate maintainers.
>
> FWIW angstrom will be using 4.5 for 'denzil' and 4.7 for 'master'. No 4.6 anywhere :)
My test build on armv4t is still running, hopefully the result will be
better than when I've tried to enable gold..
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2012-04-27 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 11:39 gcc default version change (and qt4) Richard Purdie
2012-04-27 12:02 ` Koen Kooi
2012-04-27 12:58 ` Martin Jansa [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=20120427125827.GC3635@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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