From: Paulo Matos <pmatos@linki.tools>
To: jit@gcc.gnu.org
Subject: licensing questions
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <ed8c3f3b-cf0a-600f-765a-392591dd4922@linki.tools> (raw)
Hi,
libgccjit is released with GCC and therefore GPLv3.
This seems to mean, from my relatively low knowledge in this area, that
all libraries linking to libgccjit to create bindings and libraries and
applications linking to this library are forced into GPLv3.
I though LGPL was created with the purpose of stopping the viral spread
of GPLv3. Was it the authors decision to make it GPLv3 instead of LGPL -
which would have been, I guess, more flexible?
Kind regards,
--
Paulo Matos
next reply other threads:[~2019-02-21 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Paulo Matos [this message]
2019-01-01 0:00 ` David Malcolm
2019-01-01 0:00 ` Basile Starynkevitch
2019-01-01 0:00 ` Basile Starynkevitch
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=ed8c3f3b-cf0a-600f-765a-392591dd4922@linki.tools \
--to=pmatos@linki.tools \
--cc=jit@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).