>> |
12/21/11(Wed)14:44 No.21764236>>21764160 This
was posted once on the GCC mailing list by Stallman but he later
changed his mind and decided to "hold off" on such a decision.
>
The fact of the matter is that GCC allowed applications built with it
to remain proprietary simply because we were under the belief that such
programs would likely only be used internally and not distributed. After
all, the GPL only convers distribution of software. Our line of
thinking was that if an end user had access to the source code for a
program to compile it for their system, then that program was likely
free software. This is not always the case today. Microsoft, among
others, have come out with "reference licenses" which allow the user to
view and build software from the source code but the software itself is
inherantly non-free because they violate freedoms 1 and 3. All four
conditions must be met for software to be considered truly free. We can
no longer assume that just because one has access to the source code for
the program that the software is free.
>
I believe it is imperative that this loophole be fixed for GCC 4.7 by
either adding an additional condition to the GCC license specifically or
by releasing GPLv3.1 to close the loophole for all software that
generates binaries, IR/bytecode, or interprets source code at runtime. |