All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ross Burton" <ross@burtonini.com>
To: Piotr <piotr.piwko@gmail.com>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] invalid characters in license '${EAT_GCC_LICENSE}'
Date: Mon, 11 Jan 2021 15:03:42 +0000	[thread overview]
Message-ID: <CAAnfSTsnLJ_nd+f335Fj32T6AaZMeFFriystRft0GKKjf4YwsA@mail.gmail.com> (raw)
In-Reply-To: <db7M.1610369317172636984.vXd0@lists.yoctoproject.org>

On Mon, 11 Jan 2021 at 12:48, Piotr <piotr.piwko@gmail.com> wrote:
> I've analyzed that and it seems like there is missing a license.inc including, as it is done in external-arm-toolchain.bb recipe. The same issue occurs with EAT_GDB_LICENSE:

I've not really used the external toolchain support, but license.inc does exist:

meta-arm-toolchain/recipes-devtools/external-arm-toolchain/license.inc:EAT_GCC_LICENSE
= "GPL-3.0-with-GCC-exception & GPLv3"

Ross

  reply	other threads:[~2021-01-11 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 12:48 invalid characters in license '${EAT_GCC_LICENSE}' Piotr
2021-01-11 15:03 ` Ross Burton [this message]
2021-01-11 15:07 ` [meta-arm] " Jon Mason

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=CAAnfSTsnLJ_nd+f335Fj32T6AaZMeFFriystRft0GKKjf4YwsA@mail.gmail.com \
    --to=ross@burtonini.com \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=piotr.piwko@gmail.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.