public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <Joe.Buck@synopsys.COM>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Compiling programs licensed under the GPL version 2 with GCC 4.4
Date: Sun, 26 Jul 2009 21:51:00 -0000	[thread overview]
Message-ID: <20090726215044.GA21312@synopsys.com> (raw)
In-Reply-To: <87y6qc0wmc.fsf@mid.deneb.enyo.de>


> * Joe Buck:
> 
On Sat, Jul 25, 2009 at 01:53:40PM -0700, Florian Weimer wrote:
> >> Kalle Olavi Niemitalo discovered that as an operating system vendor,
> >> you are not allowed to distribute GPL version 2 programs if they are
> >> compiled with GCC 4.4.  The run-time library is GPL version 3 or
> >> later, which is incompatible with GPL version 2, so it is not
> >> permitted to link this with the GPLv2-only program and distribute the
> >> result.

I wrote:
> > That's incorrect.  The runtime library is GPLv3 or later, but with an
> > *exception* that permits linking not only with GPLv2 programs, but
> > also with proprietary programs.

On Sat, Jul 25, 2009 at 11:46:51PM -0700, Florian Weimer wrote:
> Eh, this exception doesn't change that the GPLv2 program perceives the
> GPLv3 as incompatible.  Why would it?

Doesn't matter, because the runtime library is not under GPLv3.  It's
under GPLv3 plus the runtime restriction.  That combination is more
permissive than GPLv2 (because of the exceptions it makes).  Therefore,
as far as I can tell, there is no conflict; the combined program has
no restrictions beyond the GPLv2 restrictions.

In particular, the DRM rules don't apply; the more restrictive rules
on patents don't apply.  Unless you can identify a specific restriction
that isn't waived by the runtime exception license, then I don't see
the problem.

  parent reply	other threads:[~2009-07-26 21:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25 20:53 Florian Weimer
2009-07-26  1:57 ` Joe Buck
2009-07-26  6:47   ` Florian Weimer
2009-07-26  9:38     ` Arnaud Charlet
2009-07-26  9:51       ` Florian Weimer
2009-07-26  9:56         ` Arnaud Charlet
2009-07-26 10:19           ` Florian Weimer
2009-07-26 21:51     ` Joe Buck [this message]
2009-07-27  6:10       ` Florian Weimer
2009-07-27  7:08         ` Paolo Bonzini
2009-07-27  9:35           ` Florian Weimer
2009-07-27  9:41             ` Alfred M. Szmidt
2009-07-27 10:07             ` Robert Dewar
2009-07-27 10:10               ` Paolo Bonzini
2009-07-27 10:28               ` Manuel López-Ibáñez
2009-07-27 11:05                 ` Alfred M. Szmidt
2009-07-27 12:19                   ` Manuel López-Ibáñez
2009-07-27 10:38               ` Dave Korn
2009-07-27 12:12                 ` Robert Dewar
2009-07-27 11:02               ` Florian Weimer
2009-07-27 12:10                 ` Robert Dewar
2009-07-27 14:29                   ` Frank Ch. Eigler
2009-07-28  0:34                     ` Russ Allbery
2009-07-28  0:57                       ` Joe Buck
2009-07-26  7:12   ` Vincent Lefevre
2009-07-27 21:47 ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090726215044.GA21312@synopsys.com \
    --to=joe.buck@synopsys.com \
    --cc=fw@deneb.enyo.de \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).