From: Robert Yang <liezhi.yang@windriver.com>
To: "Purdie, Richard" <richard.purdie@intel.com>,
"Wold, Saul" <saul.wold@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: About share eglibc work directories
Date: Sat, 11 Jun 2011 15:55:37 +0800 [thread overview]
Message-ID: <4DF31F79.4070602@windriver.com> (raw)
Hi Richard and Saul,
The source code of eglibc and eglibc-nativesdk are not compatible because of
the patch ld-search-order.patch, this makes it a little complex to share their
source directories, what can I think is that always apply
ld-search-order.patch, then in do_configure_prepend:
if sdk && patch_applied:
do nothing
elif not_sdk && patch_applied:
un-apply the patch
elif sdk && patch_not_applied:
apply the patch
I don't know whether there is a CONDITIONAL variable which can make it simple.
And the source of eglibc is 137M, not too large, maybe we would not share them?
--
Thanks
Robert
next reply other threads:[~2011-06-11 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 7:55 Robert Yang [this message]
2011-06-11 8:03 ` About share eglibc work directories Phil Blundell
2011-06-11 8:18 ` Robert Yang
2011-06-11 8:46 ` Phil Blundell
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=4DF31F79.4070602@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@intel.com \
--cc=saul.wold@intel.com \
/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