public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: emile.fortes@free.fr
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GPLv3 runtime exception : libstdc++
Date: Wed, 25 Mar 2020 12:43:48 +0000	[thread overview]
Message-ID: <CAH6eHdRGyCz6+8AW9oGeTOPUDbN8kmBkpmBtD8NfYp+UTRDtxA@mail.gmail.com> (raw)
In-Reply-To: <87k138r9ez.fsf@mid.deneb.enyo.de>

On Wed, 25 Mar 2020 at 10:57, Florian Weimer wrote:
>
> * emile fortes:
>
> > Does the gplv3 exception allows us to use libstdc++ in proprietary
> > software , WHITOUT having to "...provide whatever information or
> > data necessary to install modified software on the device..."
>
> This depends on what your software does, and what kind of contractual
> arrangements you have with the recipients of your software.

And what you mean by "use libstdc++ in proprietary software".

I don't see how the runtime exception is relevant to installing
modified GPLv3 software on a device though. If your software is
proprietary, then it's not covered by the GPLv3, so is not covered by
the anti-tivoization clause.

> You need
> to hire your own lawyer for advice.

And read https://www.gnu.org/licenses/gcc-exception-3.1-faq.en.html if
you haven't done so already.

The exception means you can use GCC to compile proprietary C++ code.
Software covered by the GPLv3 is still covered by the GPLv3.

      reply	other threads:[~2020-03-25 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <600439317.566955902.1585132671519.JavaMail.root@zimbra71-e12.priv.proxad.net>
2020-03-25 10:39 ` emile.fortes
2020-03-25 10:55   ` Florian Weimer
2020-03-25 12:43     ` Jonathan Wakely [this message]

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=CAH6eHdRGyCz6+8AW9oGeTOPUDbN8kmBkpmBtD8NfYp+UTRDtxA@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=emile.fortes@free.fr \
    --cc=gcc-help@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).