LWN.net Logo

GCC unplugged

GCC unplugged

Posted Nov 21, 2007 7:25 UTC (Wed) by sylware (subscriber, #35259)
In reply to: GCC unplugged by njs
Parent article: GCC unplugged

Well, to remove any ambiguity, instead of considering plugins "derivative work", the GPL would
then be extended to barely forbid proprietary plugins. Namely any plugins would be subject to
this extended GPL.


(Log in to post comments)

GCC unplugged

Posted Nov 28, 2007 16:53 UTC (Wed) by vonbrand (subscriber, #4458) [Link]

The problem is that if I write a plugin for GCC, using the published interface to do so, my plugin is mine and mine alone, to do as I wish, unless it contains GCC-derived code (or thereabouts, it is not that clearcut). So I can happily distribute it as closed source for a heavy price, all legally.

Trying to place the use of the interface under strict conditions won't work either, as the idea of a interface is to make such connections possible; and besides as a user of the interface I'm not copying anything anyway, so no copyright interferes.

GCC unplugged

Posted Nov 29, 2007 16:28 UTC (Thu) by nix (subscriber, #2304) [Link]

It's kind of hard to write anything like a useful plugin right now without 
using a whole pile of macros defined in GPL-without-exception header 
files.

Copyright © 2008, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds