From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Allowing user to run ldconfig in post-build script
Date: Thu, 16 Jun 2016 23:32:57 +0200 [thread overview]
Message-ID: <20160616233257.7a47d276@itchy> (raw)
In-Reply-To: <20160616195310.GF3665@free.fr>
Hi!
Le Thu, 16 Jun 2016 21:53:10 +0200,
"Yann E. MORIN" <yann.morin.1998@free.fr> a ?crit :
> On 2016-06-16 15:37 +0200, Thomas Petazzoni spake thusly:
> > On Thu, 16 Jun 2016 15:12:06 +0200 (CEST), Eric Le Bihan wrote:
> >
> > > Since commit 9c40723, handling of ldconfig in the main Makefile
> > > as been dropped, and if /etc/ld.so.conf is found in the target
> > > root filesystem, the build fails.
> > >
> > > Not being able to run ldconfig and generate the ld.so cache has
> > > two drawbacks:
> > >
> > > - it prevents the user from installing some libraries in other
> > > locations than /lib and /usr/lib (e.g. /opt/foo/lib). This can be
> > > solved with symlinks, though.
> >
> > Does the dynamic linker uses /etc/ld.so.conf at runtime to find
> > other libraries, even if there is no /etc/ld.so.cache? If that's
> > the case, then our check for ld.so.conf being absent is somewhat
> > wrong, as it would be valid to have, independently of whether
> > ldconfig has created ld.so.cache or not.
>
> What I understand is that, to find a library, the linker will:
>
> 1) if there is a cache, see if it knows about that library in the
> cache;
>
> 2) if no cache, or if not known in the cache, look for ld.so.conf and
> look for that library in all paths listed in there;
>
> 3) if still not found, look in the "well-known" locations, usually
> /usr/lib then /lib (or their variants, depending on the
> mutlilib/multiarch uglyness)
The MAN page for ld.so [1] only refers to /etc/ld.so.cache when ld.so
searches for a library.
> > > - when running a program, ld.so has to explore all the library
> > > paths to find the correct location of the required libraries.
> > > This results in zillions of failed calls to open(), i.e. wasted
> > > time.
>
> Have you actually measured this overhaed?
No. I'll try to get some numbers. I only used strace.
[1] http://man7.org/linux/man-pages/man8/ld.so.8.html
Regards,
--
ELB
prev parent reply other threads:[~2016-06-16 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1722059483.342813959.1466082436418.JavaMail.root@zimbra32-e6.priv.proxad.net>
2016-06-16 13:12 ` [Buildroot] Allowing user to run ldconfig in post-build script Eric Le Bihan
2016-06-16 13:37 ` Thomas Petazzoni
2016-06-16 19:45 ` Eric Le Bihan
2016-06-16 20:28 ` Thomas Petazzoni
2016-06-16 20:34 ` Yann E. MORIN
2016-06-16 21:15 ` Eric Le Bihan
2016-06-23 22:22 ` Arnout Vandecappelle
2016-06-16 19:53 ` Yann E. MORIN
2016-06-16 20:34 ` Thomas Petazzoni
2016-06-16 21:32 ` Eric Le Bihan [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=20160616233257.7a47d276@itchy \
--to=eric.le.bihan.dev@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox