public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Robert Dewar <dewar@adacore.com>
Cc: Florian Weimer <fw@deneb.enyo.de>,
	Paolo Bonzini <bonzini@gnu.org>,
	        Joe Buck <Joe.Buck@synopsys.COM>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Compiling programs licensed under the GPL version 2 with GCC  4.4
Date: Mon, 27 Jul 2009 14:29:00 -0000	[thread overview]
Message-ID: <y0mws5uxkun.fsf@fche.csb> (raw)
In-Reply-To: <4A6D98F5.2080306@adacore.com> (Robert Dewar's message of "Mon, 27 Jul 2009 08:09:25 -0400")

Robert Dewar <dewar@adacore.com> writes:

> [...]
>>> b) you should ignore all such discussions, since they invariablly
>>>    include lots of legal-sounding opinions from people who are not
>>>    lawyers and don't know, and often have significant misconceptions.
>>
>> This is not about legal issues.  It's about FSF policy.  [...]

(Perhaps this was a poorly chosen summary sentence; Florian's next
paragraph more clearly asks the GCC developers' opinion:

# It seems to me that the new GCC run-time library license has the
# side effect of forcing GPLed software to upgrade to GPL version 3 to
# remain redistributable in compiled form.  If this is not your intent
# (as GCC developers), I think the Steering Committee should ask the
# FSF for official clarification on this matter.


> Discussion of FSF policy on licensing issues is also off-topic for
> this mailing list.

Perhaps, yet the libgcc exception licensing issues were quite
prominently discussed right here, and not too many months ago.
Florian's concern sounds linearly connected to that.  If this is as
trivial a matter as some people seem to hint, perhaps someone can
supply a link to a prior discussion for it.


- FChE

  reply	other threads:[~2009-07-27 14:29 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
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 [this message]
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=y0mws5uxkun.fsf@fche.csb \
    --to=fche@redhat.com \
    --cc=Joe.Buck@synopsys.COM \
    --cc=bonzini@gnu.org \
    --cc=dewar@adacore.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).