From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Elvis Dowson <elvis.dowson@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [meta-xilinx] WARNING: linux-xilinx: No generic license file exists for: GPL in any provider
Date: Fri, 01 Jun 2012 11:26:47 +0100 [thread overview]
Message-ID: <4539907.k7xmu0jQ3E@helios> (raw)
In-Reply-To: <D03C46EA-D51F-40C5-9947-0EA7FAE6DD94@gmail.com>
On Thursday 31 May 2012 19:44:41 Elvis Dowson wrote:
> Hi,
> While attempting to build linux-xilinx, I get the following warning:
>
> WARNING: linux-xilinx: No generic license file exists for: GPL in any
> provider
>
> What should I do to fix this warning?
You could ignore it, or you could fix the linux-xilinx recipe. FYI what it's
really saying is "GPL" by itself is not really specific enough. The recipe
should be stating "GPLv2" or "GPLv3" or whichever version the software being
built is really licensed under. Being that it sounds like it's the Linux
kernel one would assume "GPLv2" would be the correct answer for the linux-
xilinx recipe.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-06-01 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 17:44 [meta-xilinx] WARNING: linux-xilinx: No generic license file exists for: GPL in any provider Elvis Dowson
2012-06-01 10:26 ` Paul Eggleton [this message]
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=4539907.k7xmu0jQ3E@helios \
--to=paul.eggleton@linux.intel.com \
--cc=elvis.dowson@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox