|
|
|
@ -19,7 +19,7 @@ the following terms.
@@ -19,7 +19,7 @@ the following terms.
|
|
|
|
|
the license the Linux kernel is most commonly available under. |
|
|
|
|
|
|
|
|
|
As a convenience, the GNU Lesser General Public License (LGPL) v2.1 (for the |
|
|
|
|
glibc, uClibc, and some other libraries) is available there: |
|
|
|
|
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 |
|
|
|
@ -38,6 +38,11 @@ the following terms.
@@ -38,6 +38,11 @@ the following terms.
|
|
|
|
|
> 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 exectuable", it being the toolchain in |
|
|
|
|
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. |
|
|
|
|