From: Peter Seebach <peter.seebach@windriver.com>
To: Chunrong Guo <B40290@freescale.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pseudo: pseudo-native breaks native builds for symver.patch
Date: Thu, 11 Jul 2013 11:12:23 -0500 [thread overview]
Message-ID: <20130711111223.06985e9f@e6410-2> (raw)
In-Reply-To: <1373529521-31010-1-git-send-email-B40290@freescale.com>
On Thu, 11 Jul 2013 15:58:41 +0800
Chunrong Guo <B40290@freescale.com> wrote:
> *symver.patch causes failure if the host glibc does not provide the glibc-2.0 version of the symbol.
I don't think we should take this out unconditionally, because it was added
to address a (different) problem -- we were ending up with the pseudo-native
libraries being used with host glibc that might be too old, and not have
newer versions.
I was under the impression that glibc tried to maintain binary compatibility
a fairly long way back; which hosts are omitting this symbol? What
architecture are you on?
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2013-07-11 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 7:58 [PATCH] pseudo: pseudo-native breaks native builds for symver.patch Chunrong Guo
2013-07-11 16:12 ` Peter Seebach [this message]
2013-07-12 2:10 ` Guo Chunrong-B40290
2013-07-12 18:28 ` Peter Seebach
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=20130711111223.06985e9f@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=B40290@freescale.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