From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] python3: Compile host-python3 statically
Date: Fri, 23 Sep 2016 23:14:18 +0200 [thread overview]
Message-ID: <20160923231418.0c2c0c3c@free-electrons.com> (raw)
In-Reply-To: <CAA=pTTTiF11gkQzUN6n9yX+aNUZaZiRicKZa2ieF=W92yvLeFg@mail.gmail.com>
Hello,
On Fri, 23 Sep 2016 16:10:41 +0000, Frederik Peter Aalund wrote:
> I noticed that while the host-python executable doesn't have an rpath
> value, it does have a runpath value:
>
> Tag Type Name/Value
> 0x0000000000000001 (NEEDED) Shared library:
> [libpython3.5m.so.1.0]
> 0x0000000000000001 (NEEDED) Shared library: [libpthread.so.0]
> 0x0000000000000001 (NEEDED) Shared library: [libc.so.6]
> 0x000000000000001d (RUNPATH) Library runpath:
> [/projects/RedPitaya/OS/buildroot/buildroot/output/host/usr/lib]
> 0x000000000000000c (INIT) 0x4008c0
Interesting. We are passing -Wl,-rpath, so it should be a rpath. Not
sure why it gets turned into a runpath :/
> Turns out that I had LD_LIBRARY_PATH defined which overrides runpath
> (though not rpath). After undefining LD_LIBRARY_PATH, everything worked.
Ah, yes, indeed. But as said above, we're supposed to have a rpath in
all binaries installed in output/host/usr/bin, so having a runpath here
is not expected.
However, it at least explains why you were seeing the problem, while
many other people were using host-python3 without any problem.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-09-23 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:30 [Buildroot] [PATCH 3/3] python3: Compile host-python3 statically Frederik Aalund
2016-09-16 17:08 ` Thomas Petazzoni
2016-09-20 13:57 ` Frederik Peter Aalund
2016-09-23 16:10 ` Frederik Peter Aalund
2016-09-23 21:14 ` Thomas Petazzoni [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=20160923231418.0c2c0c3c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox