From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How do you add to library path?
Date: Thu, 26 Apr 2012 22:12:15 +0200 [thread overview]
Message-ID: <CAC1BbcRZ-Fft9=KZ7YpK66ykaFsN5XuatMWZCrG_5omk=MBKvA@mail.gmail.com> (raw)
In-Reply-To: <jnc1d9$t1p$1@dough.gmane.org>
On 26 April 2012 19:42, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> What's the right way to permanently add a directory to the search path
> for dynamic libraries? ?(Preferably at build-time, rather than at
> run-time.)
>
> I've added the directory path to /etc/ld.so.conf using a post-build
> script. But, that file seems to be ignored at boot time (and there is
> no "ldconfig" to run even if I wanted to).
>
> I suppose I could set LD_LIBRARY_PATH globally, but for performance
> reasons, I'd prefer that the new path went into /etc/ld.so.cache. [I'm
> not sure how one sets a global environment variable anyway.]
>
> There have been several threads about this in the past, but none of
> them seemed to offer any answers...
$ grep -A8 config\ LDSO_CACHE extra/Configs/Config.in
config LDSO_CACHE_SUPPORT
bool "Enable library loader cache (ld.so.conf)"
depends on HAVE_SHARED
default y
help
Enable this to make use of /etc/ld.so.conf, the shared library loader
cache configuration file to support for non-standard library paths.
After updating this file, it is necessary to run 'ldconfig' to update
the /etc/ld.so.cache shared library loader cache file.
$ make help | grep util
utils - build target utilities
hostutils - build host utilities (see utils)
install_utils - install target utilities
install_hostutils - install host utilities
Generally speaking, you can globally export variables for sh in e.g.
/etc/profile
HTH,
next prev parent reply other threads:[~2012-04-26 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 17:42 [Buildroot] How do you add to library path? Grant Edwards
2012-04-26 20:12 ` Bernhard Reutner-Fischer [this message]
2012-04-27 22:18 ` Arnout Vandecappelle
2012-04-28 10:44 ` Michael S. Zick
2012-04-28 11:15 ` Bernhard Reutner-Fischer
2012-04-28 14:13 ` Arnout Vandecappelle
2012-04-28 14:53 ` Grant Edwards
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='CAC1BbcRZ-Fft9=KZ7YpK66ykaFsN5XuatMWZCrG_5omk=MBKvA@mail.gmail.com' \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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.