From: Juergen Borleis <jbe@pengutronix.de>
To: Clemens Gruber <clemens.gruber@pqgruber.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Strange system library search paths with OSELAS.Toolchain
Date: Tue, 9 Feb 2016 10:31:22 +0100 [thread overview]
Message-ID: <201602091031.23326.jbe@pengutronix.de> (raw)
In-Reply-To: <20160209000420.GA28413@archie.tuxnet.lan>
Hi Clemens,
On Tuesday 09 February 2016 01:04:21 Clemens Gruber wrote:
> On Mon, Feb 08, 2016 at 09:58:58AM +0100, Juergen Borleis wrote:
> > On Saturday 06 February 2016 16:33:55 Clemens Gruber wrote:
> > > [...]
> > > stat64("/lib/vfp", 0x7eb4d6c0) = -1 ENOENT (No such file or directory)
> > > open("/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
> >
> > Try to run "ldconfig" on your target and re-check. With some tricks you
> > can do this with ptxdist at build time as well.
>
> do you have an idea on how to disable those paths at toolchain build
> time so that I do not even have to run ldconfig on every target?
Sorry, no idea.
> If there are ptxdist rules for building ldconfig (and running it on the
> target / during targetinstall) this would help a lot.
> So far, I did not find anything in the upstream OSELAS.Toolchain rules
> for glibc. I'll look into adapting the OSELAS.Toolchain build process to
> include ldconfig or change the default search paths.
<path/to/toolchain>/sysroot-<toolchain-name>/sbin/ldconfig
> 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).
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-02-09 9:31 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 [this message]
2016-02-09 16:42 ` Clemens Gruber
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=201602091031.23326.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=clemens.gruber@pqgruber.com \
--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