Quoting Paolo Bonzini <bonz...@gnu.org>:
Joern Rennecke wrote:
Quoting Ian Lance Taylor <i...@google.com>:
I'm not sure what your point is here. newlib is not under the GPL in
any case. It is not affected by the gcc runtime library license.
The old runtime library exception allowed you to distribute binaries that
both include pieces of the gcc runtime and arbitrary pieces of newlib,
without requiring the distribution to be under the terms of the GPL.
I.e. your could link non-GPL code against both the gcc runtime and newlib
and distribute it.
The new license does not allow this unless all parts included from newlib
are written in a high level language AND use the gcc runtime.
If they do not use the GCC runtime, why should those parts be affected
by the GCC runtime license?
It is not the parts of newlib that are affected, it is users that are
affected who want to link newlib which includes these parts - together
with libgcc and Independent Modules, and distribute the resulting
binaries under non-GPL terms. They will no longer be allowed to do
this with when they are using a single link step, as they are creating
a derived work for which they have no license to distribute, except
possibly the GPL.
