the FSF decided long ago to allow developers to use GCC's libraries to
compile any program, regardless of its license. Developing nonfree
software is not good for society, and we have no obligation to make it
easier. We decided to permit this because forbidding it seemed likely to
backfire, and because using small libraries to limit the use of GCC
seemed like the tail wagging the dog.
Therefore, these libraries have always had license exceptions that allow
people to distribute the object code GCC produces under any license
http://www.gnu.org/licenses/gcc-exception-faq.html
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 ..
A Compilation Process is "Eligible" if it is done using GCC, alone or
with other GPL-compatible software, or if it is done without using any
work based on GCC. For example, using non-GPL-compatible Software to
optimize the GCC intermediate representation would not qualify as an
Eligible Compilation Process.
http://lwn.net/Articles/301959/
_______________________________________________
gnu-misc-discuss mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-misc-discuss
