From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] host directories in target rpath
Date: Fri, 1 Jan 2016 23:05:49 +0100 [thread overview]
Message-ID: <20160101230549.6cb360cf@free-electrons.com> (raw)
In-Reply-To: <20160101155622.GA20087@vostro>
Dear Alex Suykov,
On Fri, 1 Jan 2016 17:56:23 +0200, Alex Suykov wrote:
> I noticed I have bunch of target executables with host directories in RPATH:
>
> $ readelf -d output/target/usr/bin/aserver | grep RPATH
> 0x0000000f (RPATH) Library rpath: [/home/alex/src/buildroot.snow/output/build/alsa-lib-1.0.29/src/.libs]
>
> $ readelf -d output/target/usr/bin/glib-compile-resources | grep RPATH
> 0x0000000f (RPATH) Library rpath: [/home/alex/src/buildroot.snow/output/build/libglib2-2.46.1/gio/.libs:/home/alex/src/buildroot.snow/output/build/libglib2-2.46.1/gobject/.libs:/home/alex/src/buildroot.snow/output/build/libglib2-2.46.1/gmodule/.libs:/home/alex/src/buildroot.snow/output/build/libglib2-2.46.1/glib/.libs:/home/alex/src/buildroot.snow/output/host/usr/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/lib]
>
> $ readelf -d output/target/usr/bin/weston | grep RPATH
> 0x0000000f (RPATH) Library rpath: [/home/alex/src/buildroot.snow/output/host/usr/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/lib]
>
> It does not break anything, but it's not right either.
> And it makes strace output look rather messy.
>
> A quick way to check it is building alsa-lib, which is where aserver comes from.
>
> The underlying cause is libtool, and for autoreconfed packages I can fix it
> by patching (host-)libtool. This fixes alsa-lib but not weston because weston
> carries that code in its pre-built configure. So I have to either patch weston
> in place (and also every non-autoreconfed package), or autoreconf them all.
>
> What's your thoughts on this? Maybe there are better ways to fix it?
You can see the following patches from Samuel Martin, which aim at
solving this problem:
http://patchwork.ozlabs.org/patch/494781/
http://patchwork.ozlabs.org/patch/494782/
http://patchwork.ozlabs.org/patch/494783/
http://patchwork.ozlabs.org/patch/494784/
http://patchwork.ozlabs.org/patch/494785/
Samuel said he would respin them on top of master and post a new
version of those patches.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-01 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 15:56 [Buildroot] host directories in target rpath Alex Suykov
2016-01-01 22:05 ` Thomas Petazzoni [this message]
2016-01-04 19:43 ` Alex Suykov
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=20160101230549.6cb360cf@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 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.