From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31718 invoked by alias); 20 Apr 2012 18:28:45 -0000 Received: (qmail 31707 invoked by uid 22791); 20 Apr 2012 18:28:44 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from shell4.bayarea.net (HELO shell4.bayarea.net) (209.128.82.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 20 Apr 2012 18:28:27 +0000 Received: (qmail 9520 invoked from network); 20 Apr 2012 11:28:26 -0700 Received: from c-76-102-3-160.hsd1.ca.comcast.net (HELO redwood.eagercon.com) (76.102.3.160) by shell4.bayarea.net with SMTP; 20 Apr 2012 11:28:26 -0700 Message-ID: <4F91AACA.4030805@eagerm.com> Date: Fri, 20 Apr 2012 18:28:00 -0000 From: Michael Eager User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 MIME-Version: 1.0 To: crossgcc@sourceware.org Subject: Re: License text in finished built toolchain? References: <4F911B40.3000002@atmel.com> In-Reply-To: <4F911B40.3000002@atmel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2012-04/txt/msg00023.txt.bz2 On 04/20/2012 01:16 AM, Per Arnold Blaasmo wrote: > 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? You do *not* need to include licenses in the tool chain installation tree. Most distributions do not include licenses with the binaries. You *do* need to provide the licenses to your users in some fashion. Many companies distribute these licenses as one or more text files along with their program (for example, on the CD/DVD) or include them as an appendix to the documentation for the program. Some, like Mozilla, have the license displayed when the program is installed. Each of the licenses describe what you must do to conform to the license. You may need to include copyright notices in your documentation, output a copyright notice (required for interactive programs licensed under the GPL), or include license files with your program. In particular, the GPL requires that you provide the source used to build the binaries or provide a reasonable means to obtain the source. You can find crosstool-ng's license in crosstool-ng/licenses.d/by-sa. Since the build tree generated by crosstool-ng does not contain crosstool-ng, and it is unlikely that you would redistribute crosstool-ng with your program, there would not appear to be any requirement to include this license. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077 -- For unsubscribe information see http://sourceware.org/lists.html#faq