4 ms·
So why not just make that part of the license? Just require any tool that uses the GCC API, even transitively, to be licensed under something GPL compatible. I
by Spivak 12y ago
So why not just make that part of the license? Just require any tool that uses the GCC API, even transitively, to be licensed under something GPL compatible. I know there would probably be a huge number of loopholes to plug but this is really something that should be fixed outside of the actual code.
- cozzyd 12y agoI was thinking the same thing. Change the GCC license to preclude such use by introducing a variant of the GPL for compilers and similar tools.
- jeremysalwen 12y agoLinked from the original article is another piece by the author describing precisely such a license: http://ebb.org/bkuhn/blog/2009/01/27/gcc-exception.html http://ebb.org/bkuhn/blog/2009/01/27/gcc-exception.html . I'm rather surprised I haven't heard of this before.
- belorn 12y agoLikely because it would be incompatible with GPL. Switching GCC's license to a GPL incompatible license is not a move I think FSF are willing to do.