From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7286 invoked by alias); 20 Apr 2012 14:03:55 -0000 Received: (qmail 7277 invoked by uid 22791); 20 Apr 2012 14:03:53 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,TW_SG X-Spam-Check-By: sourceware.org Received: from intagionic.org (HELO mail.connotech.com) (76.10.176.241) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 20 Apr 2012 14:03:16 +0000 Received: from [192.168.1.200] (unknown [192.168.1.200]) by mail.connotech.com (Postfix) with ESMTPA id F132F308D9; Fri, 20 Apr 2012 15:20:06 -0400 (EDT) Message-ID: <4F916E4A.3030708@connotech.com> Date: Fri, 20 Apr 2012 14:03:00 -0000 From: Thierry Moreau User-Agent: Thunderbird 2.0.0.17 (X11/20090608) MIME-Version: 1.0 To: Per-Arnold.Blaasmo@atmel.com CC: 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=ISO-8859-1; 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/msg00021.txt.bz2 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? > > Best Regards > Per A. > May I suggest that the business decision to use the GCC technology (in my opinion perhaps the greatest mankind achievement in the field of software engineering) should have been taken with due consideration for the legal framework called *GPL*. Then, to "redistribute a GNU toolchain" means compliance to the GPL, which obviously requires the copyright statements and license files, and more useful to the community in practice, the availability (through the redistributing organization, as detailed in the license provisions) of the source code that allowed the distributor to come up with the finished built toolchain. If you don't abide by the license terms, you should stop redistributing GCC toolchains and rely on proprietary compiler technology. You may need legal advice to get a full understanding or the situation. I don' se the point for crossgcc developers/maintainers to delve into these issues for you. Their time is best used elsewhere. Regards, -- - Thierry Moreau CONNOTECH Experts-conseils inc. 9130 Place de Montgolfier Montreal, QC, Canada H2M 2A1 Tel. +1-514-385-5691 -- For unsubscribe information see http://sourceware.org/lists.html#faq