yann@425: Unless otherwise stated in individual files, this work is licensed to you under yann@1: the following terms. yann@1: yann@1: - Files in docs/ are available under the Creative Commons Attribution, Share yann@1: Alike (by-sa), v2.5, to be found there: yann@17: licenses.d/by-sa/deed.en (human-readable summary) yann@17: licenses.d/by-sa/legalcode (legal code, the full license) yann@1: yann@191: - Files found in patches/*/ are available under the same license as the yann@338: upstream software they apply to. yann@338: yann@338: That means that you can't use those patches if you were licensed the yann@338: software under a specific license which is not the one the software is yann@338: commonly available under. yann@338: yann@338: As an example, if you ever managed to get the Linux kernel under a license yann@338: other than the GPLv2, you are not allowed to use the Linux kernel patches yann@338: coming with crosstool-NG, as those are available under the GPLv2, which is yann@338: the license the Linux kernel is most commonly available under. yann@338: yann@338: As a convenience, the GNU Lesser General Public License (LGPL) v2.1 (for the yann@853: patches against glibc, uClibc, and some other libraries) is available there: yann@338: licenses.d/lgpl.txt yann@1: yann@1: - Other files not covered by the above licenses, and not covered by an yann@1: individual license specified in the file itself, or an accompanying file, yann@1: are available under the GNU General Public License (GPL), v2, to be found yann@1: here: yann@17: licenses.d/gpl.txt yann@676: yann@676: - Also, I want to clarify one point. If you build a toolchain with crosstool-NG yann@676: and you happen to sell, deliver, or otherwise publish this toolchain to a yann@676: third party, I consider crosstool-NG as being part of the sources needed to yann@676: rebuild the afore-mentioned toolchain, alongside with all other source code yann@676: that third party is otherwise entitled to receive, due to other licenses of yann@676: the different components. See licenses.d/gpl.txt, section 3, which reads: yann@676: > For an executable work, complete source code means [...], plus the yann@676: > scripts used to control compilation and installation of the executable. yann@676: yann@676: In short: crosstool-NG is the part refered to as "the scripts to control yann@853: compilation and installation of the executable", it being the toolchain in yann@676: our case; and as such you must make it available, in conformance to the yann@676: GPLv2, see above. yann@853: yann@853: Also, if you have local patches that you apply to the different components yann@853: (either manualy, or by instructing crosstool-NG to do so), you will have to yann@853: make those patches available alongside with your toolchain, to comply with yann@853: the licenses of the components impacted by your patches.