|| ||Florian Weimer <fw-AT-deneb.enyo.de> |
|| ||Arnaud Charlet <charlet-AT-adacore.com> |
|| ||Re: Compiling programs licensed under the GPL version 2 with GCC 4.4 |
|| ||Sun, 26 Jul 2009 12:18:56 +0200|
|| ||Joe Buck <Joe.Buck-AT-synopsys.COM>, "gcc\@gcc.gnu.org" <gcc-AT-gcc.gnu.org>|
|| ||Article, Thread
* Arnaud Charlet:
>> > If the latter (the license includes something like "either version 2
>> > of the License, or (at your option) any later version"), then
>> > nothing prevents you from distributing the program under GPLv3+
>> > instead of GPLv2+.
>> Right, but we've got some stuff which is GPLv2-only, such as Git,
>> OpenOffice, OpenJDK, etc.
> I guess you should check with FSF lawyers in this case.
Kalle already did that, back in April, and hasn't received any reply.
I haven't received any reply for my request about QPL compilers like
Objective Caml, either.
I would rather ask a lawyer of my own, but this doesn't solve the
issue that we generally want to follow the FSF's wishes and not
stretch things as far as possible under copyright law.
> I suspect that other clauses would apply. For example, assuming that
> the GCC 4.4 run-time is part of the OS (which is likely the case you
> described as far as I understand), then the GPLv2 OS exception
> clause would apply.
It doesn't for someone who ships a complete operating system. Here's
the relevant quote from the GPL, version 2:
| However, as a special exception, the source code distributed need
| not include anything that is normally distributed (in either source
| or binary form) with the major components (compiler, kernel, and so
| on) of the operating system on which the executable runs, unless
| that component itself accompanies the executable.
The FSF claims that it is not permitted to link against arbitrary
libraries when you distribute a program is part of an operating
system. Free software vendors receive advice according these lines,
and the GPL FAQ at <http://www.gnu.org/philosophy/license-list.html>
also reflects that. For instance, it says about the QPL:
| Since the QPL is incompatible with the GNU GPL, you cannot take a
| GPL-covered program and QPL-covered program and link them together,
| no matter how.
This still haunts us today with OpenSSL, which is licensed under a
BSD-style license with an advertizing. It's one reason why we stick
with FSF GNAT in Debian, the GPLed run-time library in AdaCore's
distribution would cause too many licensing headaches.
On the other hand, there is a curious lack of enforcement. Most
proprietary operating system vendors (including Microsoft and Juniper,
apparently) get a free pass in this area. They just link GPL-only GNU
software with their proprietary system libraries and ship the result,
often in the same download or on the same media. This makes me feel
rather bitter. Why do proprietary vendors receive this additional
freedom, but not free software vendors?
If the FSF keeps refusing to enter any discussion on this matter (I'm
not even talking about agreeing on a solution yet!), our options for
dealing with the GCC 4.4 relicensing fallout at Debian are pretty
limited. It's also likely that any unilateral action will undermine
the effect of some of the FSF's licensing policies.
to post comments)