From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkgconf: make wrapper relocatable
Date: Wed, 09 Mar 2016 15:00:07 +0100 [thread overview]
Message-ID: <87a8m721lk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <56E02A78.1050701@zacarias.com.ar> (Gustavo Zacarias's message of "Wed, 9 Mar 2016 10:51:52 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Hi,
>> Ehh, doesn't this break using pkg-config outside buildroot?
> Hi.
> Indeed it does, but you can't have the cake and eat it at once can you?
Well, we cannot really break existing features to add new ones. The
relative location between the pkg-config wrapper script and the staging
directory is constant (or rather known at build time), so I guess we can
do something with /proc/self/exe. We might need to implement the wrapper
in C instead for that to work as /proc/self/exe for a shell script seems
to return /bin/dash here.
> Arnout in the famous vala-wrapper thread pointed that we shouldn't
> hardcode the staging directory in it and i've adjusted accordingly, so
> which way is it? (same logic would apply to both cases). Re:
> http://lists.busybox.net/pipermail/buildroot/2016-February/153671.html
> Regards.
I know people today are already using the pkg-config wrapper outside
buildroot (E.G. the output/host dir is used as a sdk), so we imho cannot
break that.
It would be nice to also fix it for vala-wrapper, but as it hasn't
worked before it is atleast not a regression if it doesn't work.
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-03-09 14:00 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 [this message]
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
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=87a8m721lk.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