Re: Total Reciprocity Public License (TRPL v1.0)

On 12/3/2025 1:56 PM, Pamela Chestek wrote:
>
> But that seems orthogonal to your point. Your hypo seems to be that 
> the compiler is under this license ("infringes the copyright of the 
> compiler") and the question is about the relationship of the output to 
> the compiler. You dismiss the possibility that some copyrightable 
> portions of the compiler end up in the compiled code, but I understand 
> that it is possible - libraries, for example. So it's at least 
> theoretically possible that the output could be a derivative work of 
> the compiler, and if so, this is a quasi-copyleft requirement (more 
> about that in a moment), which is acceptable for an open source license.
>
A great example of this is the run time exception in the GCC: 
https://gcc.gnu.org/onlinedocs/libstdc++/manual/license.html

"When you use GCC to compile a program, GCC may combine portions of
certain GCC header files and runtime libraries with the compiled
program. The purpose of this Exception is to allow compilation of
non-GPL (including proprietary) programs to use, in this way, the
header files and runtime libraries covered by this Exception."

_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Official statements by the Open Source Initiative will be sent from an opensource.org email address.

License-discuss mailing list
[email protected]
http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org