From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Set preferred glibc to 2.10.1 in conf/distro/micro.conf
Date: Mon, 18 Jan 2010 11:41:37 -0800 [thread overview]
Message-ID: <20100118194137.GA31712@gmail.com> (raw)
In-Reply-To: <op.u6oir0rqmn1qzu@guohr-laptop-ubuntu>
On (17/01/10 21:37), Guo Hongruan wrote:
> 在 Sun, 17 Jan 2010 21:30:39 +0800，Holger Hans Peter Freyther
> <holger+oe@freyther.de> 写道:
>
> >On Sunday 17 January 2010 14:10:18 Guo Hongruan wrote:
> >>* the preferred version of binutils of conf/distro/micro.conf is 2.19.51
> >>* the preferred version of glibc is 2.6.1 which is defined in
> >> sane-toolchain.inc * the ld produced by binutils-2.19.51
> >>reports that it
> >> can not find the __begin symbol when linking with glibc-2.6.1
> >
> >It would be really great if you could start to read emails too.
> >
> >So now we now two ways to cure the symptoms but we have no idea about the
> >underlying root cause.
> >
> >Is it too much to ask what the actual error is? The __begin
> >reminds me of a
> >bug in the linker script Khem was pointing out?
>
>
> I guess you are using latest binutils. There has been changes in ld
> which surfaced this issue. So either you could switch back to using
> older binutils like 2.18 or something. Or you could also port the patch
> recipes/glibc/glibc-2.9/glibc-2.9-use-_begin.patch
>
> That's the cause of the building failure. I think it is better to
> use the newer version of glibc that to port the patch to glibc-2.6.1
It takes quite a bit to validate a toolchain (gcc/binutils/libc) before
it is pushed as default preference. Dont use sword to kill a
fly. You could very well backport the one patch and keep using 2.6.1
if you want to upgrade make sure that its stable enough and tested
enough on some common architecuture/machines but as eglibc is default
libc for micro I wouldnt worry too much for glibc as it might not hit
all users of micro.
>
>
> >
> >_______________________________________________
> >Openembedded-devel mailing list
> >Openembedded-devel@lists.openembedded.org
> >http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
> --
> 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-18 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 13:10 [PATCH] Set preferred glibc to 2.10.1 in conf/distro/micro.conf Guo Hongruan
2010-01-17 13:30 ` Holger Hans Peter Freyther
2010-01-17 13:37 ` Guo Hongruan
2010-01-18 19:41 ` Khem Raj [this message]
2010-01-21 2:12 ` Guo Hongruan
2010-01-21 12:41 ` Phil Blundell
2010-01-21 13:08 ` Guo Hongruan
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=20100118194137.GA31712@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