From: Andy Ross <andy.ross@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] base/license.bbclass: handle multiple INCOMPATIBLE_LICENSEs
Date: Wed, 05 Dec 2012 21:52:49 -0800 [thread overview]
Message-ID: <50C032B1.90501@windriver.com> (raw)
In-Reply-To: <50C02651.30201@linux.intel.com>
On 12/05/2012 09:00 PM, Saul Wold wrote:
> This patch is still having problems, see the Autobuilder recently build (link below). This is on MUT with the updated binutils, I am not sure if that is part of the problem or not, but binutils was working before.
Ah, fun fun. It's not binutils. Something (I'm not sure what -- is
"yocto-autobuild" a recipe?) is pulling in the cross-canadian
toolchain, and I had missed the appended architecture in the
license.bbclass test. I'll get you a fixed and tested patch tomorrow
morning.
But there's a serious question here: *should* this have worked? The
toolchain is GPLv3, and a canadian cross toolchain is presumably
intended to be distributed (because by defintion, it doesn't run on
the local machine), no?
Andy
next prev parent reply other threads:[~2012-12-06 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 19:08 [PATCH 0/1] base/license: Incompatible License fixes Elizabeth Flanagan
2012-11-29 19:08 ` [PATCH 1/1] base/license.bbclass: handle multiple INCOMPATIBLE_LICENSEs Elizabeth Flanagan
2012-11-30 4:31 ` Saul Wold
2012-11-30 16:47 ` Andy Ross
2012-12-03 18:47 ` Saul Wold
2012-12-03 18:54 ` Andy Ross
2012-12-06 5:00 ` Saul Wold
2012-12-06 5:52 ` Andy Ross [this message]
2012-12-06 18:41 ` 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=50C032B1.90501@windriver.com \
--to=andy.ross@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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.