From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next v6 07/10] core: implement per-package SDK and target
Date: Thu, 27 Dec 2018 17:17:59 +0100 [thread overview]
Message-ID: <20181227171759.0118ff77@windsurf> (raw)
In-Reply-To: <20181226183422.76c6ff6c@windsurf.home>
Hello,
On Wed, 26 Dec 2018 18:34:22 +0100, Thomas Petazzoni wrote:
> So, without per-package directory, we fall in case (2) above.
>
> With per-package directory, we fall in case (4) above, and therefore
> the RPATH is discarded.
>
> At this point, I am not sure at which level and how the issue should be
> fixed. Needs some thought. Input/ideas welcome.
So for now, the way I fixed this is by rewriting the RPATH in fix-rpath
so that they don't point to per-package host directories. It is a bit
annoying that we end up rewriting RPATHs twice, but it is the easiest /
most straightforward solution to be able to move forward with the whole
per-package directory stuff.
Here is what I have locally:
diff --git a/support/scripts/fix-rpath b/support/scripts/fix-rpath
index fa138ca15a..67bf1eb1b3 100755
--- a/support/scripts/fix-rpath
+++ b/support/scripts/fix-rpath
@@ -127,14 +127,24 @@ main() {
while read file ; do
# check if it's an ELF file
- if ${PATCHELF} --print-rpath "${file}" > /dev/null 2>&1; then
- # make files writable if necessary
- changed=$(chmod -c u+w "${file}")
- # call patchelf to sanitize the rpath
- ${PATCHELF} --make-rpath-relative "${rootdir}" ${sanitize_extra_args[@]} "${file}"
- # restore the original permission
- test "${changed}" != "" && chmod u-w "${file}"
+ rpath=$(${PATCHELF} --print-rpath "${file}" 2>&1)
+ if test $? -ne 0 ; then
+ continue
fi
+
+ # make files writable if necessary
+ changed=$(chmod -c u+w "${file}")
+
+ # rewrite the per-package rpaths
+ changed_rpath=$(echo ${rpath} | sed "s@${PER_PACKAGE_DIR}/[^/]*/host@${HOST_DIR}@")
+ if test "${rpath}" != "${changed_rpath}" ; then
+ ${PATCHELF} --set-rpath ${changed_rpath} "${file}"
+ fi
+
+ # call patchelf to sanitize the rpath
+ ${PATCHELF} --make-rpath-relative "${rootdir}" ${sanitize_extra_args[@]} "${file}"
+ # restore the original permission
+ test "${changed}" != "" && chmod u-w "${file}"
done < <(find "${rootdir}" ${find_args[@]})
# Restore patched patchelf utility
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-27 16:17 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 14:58 [Buildroot] [PATCH next v6 00/10] Per-package host/target directory support Thomas Petazzoni
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 01/10] Makefile: evaluate CCACHE and HOST{CC, CXX} at time of use Thomas Petazzoni
2018-11-26 18:14 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 02/10] support/scripts/check-host-rpath: split condition on two statements Thomas Petazzoni
2018-11-26 18:14 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 03/10] Makefile: rework main directory creation logic Thomas Petazzoni
2018-11-23 18:07 ` Yann E. MORIN
2018-11-26 18:14 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 04/10] Makefile: move .NOTPARALLEL statement after including .config file Thomas Petazzoni
2018-11-26 18:15 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 05/10] Makefile: define TARGET_DIR_WARNING_FILE relative to TARGET_DIR Thomas Petazzoni
2018-11-26 18:15 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 06/10] package/pkg-generic: adjust config scripts tweaks for per-package directories Thomas Petazzoni
2018-11-23 18:09 ` Yann E. MORIN
2018-11-26 18:15 ` Peter Korsgaard
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 07/10] core: implement per-package SDK and target Thomas Petazzoni
2018-11-23 21:50 ` Yann E. MORIN
2018-12-04 22:24 ` Arnout Vandecappelle
2018-12-05 8:04 ` Thomas Petazzoni
2018-12-05 9:18 ` Arnout Vandecappelle
2018-12-05 9:44 ` Thomas Petazzoni
2018-12-05 10:41 ` Arnout Vandecappelle
2018-12-05 16:08 ` Andreas Naumann
2018-12-05 16:31 ` Thomas Petazzoni
2018-12-05 16:52 ` Andreas Naumann
2018-12-06 10:21 ` Andreas Naumann
2018-12-06 10:28 ` Thomas Petazzoni
2018-12-06 10:42 ` Andreas Naumann
2018-12-06 10:58 ` Thomas Petazzoni
2018-12-06 13:31 ` Andreas Naumann
2018-12-26 17:34 ` Thomas Petazzoni
2018-12-26 18:33 ` Thomas De Schampheleire
2019-01-10 21:25 ` Arnout Vandecappelle
2019-01-11 20:09 ` Thomas De Schampheleire
2019-01-13 22:10 ` Arnout Vandecappelle
2019-01-14 16:01 ` Thomas De Schampheleire
2019-01-14 16:33 ` Thomas Petazzoni
2019-01-14 20:19 ` Thomas De Schampheleire
2019-01-14 20:43 ` Thomas De Schampheleire
2018-12-26 18:58 ` Yann E. MORIN
2018-12-27 16:17 ` Thomas Petazzoni [this message]
2019-01-10 21:14 ` Arnout Vandecappelle
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 08/10] Makefile: allow top-level parallel build with BR2_PER_PACKAGE_DIRECTORIES=y Thomas Petazzoni
2018-11-23 18:11 ` Yann E. MORIN
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 09/10] package/pkg-generic: make libtool .la files compatible with per-package directories Thomas Petazzoni
2018-11-25 17:57 ` Yann E. MORIN
2018-11-30 10:20 ` Thomas Petazzoni
2018-12-01 10:59 ` Yann E. MORIN
2018-11-23 14:58 ` [Buildroot] [PATCH next v6 10/10] package/pkg-kconfig: handle KCONFIG_DEPENDENCIES " Thomas Petazzoni
2018-11-25 17:57 ` Yann E. MORIN
2018-12-05 15:23 ` Andreas Naumann
2018-12-06 14:07 ` Andreas Naumann
2018-12-06 14:25 ` Thomas Petazzoni
2018-12-26 16:40 ` Thomas Petazzoni
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=20181227171759.0118ff77@windsurf \
--to=thomas.petazzoni@bootlin.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