From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Strange system library search paths with OSELAS.Toolchain
Date: Tue, 9 Feb 2016 17:42:31 +0100 [thread overview]
Message-ID: <20160209164231.GA927@archie.tuxnet.lan> (raw)
In-Reply-To: <201602091031.23326.jbe@pengutronix.de>
Hi Juergen,
On Tue, Feb 09, 2016 at 10:31:22AM +0100, Juergen Borleis wrote:
> <path/to/toolchain>/sysroot-<toolchain-name>/sbin/ldconfig
Very nice, thank you! After running ldconfig on the target, running strace
with /bin/true shows only one access for /etc/ld.so.preload before using
the /etc/ld.so.cache successfully. That's a major improvement! Nearly 30
syscalls less, per process :)
Now I'll just write a little ptxdist rule to call ldconfig once at
initialization (or at every startup? Some distros seem to do that.)
If I ever want to support running opkg on the target, I should probably
have a mechanism to automatically rerun ldconfig in case a library was
changed.
> > I am curious: Do you also see those weird runtime paths on your ptxdist
> > projects or is there something wrong with my toolchain / bsp build?
>
> I saw these search paths on almost every system, independent of the
> distribution (embedded or not).
Maybe we could add a rule to ptxdist to run ldconfig by default on the
target? Assuming that saving syscalls is beneficial for everybody?
Cheers,
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-02-09 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 15:33 Clemens Gruber
2016-02-08 8:58 ` Juergen Borleis
2016-02-09 0:04 ` Clemens Gruber
2016-02-09 9:31 ` Juergen Borleis
2016-02-09 16:42 ` Clemens Gruber [this message]
2016-02-11 12:10 ` Michael Olbrich
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=20160209164231.GA927@archie.tuxnet.lan \
--to=clemens.gruber@pqgruber.com \
--cc=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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