Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master] Revert "Add -rpath option for host package compilation"
Date: Tue, 1 Jun 2010 19:52:04 +0200	[thread overview]
Message-ID: <20100601195204.6353fe94@surf> (raw)
In-Reply-To: <20100530084318.C8A0EC03A6@busybox.osuosl.org>

On Sun, 30 May 2010 10:42:17 +0200
Peter Korsgaard <jacmet@sunsite.dk> wrote:

> This reverts commit 6b939d40f6a29a43277566adc9d4312d49cb3abf.
> 
> The problem this commit tries to fix is valid, but the fix
> unfortunately seems to cause worse problems on certain
> distributions/setups, so revert for now.

As it seems that all HOST_CFLAGS/HOST_LDFLAGS combination have tried do
not work, I've tried another solution: setting the rpath in host
binaries outside of the build process of those binaries.

For this, I've added a new package, patchelf, which is compiled for the
host. And then, everytime a package installs something for the host
(in the $(BUILD_DIR)/%/.stamp_host_installed target in
package/Makefile.package.in), I do:

find $(HOST_DIR)/bin $(HOST_DIR)/usr/bin $(HOST_DIR)/usr/sbin $(HOST_DIR)/sbin -type f -perm +111 -exec $(HOST_DIR)/usr/bin/patchelf --set-rpath $(HOST_DIR)/usr/lib {} \; >/dev/null 2>&1 || true

Would this sort of solution be acceptable ?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-06-01 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-30  8:42 [Buildroot] [git commit master] Revert "Add -rpath option for host package compilation" Peter Korsgaard
2010-06-01 17:52 ` Thomas Petazzoni [this message]
2010-06-01 18:47   ` Peter Korsgaard
2010-06-01 19:18     ` Thomas Petazzoni
2010-06-01 20:10       ` Peter Korsgaard

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=20100601195204.6353fe94@surf \
    --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