From: Dave K. <dav...@ar...> - 2008-05-15 22:36:49
|
Doug Schaefer wrote on 15 May 2008 22:56: > Actually with that argument, GPL would be restrict you from building > against any proprietary C run-time including Solaris, AIX, etc. So I'm > not sure this is actually restricted. But then I could be missing > something. At either rate, GPL apps do not redistribute all the headers > they use, of course. GPLv2 has an explicit exception for standard libs and headers shipped with the system. http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLIncompatibleLib s " However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable." I don't know if that covers something that comes as a separate package like the PSDK; the GPLv2 was rather unix-centric, and didn't conceive that someone would ever ship an OS without a compiler, libraries and headers! I suspect the answer might be that since the compiler is not shipped with the OS, it is not a "component", but if you wanted a better answer, you'd probably want to raise it on gnu.misc. (Or even search the archives, it may have been discussed before). But anyway, that's how come it works for AIX and Solaris and co. Hmm, thinking back on it, I'm not sure if the compiler and libs and headers package always shipped as a standard part of Solaris, so there might be some leeway for optional extras. Only an opinion from the FSF itself can have any authority in this matter, however. cheers, DaveK -- Can't think of a witty .sigline today.... |