You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Leonard Lausen (Jira)" <ji...@apache.org> on 2020/08/14 00:48:00 UTC
[jira] [Comment Edited] (LEGAL-523) GCC Runtime Library Exception
[ https://issues.apache.org/jira/browse/LEGAL-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177400#comment-17177400 ]
Leonard Lausen edited comment on LEGAL-523 at 8/14/20, 12:47 AM:
-----------------------------------------------------------------
> it appears you're confused as to what purpose that page serves. That page is NOT an FAQ on licensing. That pages is a single source of truth documenting various decisions and intepretations made by ASF's legal committee.
Should ASF share it's interpretation of how license exceptions work with it's members to avoid diverging interpretations in the future?
[~rvs] it seems to me that you and [~jmclean] have argued for a different interpretation of how license exceptions work than [~fielding]. In fact [~jmclean] has argued for a practice that is inconsistent with existing practice of allowing Apache projects to use GCC compiler.
> I don't think in this case we're making any new decisions and/or interpretations.
Alright. I'm surprised about this given the different interpretations above. But I won't argue longer for why having clear guidelines to projects would be helpful.
was (Author: lausen):
> it appears you're confused as to what purpose that page serves. That page is NOT an FAQ on licensing. That pages is a single source of truth documenting various decisions and intepretations made by ASF's legal committee.
Should ASF share it's interpretation of how license exceptions work with it's members to avoid diverging interpretations in the future?
[~rvs] it seems to me that you and [~jmclean] have argued for a different interpretation of how license exceptions work than [~fielding]. In fact [~jmclean] has argued for a practice that is inconsistent with existing practice of allowing Apache projects to use GCC compiler. It seems clear that ASF members have not shared a common understanding of how license exceptions work.
> GCC Runtime Library Exception
> -----------------------------
>
> Key: LEGAL-523
> URL: https://issues.apache.org/jira/browse/LEGAL-523
> Project: Legal Discuss
> Issue Type: Question
> Reporter: Leonard Lausen
> Priority: Major
>
> In https://issues.apache.org/jira/browse/LEGAL-516, [~rvs] mentioned
> > it contains lib/native/libgfortran.so.3 which is clearly under Category X license as well.
> assuming that `libgfortran.so.3` is subject to the GPL.
> However, looking at the [source code of libgfortran|https://github.com/gcc-mirror/gcc/tree/master/libgfortran] we find that additional rights are granted
> > Under Section 7 of GPL version 3, you are granted additional
> > permissions described in the GCC Runtime Library Exception, version
> > 3.1, as published by the Free Software Foundation.
> The [GCC Runtime Library Exception, version 3.1|https://www.gnu.org/licenses/gcc-exception-3.1.en.html] states:
> > You have permission to propagate a work of Target Code formed by combining the
> > Runtime Library with Independent Modules, even if such propagation would otherwise
> > violate the terms of GPLv3, provided that all Target Code was generated by Eligible
> > Compilation Processes. You may then convey such a combination under terms of your
> > choice, consistent with the licensing of the Independent Modules.
> Please see the GNU website for definitions in the statement.
> Based on my understanding it is fine to redistribute libgfortran.so.3 as ASF as it can be distributed under terms of our choice (subject to compiling everything with GCC).
> My understanding assumes that "combining the Runtime Library with Independent Modules" does not refer to static linking but any combination (such as placing the two libraries into a jar file together).
> If you disagree, let's also discuss about static linking libgfortran.a. Static linking libgfortran.a would be rather complex, as one would first need to rebuild libgfortran.a with `--with-pic`, but in principle feasible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org