This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Add GPL compatibility check for plugins



On Jun 18, 2009, at 6:31 PM, Frank Ch. Eigler wrote:



Diego Novillo <dnovillo@google.com> writes:


On request from the FSF, I am adding this check.  When a plugin is
loaded, the compiler checks whether the symbol
plugin_is_GPL_compatible exists in the loaded shared object.  The
presence of this symbol asserts that the loaded plugin has been
licenced under a GPL-compatible license.  If the symbol does not
exist, the compiler exits [...]

Doesn't this restriction violate "right #0" of free software, the right to use the software for any purpose?

Being in possession of a non-GPL'd plugin in no way violates the GPL,
even if one accepts arguendo that a plugin can't possibly written
except having to be "derived" from GPL sources.  That's because, as we
all should know, the GPL only kicks on when *distributing* that code.

Right. The GCC license is actually apparently designed to explicitly support this. Building with a non-gpl plugin is explicitly allowed. If you link to GCC's runtime libraries, use of a non-gpl plugin just makes the resultant app subject to the terms of the GPL.


-Chris


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]