From: Peter Seebach <peter.seebach@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] Add support for ld.so.conf.d
Date: Mon, 28 Jul 2014 14:03:50 -0500 [thread overview]
Message-ID: <20140728140350.46af54ca@e6410-2> (raw)
In-Reply-To: <CAMKF1so=YuEoE2vQgG_yZWLzeKg=71vYEdHnX0V8fNowL=95zg@mail.gmail.com>
On Mon, 28 Jul 2014 11:47:30 -0700
Khem Raj <raj.khem@gmail.com> wrote:
> 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
The reason I wanted another variable is to control the creation of a
*non-empty* ld.so.conf that would pick up other config files. The idea
is that if you wanted to add a non-standard library search path, you
could create a file in ld.so.conf.d. I didn't want to make the file
have contents unconditionally.
> 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
I assume that's already working for the existing empty ld.so.conf you get
with USE_LDCONFIG=1.
It does occur to me that I don't know whether our cross-ldconfig knows
this syntax. I'll double-check that.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
prev parent reply other threads:[~2014-07-28 19:04 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
2014-07-28 20:55 ` Peter Seebach
2014-07-28 19:03 ` Peter Seebach [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=20140728140350.46af54ca@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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