All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Schoepfer" <matthias.schoepfer@googlemail.com>
To: Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Package libgcc-lic cannot be installed into the image because it has incompatible license(s): GPL-3.0
Date: Fri, 15 May 2020 11:32:15 +0200	[thread overview]
Message-ID: <5e93c06b-61a1-a89c-a2f7-0dadda804be2@googlemail.com> (raw)

Hi!

I am trying to migrate to dunfell. Out customer does not want GPLv3 or 
anything like that on the firmware.

So - same as in zeus - we have a line:

INCOMPATIBLE_LICENSE = "GPLv3 LGPLv3 GPLv3+ LGPLv3+ GPL-3.0 LGPL-3.0 
AGPL-3.0"

during do_rootfs, the process fails with:

do_rootfs: Package libgcc-lic cannot be installed into the image because 
it has incompatible license(s): GPL-3.0

The package basically consists of the license information for libgcc, 
libgcc is allowed due to the linking exception.

Even, when I try to allow this package with something like this:

INCOMPATIBLE_LICENSE_pn-libgcc-lic = ""
INCOMPATIBLE_LICENSE_pn-libgcc = ""

which has worked in the past to have an in house debug image with the 
gdbserver on it, it still fails.

Am I the first to experience this? Am I doing something wrong?

We do

COPY_LIC_MANIFEST = "1"
COPY_LIC_DIRS = "1"
LICENSE_CREATE_PACKAGE = "1"

as well, if that info is needed.

Any help would be appreciated.

Thanks and Regards,

   Matthias


             reply	other threads:[~2020-05-15  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  9:32 Matthias Schoepfer [this message]
2020-05-15 14:46 ` [yocto] Package libgcc-lic cannot be installed into the image because it has incompatible license(s): GPL-3.0 Khem Raj
2020-05-16 14:12   ` Matthias Schoepfer
2020-05-16 14:30     ` Khem Raj

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=5e93c06b-61a1-a89c-a2f7-0dadda804be2@googlemail.com \
    --to=matthias.schoepfer@googlemail.com \
    --cc=yocto@yoctoproject.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.