From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] insane bbclass: extend RPATH check to cover sysroots as well
Date: Tue, 25 Jan 2011 17:12:22 +0100 [thread overview]
Message-ID: <20110125161222.GG3616@jama> (raw)
In-Reply-To: <ihmnv8$n3g$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Tue, Jan 25, 2011 at 03:50:16PM +0100, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 25-01-11 15:40, Frans Meulenbroeks wrote:
> > 2011/1/25 Koen Kooi <k.kooi@student.utwente.nl>:
> > On 20-01-11 08:10, Koen Kooi wrote:
> >>>> On 19-01-11 20:35, Philip Balister wrote:
> >>>>> On 01/19/2011 11:21 AM, Koen Kooi wrote:
> >>>>>> * Having rpath to sysroot is just as bad as one to workdir
> >>>>
> >>>>> When you do a build with this, how many recipes have issues?
> >>>>
> >>>> Console-image is clean now :)
> >
> > And angstrom-gnome-image as well, so can I get some Acks or tested-bys
> > please?
> >
> >> NAK, I feel other distro's like shr and minimal should be given some
> >> time to test this too.
>
> Martin has already Acked it, fwiw
Yes, I think that if it says something it's broken then it's broken and
needs to be fixed, haven't seen any false positives with it, that's why
I Acked it.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2011-01-25 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 19:21 [PATCH] insane bbclass: extend RPATH check to cover sysroots as well Koen Kooi
2011-01-19 19:35 ` Philip Balister
2011-01-19 19:58 ` Koen Kooi
2011-01-20 7:10 ` Koen Kooi
2011-01-25 13:41 ` Koen Kooi
2011-01-25 14:38 ` Martin Jansa
2011-01-25 14:40 ` Frans Meulenbroeks
2011-01-25 14:50 ` Koen Kooi
2011-01-25 15:31 ` Frans Meulenbroeks
2011-01-25 22:21 ` Frans Meulenbroeks
2011-01-25 16:12 ` Martin Jansa [this message]
2011-01-26 18:20 ` Frans Meulenbroeks
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=20110125161222.GG3616@jama \
--to=martin.jansa@gmail.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.