From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] External Toolchain: Calculation of SYSROOT_DIR in toolchain/toolchain-external/ext-tool.mk wrong?
Date: Wed, 1 Feb 2012 15:15:57 +0000 (UTC) [thread overview]
Message-ID: <jgbkvc$o5a$1@dough.gmane.org> (raw)
In-Reply-To: 20120201140155.67edc41c@skate
On 2012-02-01, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Le Wed, 1 Feb 2012 13:30:01 +0100,
> "Warlich, Christof" <christof.warlich@siemens.com> a ??crit :
>
>> I fully agree with you, but when I talked about the amount of effort, I
>> was referring to the effort that it would take me to convince management
>> to give away that code. I know from earlier experience how much (useless)
>> energy that may take.
>
> Ok. Do your management realize that a toolchain is mostly composed of
> gcc, binutils, uClibc and gdb, that all of these are distributed under
> GPL or LGPL licenses, and therefore you have to keep the source code
> open for those components in order to comply with their licenses?
For most of the toolchain, that's only true if they distribute
binaries. Which they apparently do not do. As long as they don't
distribute binaries of gcc, binutils, gdb, then they can keep the
sources to themselves can't they?
--
Grant Edwards grant.b.edwards Yow! I have a VISION! It's
at a RANCID double-FISHWICH on
gmail.com an ENRICHED BUN!!
next prev parent reply other threads:[~2012-02-01 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 8:35 [Buildroot] External Toolchain: Calculation of SYSROOT_DIR in toolchain/toolchain-external/ext-tool.mk wrong? Warlich, Christof
2012-02-01 9:38 ` Thomas Petazzoni
2012-02-01 11:20 ` Warlich, Christof
2012-02-01 11:34 ` Thomas Petazzoni
2012-02-01 12:30 ` Warlich, Christof
2012-02-01 13:01 ` Thomas Petazzoni
2012-02-01 15:15 ` Grant Edwards [this message]
2012-02-01 15:48 ` Warlich, Christof
2012-02-01 15:25 ` Warlich, Christof
2012-02-01 16:16 ` Michael S. Zick
2012-02-01 15:05 ` Thomas De Schampheleire
2012-02-01 15:41 ` Warlich, Christof
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='jgbkvc$o5a$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox