This is the mail archive of the
mailing list for the GCC project.
Re: License compliance on updating gcc runtime libraries
- From: <hiraku dot toyooka at cybertrust dot co dot jp>
- To: <jwakely dot gcc at gmail dot com>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Thu, 28 Feb 2019 10:28:08 +0000
- Subject: Re: License compliance on updating gcc runtime libraries
- References: <CADPJy8VH-1O_nWy1TVswrm9VshVq1tJBpy33UY-p8dpVtsq32g@mail.gmail.com> <CAH6eHdT_L9sAe-7xQ1VfA6fxR_dtnRet5g+1m4PBTNN=ayouOQ@mail.gmail.com>
Thank you for your reply.
> The exception applies to the application code, not to libgcc_s.so,
> libstdc++.so etc.
I noticed my prerequisite might be wrong.
I thought that the shared runtime libraries are also included in the
"work of Target Code formed by combining the Runtime Library with
Independent Modules" when they are distributed with applications.
But I read the FAQ again. It says:
> Note that if you distribute libstdc++ as an independent library, you
> will need to follow the terms of the GPL when doing so. For example,
> if you distribute the library itself in object code form, you will
> need to provide source code to your recipients using one of the
> methods listed in section 6 of GPLv3.
So the update case is same. The vendor needs to follow the terms of the
GPL for the shared runtime libraries.