From: Per Arnold Blaasmo <Per-Arnold.Blaasmo@atmel.com>
To: <crossgcc@sourceware.org>
Subject: License text in finished built toolchain?
Date: Fri, 20 Apr 2012 08:16:00 -0000 [thread overview]
Message-ID: <4F911B40.3000002@atmel.com> (raw)
Hi,
I have a question regarding the finished built toolchain and
redistribution if that.
If I use Crosstool-ng to build a GNU Toolchain and redistribute that
with my own product.
Do we need to have the license files in the finished build tree?
Should crosstool-ng copy those in to the finished tree?
What about crosstool-ng's license?
Do we need to add that to the finished built toolchain?
Do anyone have any thought on this?
Best Regards
Per A.
--
Per Arnold Blåsmo
Senior Design Engineer, Atmel Norway
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2012-04-20 8:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 8:16 Per Arnold Blaasmo [this message]
2012-04-20 14:03 ` Thierry Moreau
2012-04-20 16:02 ` Bill Pringlemeir
2012-04-20 18:28 ` Michael Eager
2012-04-21 22:27 ` Oron Peled
2012-04-22 0:01 ` Michael Eager
2012-04-23 17:19 ` Yann E. MORIN
2012-04-23 21:46 ` Michael Hope
2012-04-23 22:21 ` Oron Peled
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=4F911B40.3000002@atmel.com \
--to=per-arnold.blaasmo@atmel.com \
--cc=crossgcc@sourceware.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).