From: David Malcolm <dmalcolm@redhat.com>
To: "Timur Kristóf" <timur.kristof@gmail.com>,
"jit@gcc.gnu.org" <jit@gcc.gnu.org>
Subject: Re: libgccjit licensing question
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <1502458184.3741.7.camel@redhat.com> (raw)
In-Reply-To: <1502388795.3666.5.camel@gmail.com>
On Thu, 2017-08-10 at 20:13 +0200, Timur Kristóf wrote:
> Hi,
>
> Is libgccjit part of the GCC Runtime Library Exception?
> Can I use libgccjit in a non-GPL (for example, MIT or Apache
> licensed)
> project (without turning that project into GPL)? Can the authors of
> proprietary software use it?
>
> Thanks in advance for your answers!
>
> Best regards,
> Timur
>
> ps. Sorry if this has been asked before, but I couldn't find any
> definitive answers.
I'm the author and maintainer of libgccjit, but AFAIK the FSF holds the
copyright on it.
I'm not sure of the answers to your questions; I've emailed requesting
clarification of this.
I'm not a lawyer, so please don't consider any of this legal advice;
sorry that I can't be more helpful at this point.
Dave
next prev parent reply other threads:[~2017-08-11 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 Timur Kristóf
2017-01-01 0:00 ` David Malcolm [this message]
2017-01-01 0:00 ` Timur Kristóf
2021-07-02 0:21 Antoni Boucher
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=1502458184.3741.7.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=jit@gcc.gnu.org \
--cc=timur.kristof@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).