From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] eglibc: Make ld.so.conf more flexible
Date: Wed, 23 Jul 2014 18:50:52 -0500 [thread overview]
Message-ID: <20140723185052.74ad39d3@e6410-2> (raw)
In-Reply-To: <1406155290-25903-1-git-send-email-ben.shelton@ni.com>
On Wed, 23 Jul 2014 17:41:30 -0500
Ben Shelton <ben.shelton@ni.com> wrote:
> Most modern distros will include conf files in /etc/ld.so.conf.d/
> when generating the ld.so cache. This change will bring that flexibility.
I was just looking at a patch to do roughly this. Mine added a
USE_LDCONFIG_CONF_D flag, and then had eglibc's install create the directory
and append that line to ld.so.conf if the flag was set. I'm not sure whether
the extra functionality justifies the effort. I would suggest that, if
this is going to be unconditionally present, the directory should be too.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2014-07-23 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 22:41 [PATCH] eglibc: Make ld.so.conf more flexible Ben Shelton
2014-07-23 23:50 ` Peter Seebach [this message]
2014-07-24 1:48 ` Khem Raj
2014-07-24 1:59 ` Mark Hatle
2014-07-24 21:30 ` 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=20140723185052.74ad39d3@e6410-2 \
--to=peter.seebach@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox