[ale] OT: GPL and GNU compilers

[Mike Panetta]

Nope, glibc is LGPL, so its ok to link against it (unless something has changed?).  If you make any changes to glibc though you do need to give them back.  I personally think all libraries should be LGPL (its a more "free" license then the GPL IMO), but unfortunately some are not (the LM Sensors libs come to mind), so they cannot easily be used in commertial products, without doing some sneaky things, such as writing a small binary that calls the GPL'd code, GPLing that and then calling it from your program with exec.  Its a pain to do it that way, but its one way to get around the linking clause :P

Mike

-------Original Message-------
From: Jeff Layton <jeffrey.b.layton at lmco.com>
To: ale at ale.org
Sent: 05/07/03 11:19 AM
To: ale at ale.org
Subject: [ale] OT: GPL and GNU compilers

> 
> Hello,

   Unfortunately I have an off-optib question about the GNU
compilers on Linux. If I compile my code with a GNU compiler
(gcc, g77, etc.), that calls functions from glibc, then is my code
GPL? (I don't know the license on glibc - I'm checking now).

Thanks!

Jeff


--
Jeff Layton
Senior Engineer - Aerodynamics and CFD
Lockheed-Martin Aeronautical Company - Marietta

"Is it possible to overclock a cattle prod?" - Irv Mullins



_______________________________________________
Ale mailing list
Ale at ale.org
<a target=_blank
href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
> 
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale