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

On Sat, 2011-06-11 at 16:18 +0800, Robert Yang wrote:
> 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:

Thanks.  I did see that comment before but I don't think it really
answers the question.

If I'm understanding correctly, the issue is that you want nativesdk
binaries to search for libraries inside the SDK initially, and then to
fall back on the host's own search path (i.e. the same one that host
binaries would use) for libs that aren't shipped as part of the SDK.

Is the issue that the SYSTEM_DIRS end up pointing to somewhere inside
the sysroot?  If that's the case then it seems like a better fix would
be just to force it back to the genuine system dirs in the nativesdk
case.  (The default comes from Makeconfig so I think you should be able
to do this without source code patching.)  This would avoid the risk of
the sdk breaking on systems where ld.so.cache is missing for whatever
reason.

p.





      reply	other threads:[~2011-06-11  8:49 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
2011-06-11  8:46     ` Phil Blundell [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=1307781982.3307.22.camel@lenovo.internal.reciva.com \
    --to=pb@pbcl.net \
    --cc=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