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: Fri, 22 Jan 2010 14:02:37 -0800 [thread overview]
Message-ID: <4B5A207D.7080904@techsol.ca> (raw)
In-Reply-To: <20100121232210.GB11015@gmail.com>
Khem Raj wrote:
> On (21/01/10 14:24), Dallas Foley wrote:
>> 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.
>
> You could try to backport armv4t-interworking.patch from eglibc/files
> that should help you will getting 2.9 up on armv4t. This patch is
> applied to 2.10.1 may be moving to 2.10.1 would be better than 2.9
> IMO
>
> -Khem
Confirmed. gpe-mini-browser2 works with glibc 2.10.1
prev parent reply other threads:[~2010-01-22 22:05 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
2010-01-21 23:22 ` Khem Raj
2010-01-21 23:35 ` Dallas Foley
2010-01-22 22:02 ` Dallas Foley [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=4B5A207D.7080904@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