From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Wed, 09 Mar 2016 15:31:23 +0100 Subject: [Buildroot] [PATCH] pkgconf: make wrapper relocatable In-Reply-To: <56E02D83.9020402@zacarias.com.ar> (Gustavo Zacarias's message of "Wed, 9 Mar 2016 11:04:51 -0300") References: <1457529409-24102-1-git-send-email-gustavo@zacarias.com.ar> <87egbj228a.fsf@dell.be.48ers.dk> <56E02A78.1050701@zacarias.com.ar> <87a8m721lk.fsf@dell.be.48ers.dk> <56E02D83.9020402@zacarias.com.ar> Message-ID: <871t7j205g.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Gustavo" == Gustavo Zacarias writes: > On 09/03/16 11:00, Peter Korsgaard wrote: >> 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. > That's overly complicated for no value at all. > You know the sysroot is in the host directory as well, so you just > need to filter out /usr/bin from $0 and hardcode the tuple in the > wrapper - > that's guaranteed to not change, otherwise you're in serious trouble. Yes, that's basically what I'm saying +/- the question if you want to rely on $0 containing the full path to the wrapper or if you use /proc/self/exe instead. -- Venlig hilsen, Peter Korsgaard