Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: "Purdie, Richard" <richard.purdie@intel.com>,
	"Wold, Saul" <saul.wold@intel.com>
Subject: Re: About share eglibc work directories
Date: Sat, 11 Jun 2011 16:18:06 +0800	[thread overview]
Message-ID: <4DF324BE.2090407@windriver.com> (raw)
In-Reply-To: <1307779402.3307.12.camel@lenovo.internal.reciva.com>


On 06/11/2011 04:03 PM, Phil Blundell wrote:
> On Sat, 2011-06-11 at 15:55 +0800, Robert Yang wrote:
>> 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:
>
> I must admit I never quite understood why ld-search-order.patch is
> really required; it seems like rather a gruesome hack.  Why can't the
> SDK paths just be put in RPATH records for the nativesdk binaries?
>

Here is the comment in ld-search-order.patch, hope this can answer you question:

Upstream-Status: Inappropriate [embedded specific]

The default lib search path order is:

   1) LD_LIBRARY_PATH
   2) RPATH from the binary
   3) ld.so.cache
   4) default search paths embedded in the linker

For nativesdk binaries which are being used alongside binaries on a host system, we
need the search paths to firstly search the shipped nativesdk libs but then also
cover the host system. For example we want the host system's libGL and this may be
in a non-standard location like /usr/lib/mesa. The only place the location is know
about is in the ld.so.cache of the host system.

Since nativesdk has a simple structure and doesn't need to use a cache itself, we
repurpose the cache for use as a last resort in finding host system binaries. This
means we need to switch the order of 3 and 4 above to make this work effectively.

RP 14/10/2010

// Robert


> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2011-06-11  8:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11  7:55 About share eglibc work directories Robert Yang
2011-06-11  8:03 ` Phil Blundell
2011-06-11  8:18   ` Robert Yang [this message]
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=4DF324BE.2090407@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