Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkgconf: make wrapper relocatable
Date: Wed, 09 Mar 2016 16:55:08 +0100	[thread overview]
Message-ID: <87k2lbzlwj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAHXCMMJS=QknbFiVxvNLKHp0QZi2_LtJ+jnRz-XEYgsfAQh6pw@mail.gmail.com> (Samuel Martin's message of "Wed, 9 Mar 2016 16:22:34 +0100")

>>>>> "Samuel" == Samuel Martin <s.martin49@gmail.com> writes:

Hi,

 >> What about doing this relatively to the wrapper location?
 >> 
 >> WRAPPER_DIR=$(dirname $0)
 >> STAGING_DIR=$(readlink -f ${WRAPPER_DIR}/../../../staging/)
 >> 
 >> and there you are, it is both relocatable and doesn't rely on
 >> STAGING_DIR being defined in the environment.

 > Funny that's close to what I've done in my relocatable sdk branch few
 > days ago...
 > https://github.com/tSed/buildroot/commit/cebeb4f43a44eda8e9c1d2fd9629e9f9deea3f28

Heh, great minds think alike ;)

Something else more-or-less related that I think we should
fix/workaround until the relocatable sdk rpath handling gets integrated
is the issue about the toolchain linking to gmp/mpc/mpfr, and not
finding our libraries when the toolchain is moved.

That is currently quite painful, especially when you want to reuse the
toolchain on different machines/distributions, that may not have
compatible libraries in /usr/lib.

The easiest workaround is just to build our host-gmp/mpc/mpfr statically
for now. This has minimal size impact on the toolchain (< 1MB for a
.tar.gz of output/host).

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2016-03-09 15:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 13:16 [Buildroot] [PATCH] pkgconf: make wrapper relocatable Gustavo Zacarias
2016-03-09 13:46 ` Peter Korsgaard
2016-03-09 13:51   ` Gustavo Zacarias
2016-03-09 14:00     ` Peter Korsgaard
2016-03-09 14:04       ` Gustavo Zacarias
2016-03-09 14:31         ` Peter Korsgaard
2016-03-09 14:37           ` Arnout Vandecappelle
2016-03-09 14:40             ` Gustavo Zacarias
2016-03-09 14:46             ` Peter Korsgaard
2016-03-09 14:52               ` Arnout Vandecappelle
2016-03-09 15:06                 ` Peter Korsgaard
2016-03-09 14:03     ` Thomas Petazzoni
2016-03-09 14:28       ` Gustavo Zacarias
2016-03-09 14:40         ` Arnout Vandecappelle
2016-03-09 14:41           ` Gustavo Zacarias
2016-03-09 14:42           ` Arnout Vandecappelle
2016-03-09 14:30       ` Peter Korsgaard
2016-03-09 14:50         ` Thomas Petazzoni
2016-03-09 14:55           ` Peter Korsgaard
2016-03-09 15:22       ` Samuel Martin
2016-03-09 15:55         ` Peter Korsgaard [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=87k2lbzlwj.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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