From: Phil Blundell <pb@pbcl.net>
To: akuster <akuster@mvista.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] ldconfig: add method to extend ldconfig search dirs
Date: Tue, 08 Dec 2015 22:34:09 +0000 [thread overview]
Message-ID: <1449614049.2002.11.camel@pbcl.net> (raw)
In-Reply-To: <56674604.3030900@mvista.com>
On Tue, 2015-12-08 at 13:05 -0800, akuster wrote:
> This is for ldconfig-native. The homebrew OE created. It has hard coded
> search patches. So OE only supports the standard /usr/* /lib* paths in
> the native part of the build.
In that case, given that you're talking about image construction, isn't
the right thing to make ldconfig-native respect whatever search paths
it's given by /etc/ld.so.conf in the image filesystem?
> so its using the default in the native ldconfig:
>
> #ifndef LD_SO_CONF
> # define LD_SO_CONF SYSCONFDIR "/ld.so.conf"
> #endif
I assume the point you're making here is that this ends up reading the
host's /etc/ld.so.conf, not the one in the image. Is that right?
p.
next prev parent reply other threads:[~2015-12-08 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 17:41 [PATCH 0/2] Add ldconfig alt lib search paths Armin Kuster
2015-11-11 17:41 ` [PATCH 1/2] ldconfig: add method to extend ldconfig search dirs Armin Kuster
2015-12-08 16:33 ` akuster808
2015-12-08 17:51 ` Phil Blundell
[not found] ` <56674604.3030900@mvista.com>
2015-12-08 22:34 ` Phil Blundell [this message]
[not found] ` <566891A3.4040300@mvista.com>
2015-12-09 21:41 ` Phil Blundell
2015-11-11 17:41 ` [PATCH 2/2] ldsoconf: allow extension via local.conf Armin Kuster
2015-11-11 18:39 ` Khem Raj
2015-11-11 19:22 ` akuster808
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=1449614049.2002.11.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=akuster@mvista.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