1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: crosstool-ng
Source: http://crosstool-ng.org/
Files: *
Copyright: 2015 Crosstool-NG Developers
License: GPL-2.0+
/usr/share/common-licenses/GPL-2
Files: debian/*
Copyright:
2015 Andrew 'Necromant' Andrianov <andrew@ncrmnt.org>
2017 Several Candidates <open@example.com>
License: GPL-2.0+
/usr/share/common-licenses/GPL-2
Files: docs/*
Copyright: Various
License: CC-BY-SA-2.5
Files in docs/ are available under the Creative Commons Attribution, Share
Alike (by-sa), v2.5, to be found there:
licenses.d/by-sa/deed.en (human-readable summary)
licenses.d/by-sa/legalcode (legal code, the full license)
Files: patches/*
Copyright: Various
License: Various
Files found in patches/*/ are available under the same license as the
upstream software they apply to.
.
That means that you can't use those patches if you were licensed the
software under a specific license which is not the one the software is
commonly available under.
.
As an example, if you ever managed to get the Linux kernel under a license
other than the GPLv2, you are not allowed to use the Linux kernel patches
coming with crosstool-NG, as those are available under the GPLv2, which is
the license the Linux kernel is most commonly available under.
.
As a convenience, the GNU Lesser General Public License (LGPL) v2.1 (for the
patches against glibc, uClibc, and some other libraries) is available there:
licenses.d/lgpl.txt
.
Other files not covered by the above licenses, and not covered by an
individual license specified in the file itself, or an accompanying file,
are available under the GNU General Public License (GPL), v2, to be found
here:
licenses.d/gpl.txt
.
Also, I want to clarify one point. If you build a toolchain with crosstool-NG
and you happen to sell, deliver, or otherwise publish this toolchain to a
third party, I consider crosstool-NG as being part of the sources needed to
rebuild the afore-mentioned toolchain, alongside with all other source code
that third party is otherwise entitled to receive, due to other licenses of
the different components. See licenses.d/gpl.txt, section 3, which reads:
> For an executable work, complete source code means [...], plus the
> scripts used to control compilation and installation of the executable.
.
In short: crosstool-NG is the part refered to as "the scripts to control
compilation and installation of the executable", it being the toolchain in
our case; and as such you must make it available, in conformance to the
GPLv2, see above.
.
Also, if you have local patches that you apply to the different components
(either manualy, or by instructing crosstool-NG to do so), you will have to
make those patches available alongside with your toolchain, to comply with
the licenses of the components impacted by your patches.
|
