Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Move sane-toolchain defaults for gcc binutils and eglibc
Date: Wed, 12 May 2010 10:49:02 -0700	[thread overview]
Message-ID: <20100512174902.GA9872@gmail.com> (raw)
In-Reply-To: <1273657450.1773.43.camel@saphir>

[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]

On (12/05/10 11:44), Michael 'Mickey' Lauer wrote:
> Am Mittwoch, den 12.05.2010, 11:39 +0200 schrieb Martin Jansa:
> > On Tue, May 11, 2010 at 10:39 AM, Roman I Khimov <khimov@altell.ru> wrote:
> > > В сообщении от Вторник 11 мая 2010 03:27:20 автор Khem Raj написал:
> > >> 4.4.3 is not so widely used in distributions unlike 4.4.2
> > 
> > Hi,
> > 
> > My guess: just because it's not preferred by sane-toolchain.inc?
> > 
> > >> I can also just add 4.4.4 and leave 4.4.3 as it is if someone wants
> > >> to keep using 4.4.3
> > >
> > > Using 4.4.3 here, think it'd be nice to move to 4.4.4.
> > 
> > what about updating
> > conf/distro/include/sane-toolchain.inc
> > to 4.4.4 if we don't find any new issue with it?
> 
> Sounds good.

Here is a patch to move gcc to 4.4.4, eglibc to 2.11 and binutils to
2.20.1 releases as defaults. I have tested this combination on ARM
and x86 without any regressions that I dont have on existing combination. 

sane-toolchain.in is used by kaeilos-2010, shr, micro and minimal DISTROs
if the maintainers are ok with this then please ack this patch

Thanks
-Khem

Signed-off-by: Khem Raj <raj.khem@gmail.com>

[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 1043 bytes --]

diff --git a/conf/distro/include/sane-toolchain.inc b/conf/distro/include/sane-toolchain.inc
index daa2def..7f249b0 100644
--- a/conf/distro/include/sane-toolchain.inc
+++ b/conf/distro/include/sane-toolchain.inc
@@ -5,14 +5,14 @@
 #############################################################################
 
 # Base line versions, good for most things
-PREFERRED_GCC_VERSION                ?= "4.4.2"
-PREFERRED_BINUTILS                   ?= "2.20"
+PREFERRED_GCC_VERSION                ?= "4.4.4"
+PREFERRED_BINUTILS                   ?= "2.20.1"
 
 # Prefer glibc 2.6 and uclibc 0.9.30, these have had the most testing.
 PREFERRED_VERSION_glibc             ?= "2.10.1"
 PREFERRED_VERSION_glibc-initial     ?= "2.10.1"
-PREFERRED_VERSION_eglibc             ?= "2.10"
-PREFERRED_VERSION_eglibc-initial     ?= "2.10"
+PREFERRED_VERSION_eglibc             ?= "2.11"
+PREFERRED_VERSION_eglibc-initial     ?= "2.11"
 PREFERRED_VERSION_uclibc            ?= "0.9.30.1"
 PREFERRED_VERSION_uclibc-initial    ?= "0.9.30.1"
 

  reply	other threads:[~2010-05-12 17:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 23:27 [RFC] Move gcc 4.4.3 recipes in favour of 4.4.4 Khem Raj
2010-05-11  4:37 ` Martin Jansa
2010-05-11  5:28   ` Khem Raj
2010-05-11  8:39 ` Roman I Khimov
2010-05-12  9:39   ` Martin Jansa
2010-05-12  9:44     ` Michael 'Mickey' Lauer
2010-05-12 17:49       ` Khem Raj [this message]
2010-05-12 21:28         ` [RFC] Move sane-toolchain defaults for gcc binutils and eglibc Martin Jansa
2010-05-12 11:14     ` [RFC] Move gcc 4.4.3 recipes in favour of 4.4.4 Roman I Khimov

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=20100512174902.GA9872@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@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