public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Ángel González" <keisial@gmail.com>
Cc: Ian Lance Taylor <iant@google.com>,
	Florian Weimer <fw@deneb.enyo.de>,
	gcc-help@gcc.gnu.org, 	Byron Blue <byron@maqsonar.com>,
	Georg-Johann Lay <gjl@gcc.gnu.org>
Subject: Re: Simple question
Date: Sun, 26 Aug 2012 09:55:00 -0000	[thread overview]
Message-ID: <CAH6eHdRddw=B7jce0eJGfVtQS9zpxz4xF=xcXti+kUkeo0kppw@mail.gmail.com> (raw)
In-Reply-To: <50393CB7.5040607@gmail.com>

On Aug 25, 2012 10:01 PM, "Ángel González" wrote:
>
> That's probably because the Runtime library exception requires an explicit
> notice on affected files. Had the FSF additionally "licensed" that any
> non-GPL
> code compiled with an official release of gcc is subject to that
> exception and
> is not bound to the GPL due to the compilation.

Many (maybe most) people don't use official releases, they use the
version provided by their distro, which might be modified.

The OP asked a simple question and the answer is that using GCC to
compile non-free code is ok.

This thread should have ended there.

  reply	other threads:[~2012-08-25 21:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 13:58 Byron Blue
2012-08-22 14:03 ` Ángel González
2012-08-22 14:35 ` Ian Lance Taylor
2012-08-22 15:21 ` David Brown
2012-08-22 16:39 ` Bob Plantz
2012-08-25 15:57 ` Florian Weimer
2012-08-25 16:05   ` Georg-Johann Lay
2012-08-25 17:30   ` Ian Lance Taylor
2012-08-25 17:55     ` Bob Plantz
2012-08-25 18:20     ` Georg-Johann Lay
2012-08-25 20:37       ` Ian Lance Taylor
2012-08-25 21:01         ` Georg-Johann Lay
2012-08-25 21:23           ` Ian Lance Taylor
2012-08-26  9:13             ` Ángel González
2012-08-26  9:55               ` Jonathan Wakely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-16 19:26 simple question lrtaylor
2004-04-16 19:19 Ramin NIkaeen
2004-04-16 16:40 lrtaylor
2004-04-15 21:43 Ramin NIkaeen
2004-04-15 21:47 ` Andreas Tobler
2004-04-15 21:47 ` Gabriel Dos Reis
2004-04-15 21:48 ` Paolo Carlini
2004-04-16  9:06 ` Houda Benabderrazik
2002-11-27 10:11 cowen
2000-08-08 10:46 RPathiyal
2000-08-08 18:18 ` Alexandre Oliva

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='CAH6eHdRddw=B7jce0eJGfVtQS9zpxz4xF=xcXti+kUkeo0kppw@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=byron@maqsonar.com \
    --cc=fw@deneb.enyo.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gjl@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=keisial@gmail.com \
    /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).