From: Andrew Haley <aph@redhat.com>
To: Anton Tikhomirov <baltoon@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Using libgcc library in commercial product
Date: Tue, 13 May 2008 09:14:00 -0000 [thread overview]
Message-ID: <48295BA7.6070209@redhat.com> (raw)
In-Reply-To: <eae40580805130043jd7d2998u216544e3669e60fb@mail.gmail.com>
Anton Tikhomirov wrote:
> We're using libgcc in our project (commercial), but its license is
> GPL, but also we heard about special exception for this library.
> Can you give an example of such exception (if it exists), so we can
> use libgcc without worry
Yes, the exception is there. The licence is the first 30 lines of gcc/libgcc2.c.
Andrew.
prev parent reply other threads:[~2008-05-13 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 8:16 Anton Tikhomirov
2008-05-13 9:14 ` Andrew Haley [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=48295BA7.6070209@redhat.com \
--to=aph@redhat.com \
--cc=baltoon@gmail.com \
--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).