premetz@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (Dan L. Premetz 4-6581) writes:
> I'm currently dealing with a vendor who has their own modified compiler which is based off of GCC. Doing a "<vendor compiler command> -v" yields:
>
> Reading specs from ./../lib/gcc-lib/<vendor path>/specs
> gcc version gcc-<version> <etc, etc, etc...>
>
> Recently, the company has changed their licensing terms such that they want to license the usage of the compiler itself (several thousand dollars per seat). Previously, they had licensed their proprietary, front-end IDE, not the GNU-based command-line tools.
>
> I've done this job long enough and dealt with enough sales people to know what's going on here: the representatives of this company which have been appointed to work with us do not understand the technical distinction between their own proprietary tools and the GNU-based underpinnings which make it possible for their tools to work.
>
> I am looking for a confirmation that I am correct in my understanding that any work based off of a GNU project is also subject to the GNU GPL. At present, I have a copy of the GPL and will forward it to our legal people, but I won't *press* the issue unless I'm certain I know what I'm talking about.
You are correct that the compiler is subject to the GPL. If they gave
you a copy of the compiler binary, then they must provide the sources,
and you may modify the sources however you see fit, and you may
distribute the result however you see fit, subject to the restrictions
of the GPL.
That said, the vendor is perfectly entitled to charge several thousand
dollars per seat for giving you the compiler. What they are not
entitled to do is to restrict you from using the compiler in some
other way once you receive it. Of course in that scenario they may
refuse to give you support or updates.
The FSF is the copyright holder of gcc. If there is a real problem
here, they are the people to help you. See
http://www.gnu.org/licenses/gpl-violation.html
Ian
