All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] legal info: saving of external toolchain
Date: Thu, 10 Oct 2013 23:04:58 +0200	[thread overview]
Message-ID: <20131010230458.78e1a857@skate> (raw)
In-Reply-To: <CAAXf6LXAP+nsmMm7fp0_xvzLNT8cAYof4DECUYhpSs1RzE3Zeg@mail.gmail.com>

Dear Thomas De Schampheleire,

On Thu, 10 Oct 2013 16:51:41 +0200, Thomas De Schampheleire wrote:

> The legal info infrastructure currently does not do anything for the
> toolchain, for 'technical reasons'. I can't recall what these
> technical reasons where. At least for external toolchains I don't see
> a big problem to copy the toolchain also in the sources/ subdirectory.
> The developer then still has the obligation to also provide the
> sources that accompany this binary distribution of the toolchain
> (which is impossible for buildroot to do), but at least the binary
> version is already taken care of.
> 
> In fact, the legal-info target already calls toolchain-legal-info, but
> it does not do anything really.
> 
> What do you think about implementing this for external toolchains (at
> least)? The fact that the toolchain is now using the package
> infrastructure probably makes that a tad easier.

I do agree. The primary reason I turned the toolchain backends into
package was precisely to be able to leverage all the goodness of the
package infrastructure: source, external-deps and legal-info.

Note that you're only mentioning external toolchains, but it also
applies to the internal toolchain: verifying that we have proper
licensing information on mpfr, gmp, mpc, gcc, glibc, eglibc, uclibc,
binutils would be good.

For external toolchains it's a little bit more complicated, because the
tarballs are actually pre-compiled binaries. To comply with the
license, we would have to add a mechanism to also download the source
code of the external toolchain. For example, for the Sourcery CodeBench
ARM toolchain, the source is in
http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/arm-2013.05-24-arm-none-linux-gnueabi.src.tar.bz2.
But we don't really have a good way of encoding that in Buildroot at
the moment, I'm afraid.

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2013-10-10 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 14:51 [Buildroot] legal info: saving of external toolchain Thomas De Schampheleire
2013-10-10 20:37 ` Luca Ceresoli
2013-10-10 21:04 ` Thomas Petazzoni [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=20131010230458.78e1a857@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.