From: Andrew Haley <aph@redhat.com>
To: Anton Tikhomirov <baltoon@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Using GCC compiler
Date: Mon, 07 Apr 2008 10:47:00 -0000 [thread overview]
Message-ID: <47F9E311.5030109@redhat.com> (raw)
In-Reply-To: <eae40580804070155q26b39acbvf2b1c81c9b6dabc0@mail.gmail.com>
Anton Tikhomirov wrote:
> As we're planning to compile our closed (commercial) product using GCC
> compiler, new question arises - should we mention that we used GCC
> compiler and where (documentation?)
We would be happy for you to do that, but as far as I am aware the
GNU General Public License imposes no requirement on you to do so.
The full licence terms are contained in the COPYING file distributed
with gcc. Also check the additional terms in the file libgcc2.c that
cover distributing the gcc libraries that are linked with your binary
when you compile with gcc.
Andrew.
prev parent reply other threads:[~2008-04-07 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 9:02 Anton Tikhomirov
2008-04-07 10:47 ` 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=47F9E311.5030109@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).