From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9381] New: check-host-rpath issues
Date: Wed, 26 Oct 2016 11:45:54 +0000 [thread overview]
Message-ID: <bug-9381-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9381
Bug ID: 9381
Summary: check-host-rpath issues
Product: buildroot
Version: 2016.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jpcartal at free.fr
CC: buildroot at uclibc.org
Target Milestone: ---
Hello,
It seems that the check-host-rpath script has issues with buildroot paths that
contains links :
jpcartal at florida:buildroot-2016.08$ echo $PWD
/home/jpcartal/Dev/Ssd/buildroot/buildroot-2016.08
jpcartal at florida:buildroot-2016.08$ realpath $PWD
/home/jpcartal/Ssd/buildroot/buildroot-2016.08
jpcartal at florida:buildroot-2016.08$ support/scripts/check-host-rpath toto
$PWD/output/host
***
*** ERROR: package toto installs executables without proper RPATH:
***
/home/jpcartal/Dev/Ssd/buildroot/buildroot-2016.08/output/host/usr/bin/crlutil
***
/home/jpcartal/Dev/Ssd/buildroot/buildroot-2016.08/output/host/usr/bin/arm-buildroot-linux-gnueabihf-ar
....
jpcartal at florida:buildroot-2016.08$ cd $(realpath $PWD)
jpcartal at florida:buildroot-2016.08$ support/scripts/check-host-rpath toto
$PWD/output/host
jpcartal at florida:buildroot-2016.08$
Also it seems that the $ORIGIN ld feature is not supported.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-10-26 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 11:45 bugzilla at busybox.net [this message]
2016-10-26 12:07 ` [Buildroot] [Bug 9381] check-host-rpath issues bugzilla at busybox.net
2016-10-26 12:11 ` bugzilla at busybox.net
2016-10-26 12:22 ` bugzilla at busybox.net
2016-10-27 7:15 ` bugzilla at busybox.net
2016-10-27 7:16 ` bugzilla at busybox.net
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=bug-9381-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.