From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4995 invoked by alias); 25 Aug 2012 20:19:48 -0000 Received: (qmail 4986 invoked by uid 22791); 25 Aug 2012 20:19:47 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Received: from mo-p05-ob.rzone.de (HELO mo-p05-ob.rzone.de) (81.169.146.182) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 25 Aug 2012 20:19:34 +0000 X-RZG-AUTH: :LXoWVUeid/7A29J/hMvvT2k715jHQaJercGOZE+TiTS5oyq5h49L8Cg= X-RZG-CLASS-ID: mo05 Received: from [192.168.2.100] (dslb-084-058-194-143.pools.arcor-ip.net [84.58.194.143]) by smtp.strato.de (jored mo40) (RZmta 30.11 DYNA|AUTH) with ESMTPA id L05107o7PK8blx ; Sat, 25 Aug 2012 22:19:32 +0200 (CEST) Message-ID: <503932B6.20704@gcc.gnu.org> Date: Sat, 25 Aug 2012 21:01:00 -0000 From: Georg-Johann Lay User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Ian Lance Taylor CC: Florian Weimer , Byron Blue , gcc-help@gcc.gnu.org Subject: Re: Simple question References: <7D3F997945FA4AEAA34010AAEFFD4335@Byron> <87fw7bs9w9.fsf@mid.deneb.enyo.de> <50390B17.5050104@gcc.gnu.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2012-08/txt/msg00241.txt.bz2 Ian Lance Taylor schrieb: > Georg-Johann Lay wrote: >> Ian Lance Taylor schrieb: >> >> Some weeks ago a customer came up with concerns about libgcc, GPL, >> the runtime exception and libgcc code. >> >> The objection against libgcc was that it uses parts that are GPL >> but do *not* come with the runtime exception. >> >> For example, ./libgcc/libgcc2.c includes tm.h which includes files >> from the ARM backend like ./gcc/config/arm/arm.h given the compiler >> is configured for ARM. arm.h does not come with the library >> exception because it is part of the compiler proper. >> >> The question is now: How is this handled? >> >> Is there a definite statement from the FSF on this case? >> If yes, please point me to it. >> If no, it would be highly appreciated to add a note to the >> FSF or GPL web sites and FAQ. > > I linked to the FSF FAQ earlier, and I think it is clear: > > http://www.gnu.org/licenses/gpl-faq.html#CanIUseGPLToolsForNF hmm. That text is about bison and hairy code. It doesn't even mention "runtime library exception" or #include > I don't think this is a real problem in practice. The statement on > libgcc/libgcc2.c is clear. No part of gcc/config/arm/arm.h is copied > into libgcc2.c. What if not a copy is #include? If it is legal to #include any code, I could just as well include GPL code in non-GPL software. > However, if you are concerned about it, I recommend that you > raise the issue with the GCC Steering Committee (by sending > an e-mail to gcc@gcc.gnu.org). I have no problem with the GPL, but companies unfamiliar with it tend to be kind of paranoid with it... Of course it is possible to ask the FSF or the GCC steering committee each and every time, but such questions pop up again and again and it might help GCC or other free software if the FAQ was more specific and more explicit on that. The FAQ could explicitly work out some common use cases like include GPL code in non-GPL code, or the above mentioned inclusion of code without runtime exception from code with runtime exception. If it's no problem, then the page could say so. I believe that *any* misconceptions about GPL and runtime exception should be cleared up as early as possible, and as clearly as possible, and as easily to find on the web as possible. Anything else keeps potential users from using free software. That's not the intention of its founders or its authors.