Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8646] check-host-rpath script returns false positives when rpath contains symlink
Date: Wed, 03 Feb 2016 20:10:55 +0000	[thread overview]
Message-ID: <bug-8646-163-VBAn3x7lkx@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8646-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=8646

--- Comment #1 from Samuel Martin <s.martin49@gmail.com> ---
(In reply to Aaron Bamberger from comment #0)

> The path that buildroot is checked out under on our build server contains a 
> symlink (it's checked out under /home, which is actually a symlink to
> /share/home).  After looking at the RUNPATH of the libraries that are 
> triggering the error, it appears that something in the build system is 
> canonicalizing the RUNPATH (it contains /share/home), while the hostdir that 
> the script is checking against has not been canonicalized (it just contains 
> /home).  Therefore, even though the paths are logically the same, the string 
> comparison of the paths in the script returns false.

Indeed, this is a known issue for which a patch fixing it globally in
Buildroot,
is pending in patchwork [1].

[1] http://patchwork.ozlabs.org/patch/576593/

Regards,

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2016-02-03 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 19:50 [Buildroot] [Bug 8646] New: check-host-rpath script returns false positives when rpath contains symlink bugzilla at busybox.net
2016-02-03 20:10 ` bugzilla at busybox.net [this message]
2016-02-03 20:17 ` [Buildroot] [Bug 8646] " bugzilla at busybox.net
2016-02-03 20:20 ` bugzilla at busybox.net
2016-10-20 21:33 ` 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-8646-163-VBAn3x7lkx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox