I am following up on the discussion in issue #113 regarding the statically linked libstdc++ components and the GCC Runtime Library Exception. I came across it because the GPL 3 license was detected by our scanning tools, based on the reference in the NOTICE file, and the compliance process flagged issues.
From my understanding, the thread discussed in a more abstract way that the use of statically linked libstdc++ is intended to be permissible under the GCC exception. However, given the GCC exception has some requirements which must be met in order to "do its magic", I could not find any discussion as to which specific conditions need to be satisfied for this assessment, and whether these conditions were actually considered and fulfilled in the relevant build and distribution process of the project.
In particular, could you please clarify whether:
the included GCC runtime libraries (e.g. libstdc++) are used and distributed in unmodified form;
no source code from the GCC runtime libraries beyond ordinary runtime linking/header usage is copied or incorporated into the component itself;
the affected component is intended to remain technically independent from the GCC runtime libraries rather than constituting a derivative work of them; and
the relevant binaries are generated through a standard GCC-based build process without the use of incompatible GPL-restricted tooling affecting the resulting target code.
Any clarification/confirmation on these points would significantly facilitate downstream compliance assessments and the continued use of the package. Thank you very much!
I am following up on the discussion in issue #113 regarding the statically linked libstdc++ components and the GCC Runtime Library Exception. I came across it because the GPL 3 license was detected by our scanning tools, based on the reference in the NOTICE file, and the compliance process flagged issues.
From my understanding, the thread discussed in a more abstract way that the use of statically linked libstdc++ is intended to be permissible under the GCC exception. However, given the GCC exception has some requirements which must be met in order to "do its magic", I could not find any discussion as to which specific conditions need to be satisfied for this assessment, and whether these conditions were actually considered and fulfilled in the relevant build and distribution process of the project.
In particular, could you please clarify whether:
the included GCC runtime libraries (e.g. libstdc++) are used and distributed in unmodified form;
no source code from the GCC runtime libraries beyond ordinary runtime linking/header usage is copied or incorporated into the component itself;
the affected component is intended to remain technically independent from the GCC runtime libraries rather than constituting a derivative work of them; and
the relevant binaries are generated through a standard GCC-based build process without the use of incompatible GPL-restricted tooling affecting the resulting target code.
Any clarification/confirmation on these points would significantly facilitate downstream compliance assessments and the continued use of the package. Thank you very much!