License compliance on updating gcc runtime libraries

Jonathan Wakely jwakely.gcc@gmail.com
Wed Feb 27 09:32:00 GMT 2019


On Wed, 27 Feb 2019 at 09:06, <hiraku.toyooka@cybertrust.co.jp> wrote:
>
> Hello,
>
> I have questions about the GCC Runtime Library Exception.
>
> When an equipment vendor distributes an update of shared gcc runtime
> libraries (e.g. libgcc_s.so, libstdc++.so) to the shipped equipment
> and when the equipment has applications which are dynamically linked to
> older release of the shared libraries and which are being linked to
> newer ones, in this case, is the exception applied to the newer ones?

The exception applies to the application code, not to libgcc_s.so,
libstdc++.so etc.

Updating the runtime libraries doesn't change anything. If the
applications were covered by the exception when compiled, they are
still covered by the exception later when the runtime libraries are
updated.

> I read the exception document(*) and FAQ(**).
> I understood that "a work of Target Code formed by combining the Runtime
> Library with Independent Modules" could be propagated as non-GPLv3
> license, even if "the Runtime Library" was dynamically linked to
> "Independent Modules".
> I wonder if an update of the shared libraries are regarded as a part of
> the "work of Target Code" or "independent library" in the above case.
>
> Could anyone kindly tell me the intention of the exception?

The intention is that GCC can be used to build non-GPL software.
Updating the shared libraries doesn't change that.



More information about the Gcc mailing list