Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] eglibc: Make ld.so.conf more flexible
Date: Wed, 23 Jul 2014 20:59:27 -0500	[thread overview]
Message-ID: <53D0687F.8050404@windriver.com> (raw)
In-Reply-To: <CAMKF1sqy70-p_sJ9waC6yJGxxfcY=Fgbr=DdK6Cv019GM=YNEg@mail.gmail.com>

On 7/23/14, 8:48 PM, Khem Raj wrote:
> On Wed, Jul 23, 2014 at 4:50 PM, Peter Seebach
> <peter.seebach@windriver.com> wrote:
>> 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.
>
> Many embedded systems dont use ldconfig and we have USE_LDCONFIG knob
> to control it.
> This should fall under that knob as well.

Original idea was two knobs.. one for USE_LDCONFIG, and one for using the 
ld.so.conf.d directory and setup.

The later has been requested of me many times, but we've not implemented it 
generically.  I think it's time to do so -- but it should be tied to 
USE_LDCONFIG at a minimum, I just don't know if it should always be enabled or 
just sometimes.  (Always means the ld.so.conf file gets the include line, so 
it's NOT a lot of bytes.)

--Mark

>>
>> -s
>> --
>> Listen, get this.  Nobody with a good compiler needs to be justified.
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core



  reply	other threads:[~2014-07-24  1:59 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
2014-07-24  1:48   ` Khem Raj
2014-07-24  1:59     ` Mark Hatle [this message]
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=53D0687F.8050404@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox