On 25/08/12 22:37, Ian Lance Taylor wrote: > On Sat, Aug 25, 2012 at 1:16 PM, Georg-Johann Lay <gjl@xxxxxxxxxxx> wrote: >> Ian Lance Taylor schrieb: >> >>> Georg-Johann Lay wrote: >>>> Ian Lance Taylor schrieb: >>>> >>>> Some weeks ago a customer came up with concerns about libgcc, GPL, >>>> the runtime exception and libgcc code. >>>> >>>> The objection against libgcc was that it uses parts that are GPL >>>> but do *not* come with the runtime exception. >>>> >>>> For example, ./libgcc/libgcc2.c includes tm.h which includes files >>>> from the ARM backend like ./gcc/config/arm/arm.h given the compiler >>>> is configured for ARM. arm.h does not come with the library >>>> exception because it is part of the compiler proper. >>>> >>>> The question is now: How is this handled? >>>> >>>> Is there a definite statement from the FSF on this case? >>>> If yes, please point me to it. >>>> If no, it would be highly appreciated to add a note to the >>>> FSF or GPL web sites and FAQ. >>> >>> I linked to the FSF FAQ earlier, and I think it is clear: >>> >>> http://www.gnu.org/licenses/gpl-faq.html#CanIUseGPLToolsForNF >> >> hmm. That text is about bison and hairy code. >> It doesn't even mention "runtime library exception" or #include > That link poses the question "Can I use GPL-covered tools such as GCC > to compile [non free programs]?" and answers the question "Yes." > > Details like the runtime library exception and #include simply aren't > relevant. The issues with the runtime library exception only arise in > very unusual and, to the best of my knowledge, purely theoretical > cases. No ordinary user of GCC will ever encounter them. The issue > with #include simply doesn't matter. That's probably because the Runtime library exception requires an explicit notice on affected files. Had the FSF additionally "licensed" that any non-GPL code compiled with an official release of gcc is subject to that exception and is not bound to the GPL due to the compilation. Most lawyers will get confused if needing to track which files get automatically linked by gcc and if they have proper exception. Should be clear from the first FAQ answer, though: http://www.gnu.org/licenses/gcc-exception-3.1-faq.html Another view about the #include could be that the exception at libgcc/libgcc2.c covers all included headers, too. But that may be arguable. >> Of course it is possible to ask the FSF or the GCC steering >> committee each and every time, but such questions pop up again and >> again and it might help GCC or other free software if the FAQ was >> more specific and more explicit on that. The FAQ could explicitly >> work out some common use cases like include GPL code in non-GPL >> code, or the above mentioned inclusion of code without runtime >> exception from code with runtime exception. > What questions pop up again and again? Where do they pop up? I have > not seen them. I have seen many people ask the CanIUseGPLToolsForNF question. Funny thing is that I don't think they call <big corporation> to check if it's ok to use their <software> for <confidential business>. Not that I have seen explicit exceptions for that on propietary EULAs, either (why should they?). Still, many people have doubts about the free software being viric, when they just want to work with it in user mode. That makes me think there's a problem in the way many people understood licenses like GPL. That enters a different realm, though. Regards
