From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] Add support for ld.so.conf.d
Date: Mon, 28 Jul 2014 13:59:20 -0500 [thread overview]
Message-ID: <53D69D88.8090009@windriver.com> (raw)
In-Reply-To: <CAMKF1so=YuEoE2vQgG_yZWLzeKg=71vYEdHnX0V8fNowL=95zg@mail.gmail.com>
On 7/28/14, 1:47 PM, Khem Raj wrote:
> On Mon, Jul 28, 2014 at 11:39 AM, Peter Seebach
> <peter.seebach@windriver.com> wrote:
>> The default behavior for USE_LDCONFIG is to use an empty ld.so.conf.
>> In some cases, it might be desireable to have an ld.so.conf.d directory,
>> and inherit files from there. This is a common enough use case to
>> justify support in the recipe, but not common enough to make it the
>> default. So, eglibc gets a new USE_LDCONFIG_CONF_D value, default 0.
>> If it's set to 1, we create the directory and add an "include" line
>> for it to ld.so.conf.
>
> the patch is good but introducing another variable is not needed you
> can cover it under US_LDCONFIG itself, ldconfig with empty ld.so.conf
> will still parse standard lib search paths anyway
>
> Secondly when we use ldconfig it generates ld.so.cache under /etc
> so I hope we take care of this when we have ro-rootfs
>
In a read-only root case, the ld.so.cache is generated in the cross environment.
I don't know if the cross ldconfig knows about the includes though. Someone
will have to check that.
--Mark
next prev parent reply other threads:[~2014-07-28 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 18:39 [PATCH 0/1] add USE_LDCONFIG_CONF_D Peter Seebach
2014-07-28 18:39 ` [PATCH 1/1] Add support for ld.so.conf.d Peter Seebach
2014-07-28 18:47 ` Khem Raj
2014-07-28 18:59 ` Mark Hatle [this message]
2014-07-28 20:55 ` Peter Seebach
2014-07-28 19:03 ` 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=53D69D88.8090009@windriver.com \
--to=mark.hatle@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.