From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] check-host-rpath: support symlinks in rpath
Date: Wed, 05 Oct 2016 10:54:28 +0200 [thread overview]
Message-ID: <2359483.ncWTPxTSyx@sagittea> (raw)
In-Reply-To: <8fb2b678-db51-9ba7-c07d-d7956c9708db@mind.be>
Hi Arnout,
On Tuesday 04 October 2016 23:33:34 Arnout Vandecappelle wrote:
> On 30-09-16 12:09, J?r?me Pouiller wrote:
> > If compilation path contains symlinks, rpath may sometime contains
> > symlinks and sometime canonicalized path.
> >
> > A pratical example:
> > $ ln -s /opt/buildroot /opt/buildroot-symblink
> > $ cd /opt/buildroot-symlink
> > $ make O=out
> > $ make -C out package-rebuild
> >
> > This last command produce an error since already installed host
> > binaries contains /opt/buildroot/out/host/usr/lib as rpath while
> > check-host-rpath expect /opt/buildroot-symlink/out/host/usr/lib
> >
> > This patch canonicalize all paths used in check-host-rpath in order
> > to avoid problem
>
> Wouldn't this also be fixed by
> http://patchwork.ozlabs.org/patch/613854/ ? With that patch (series)
> applied, there shouldn't be any symlinks anymore once the real make
> starts.
I didn't saw Samuel's patch. I will test it soon. I think it supersede
mine.
BR,
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2016-10-05 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 10:09 [Buildroot] [PATCH 0/2] Symlinks in compilation path confuse check-host-rpath Jérôme Pouiller
2016-09-30 10:09 ` [Buildroot] [PATCH 1/2] check-host-rpath: support symlinks in rpath Jérôme Pouiller
2016-10-04 21:33 ` Arnout Vandecappelle
2016-10-05 8:54 ` Jérôme Pouiller [this message]
2016-10-16 10:58 ` Arnout Vandecappelle
2016-10-16 11:43 ` Samuel Martin
2016-09-30 10:09 ` [Buildroot] [PATCH 2/2] Canonicalize $(BASE_DIR) Jérôme Pouiller
2016-10-03 21:21 ` [Buildroot] [PATCH 0/2] Symlinks in compilation path confuse check-host-rpath 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=2359483.ncWTPxTSyx@sagittea \
--to=jezz@sysmic.org \
--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