From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] insane.bbclass: Make RPATH a non-fatal error
Date: Fri, 18 Feb 2011 12:36:45 -0700 [thread overview]
Message-ID: <4D5ECA4D.4090309@mentor.com> (raw)
In-Reply-To: <1298057187-2466-1-git-send-email-tom_rini@mentor.com>
On 02/18/2011 12:26 PM, Tom Rini wrote:
> In order to make the user experience better we now use bb.warn
> on non-fatal QA errors and bb.error on fatal errors.
Part of my motivation here is that after looking at poky, this error is
_not_ fatal there yet (none are), and until we can kill libtool 2.2.x
(which won't be until oe-core I believe) this is going to be a big
problem to solve, generally involving a libtool hack. I think we can
best spend our time here on fixing RPATH issues that still show up once
we're all using libtool 2.4 (as there will still be a few in 'odd'
packages, but most will now be correct automatically).
I'm going to push this into my simplify-target-flags branch as well and
see what falls out now (doing so already for smaller test cases).
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-02-18 19:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 19:26 [PATCH] insane.bbclass: Make RPATH a non-fatal error Tom Rini
2011-02-18 19:33 ` Khem Raj
2011-02-18 19:36 ` Tom Rini [this message]
2011-02-18 19:53 ` Denys Dmytriyenko
2011-02-18 19:54 ` Eric Bénard
2011-02-18 20:36 ` Eric Benard
2011-02-19 9:45 ` Frans Meulenbroeks
2011-02-19 11:52 ` Andreas Mueller
2011-02-19 13:26 ` Otavio Salvador
2011-02-19 16:59 ` Tom Rini
2011-02-20 12:42 ` Frans Meulenbroeks
2011-02-20 14:46 ` Tom Rini
2011-02-20 14:59 ` Eric Benard
2011-02-20 15:05 ` Andreas Mueller
2011-02-20 15:37 ` Tom Rini
2011-02-20 16:31 ` Frans Meulenbroeks
2011-02-20 16:54 ` Andreas Mueller
2011-02-20 17:56 ` Frans Meulenbroeks
2011-02-20 18:26 ` Frans Meulenbroeks
2011-02-20 18:58 ` Andreas Mueller
2011-02-19 17:33 ` Holger Freyther
2011-02-19 18:27 ` Frans Meulenbroeks
2011-02-20 1:19 ` Tom Rini
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=4D5ECA4D.4090309@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.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 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.