Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andy Ross <andy.ross@windriver.com>
To: openembedded-core@openembedded.org
Subject: [PATCH] Fix RPATH warning vs. weird paths
Date: Wed, 15 Aug 2012 15:46:21 -0700	[thread overview]
Message-ID: <1345070782-4518-1-git-send-email-andy.ross@windriver.com> (raw)

We hit some oddball cases where libraries were being built with RPATHs
referencing host directores and causing version skew in builds.  There
is a warning case to detect that already, but it was being fooled by
".." terms in the path strings.  This just adds a normalize step to
the path comparison and unmasks the missing warnings.

Andy




             reply	other threads:[~2012-08-15 22:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 22:46 Andy Ross [this message]
2012-08-15 22:46 ` [PATCH] insane.bbclass: Fix RPATH warning in the face of funny path strings Andy Ross
2012-08-16  0:14   ` Chris Larson
2012-08-16 16:10     ` Andy Ross
2012-08-16 16:10       ` Andy Ross
2012-08-16  8:39   ` Phil Blundell
2012-08-16 17:43     ` Andy Ross
2012-08-17 10:28       ` Richard Purdie
2012-08-17 15:02         ` Andy Ross

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=1345070782-4518-1-git-send-email-andy.ross@windriver.com \
    --to=andy.ross@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-core@openembedded.org \
    /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