On 25/08/2014 20:43, John J. McDonough wrote:
> If you use an open source compiler under the GPL, then there is no
> question that you can do what you want with the result, and ditto for
> those libraries licensed under GPL.

You cannot "do what you want with the result", as the GPL (and other
similar licenses) place requirements on you if your final product
includes GNU GPL libraries.

>From http://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL :

"If a library is released under the GPL (not the LGPL), does that mean
that any software which uses it has to be under the GPL or a
GPL-compatible license?

Yes, because the software as it is actually run includes the library."

>From http://www.gnu.org/licenses/why-not-lgpl.html :

"using the ordinary GPL for a library makes it available only for free
programs"

A popular example of this is home routers that use Linux as a base
operating system and bundle GPL binaries/libraries.

Therefore if *all* required libraries for compiling a program were GNU
GPL, e.g.

 - the C runtime
 - startup/initialisation code
 - popular functions like printf() or malloc()

... then you would not be free to "do what you want".  For this reason
the GNU C library (glibc) is LGPL and avr-libc is a modified BSD license.

David
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.