ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-18 20:37:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update and clarify COPYING (plus a typo).

Browse Source 
/trunk/COPYING |    9     7     2     0 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)
This commit is contained in:
Yann E. MORIN" 2008-09-14 18:20:03 +00:00
parent 02d2b29cda
commit 894a3cd5ba
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
COPYING
View File

@ -19,7 +19,7 @@ the following terms.
the license the Linux kernel is most commonly available under. the license the Linux kernel is most commonly available under.
As a convenience, the GNU Lesser General Public License (LGPL) v2.1 (for the 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 licenses.d/lgpl.txt
- Other files not covered by the above licenses, and not covered by an - Other files not covered by the above licenses, and not covered by an
@ -38,6 +38,11 @@ the following terms.
> scripts used to control compilation and installation of the executable. > scripts used to control compilation and installation of the executable.
In short: crosstool-NG is the part refered to as "the scripts to control 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 our case; and as such you must make it available, in conformance to the
GPLv2, see above. 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.