From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] binutils: add license information
Date: Fri, 17 Apr 2020 14:16:58 +0200 [thread overview]
Message-ID: <20200417121658.lbwcbb7dgeltvhay@pengutronix.de> (raw)
In-Reply-To: <20200417073935.GA8984@pengutronix.de>
On Fri, Apr 17, 2020 at 09:39:35AM +0200, Michael Tretter wrote:
> On Fri, Apr 17, 2020 at 08:47:34AM +0200, Michael Olbrich wrote:
> > On Thu, Apr 16, 2020 at 10:43:19AM +0200, Michael Tretter wrote:
> > > Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> > > ---
> > > rules/binutils.make | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/rules/binutils.make b/rules/binutils.make
> > > index ca1080bc811d..094347e3f8bf 100644
> > > --- a/rules/binutils.make
> > > +++ b/rules/binutils.make
> > > @@ -22,6 +22,7 @@ BINUTILS_SUFFIX := tar.bz2
> > > BINUTILS_URL := $(call ptx/mirror, GNU, binutils/$(BINUTILS).$(BINUTILS_SUFFIX))
> > > BINUTILS_SOURCE := $(SRCDIR)/$(BINUTILS).$(BINUTILS_SUFFIX)
> > > BINUTILS_DIR := $(BUILDDIR)/$(BINUTILS)
> > > +BINUTILS_LICENSE := GPL-2.0-or-later AND GPL-3.0-or-later AND LGPL-2.0-or-later AND LGPL-3.0-or-later
> >
> > No. The version is derived from the toolchain, so we cannot be sure that
> > this is always correct. What we need to do is export the license
> > information in the toolchain and import it here when possible. We already
> > do the same thing for glibc and gcclibs.
>
> Hm. The difference between glibc/gcclibs and the binutils is that for binutils
> only the version is extracted from the toolchain and the binutils are build
> from source in the BSP. Thus, we could also extract the license information
> from the downloaded source code, which would be the same license as in the
> toolchain. I'm not sure if this is actually simpler than exporting the
> license information in the toolchain.
In any case, the respective _LICENSE_FILES variable should be set
somewhere too.
- Roland
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-04-17 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 8:43 Michael Tretter
2020-04-17 6:47 ` Michael Olbrich
2020-04-17 7:13 ` [ptxdist] [TOOLCHAIN PATCH] cross-binutils: export license for binutils package Michael Olbrich
2020-04-17 7:39 ` [ptxdist] [PATCH] binutils: add license information Michael Tretter
2020-04-17 12:16 ` Roland Hieber [this message]
2020-04-17 12:23 ` Michael Olbrich
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=20200417121658.lbwcbb7dgeltvhay@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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