New GCC Runtime Library Exception: not fit for purpose
amylaar@spamcop.net
amylaar@spamcop.net
Thu Jan 29 15:04:00 GMT 2009
Quoting Ian Lance Taylor <iant@google.com>:
> Joern Rennecke <amylaar@spamcop.net> writes:
>
>> Quoting Manuel López-Ibáñez <lopezibanez@gmail.com>:
>>
>>> 2009/1/29 Joern Rennecke <amylaar@spamcop.net>:
>>>>
>>>>> The runtime library license says that you can link libgcc with
>>>>> proprietary code, whether that proprietary code was compiled with gcc
>>>>> or whether it was compiled with some non-gcc proprietary compiler.
>>>>
>>>> No, it says that you can only do that if every file of the
>>>> proprietary code
>>>> is written or generated in a high level language, and uses the
>>>> GCC runtime.
>>>>
>>>
>>> Where does it say that?
>>
>> Where does it grant any other permission?
>> It allows you to propagate a work of Target code formed by combining
>> the Runtime Library with Independent Modules under certain conditions,
>> but
>> it doesn't give you any permission to propagate a work that also includes
>> code that is neither part of the Runtime Library nor an Independent Module.
>
> I don't think it needs to.
>
> Code that is neither Target Code nor an Independent Module is code
> that has never been involved with gcc, and the license does not cover
> it. The license does not prohibit combining Target Code or
> Independent Modules with other code, so it is permitted.
>
> Ian
>
More information about the Gcc
mailing list