Date: Wed, 28 Jan 2009 10:50:33 -0800 From: Chuck Swiger <cswiger@mac.com> To: Michel Talon <talon@lpthe.jussieu.fr> Cc: freebsd-current@freebsd.org Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) Message-ID: <7508A5B5-C6D2-498A-AEA1-D84E85F1D743@mac.com> In-Reply-To: <20090128155340.GA75143@lpthe.jussieu.fr> References: <20090128155340.GA75143@lpthe.jussieu.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 28, 2009, at 7:53 AM, Michel Talon wrote: > pluknet wrote: >> I found this article today. It answers some questions about GPLv3. >> >> http://www.fsf.org/licensing/licenses/gcc-exception-faq.html > > Indeed this is exactly what i said, there are exemptions for code that > the compiler brings into the executable (notably this is particularly > the case for g++) such that using gcc has absolutely no bearing on the > license of the resulting binary. The relevant bit I saw from that page was: > As long as you use an Eligible Compilation Process, then you have =20 > permission to take the Target Code that GCC generates and propagate =20= > it =93under terms of your choice.=94 If you did use GPL-incompatible =20= > software in conjunction with GCC during the Compilation Process, you =20= > would not be able to take advantage of this permission. Since all of =20= > the object code that GCC generates is derived from these GPLed =20 > libraries, that means you would be required to follow the terms of =20 > the GPL when propagating any of that object code. You could not use =20= > GCC to develop your own GPL-incompatible software. Evidently, the FSF is now claiming that all object code produced from =20= GCC 4.2.2 and later is GPLv3-licensed, and only their exception =20 permits you to distribute executables compiled using an "Eligible =20 Compilation Process" under the terms of some other license. I wonder if they make this claim even if -nostartfiles, -nostdlib and/=20= or -nodefaultlibs options are used? Regards, --=20 -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7508A5B5-C6D2-498A-AEA1-D84E85F1D743>