From: Dallas Foley <dfoley@techsol.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: I realy think we should upgrade PREFERRED_VERSION_glibc to 2.9 in conf/distro/include/sane-toolchain.inc
Date: Thu, 21 Jan 2010 14:24:16 -0800 [thread overview]
Message-ID: <4B58D410.2020100@techsol.ca> (raw)
In-Reply-To: <19c1b8a91001211410y19908564h7fe9aca3f81317ab@mail.gmail.com>
Khem Raj wrote:
> On Thu, Jan 21, 2010 at 5:32 AM, Guo Hongruan <camelguo@gmail.com> wrote:
>> Hi guys,
>> I think we should upgrade PREFERRED_VERSION_glibc from 2.6 to 2.9 in
>> conf/distro/include/sane-toolchain.inc. The reasons are:
Although I haven't tried a build from scratch in a few weeks or so, I
have one known problem with glibc 2.9. I wonder if it's just me or not.
glibc 2.6.1 always works. On my armv4t board gpe-mini-browser2 always
seg faults. I've tried different gcc and binutils combinations. However,
glibc 2.9 on armv5te (imx) or armv7a (omap) work fine for me.
>>
>> 1. Most of distributions have upgraded their preferred glibc to 2.9 long
>> time ago.
>> conf/distro/angstrom-2008.1.conf:PREFERRED_VERSION_glibc ?=
>> "2.9"
>> conf/distro/angstrom-2008.1.conf:PREFERRED_VERSION_glibc-initial ?=
>> "2.9"
>> conf/distro/jlime-2009.1.conf:PREFERRED_VERSION_glibc-initial = "2.9"
>> conf/distro/jlime-2009.1.conf:PREFERRED_VERSION_glibc = "2.9"
>> conf/distro/kaeilos.conf:PREFERRED_VERSION_glibc ?= "2.9"
>> conf/distro/kaeilos.conf:PREFERRED_VERSION_glibc-initial ?= "2.9"
>>
>> from the above, you can get to know that most distributions have upgraded
>> their preferred glibc to 2.9 from 2008 ago.
>>
>> Of course, there are still some distributions which uses old glibc. The only
>> reason I guess is that we have not updated them for a long time. (for from
>> tinderbox, you can get to know that these distributions have not been built
>> for a long time)
>>
>>
>> 2. from tinderbox, you can see that the glibc-2.9 is well-tested, no
>> glibc-2.6
>> http://tinderbox.openembedded.net/packages/?name=glibc&page=1
>>
>> from the above link, you can get to know that the glibc-2.9 not glibc-2.6.1
>> has had most testing.
>>
>> 3. the last reason is that I have built some projects with glibc-2.6, unless
>> with the old binutils, the glibc-2.6 always failed to build.
>>
>> So, I think it is the time to upgrade PREFERRED_VERSION_glibc to 2.9 in
>> sane-toolchian.inc
>
> Yes I am ok with this. Infact you could even use 2.10.1 now you are at it
> and micro already did the change.
>
>> --
>> Guo Hongruan, Embedded Linux Consultant
>> Skype: camelguo
>> Twitter: camelguo
>> http://www.gulessoft.com
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
next prev parent reply other threads:[~2010-01-21 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 13:32 I realy think we should upgrade PREFERRED_VERSION_glibc to 2.9 in conf/distro/include/sane-toolchain.inc Guo Hongruan
2010-01-21 22:10 ` Khem Raj
2010-01-21 22:24 ` Dallas Foley [this message]
2010-01-21 23:22 ` Khem Raj
2010-01-21 23:35 ` Dallas Foley
2010-01-22 22:02 ` Dallas Foley
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=4B58D410.2020100@techsol.ca \
--to=dfoley@techsol.ca \
--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