On Wed, 28 Jan 2009, Mark Mitchell wrote: > Joseph S. Myers wrote: > > > The tm.h headers are a lot of essentially host-side code with a few macros > > such as LIBGCC2_LONG_DOUBLE_TYPE_SIZE that affect target-side code in some > > cases. But if we should add the exception to over 80000 lines of code > > (the amount of config/*.h and config/*/*.h headers currently under GPLv3, > > which may not be the exact set of tm.h headers) for the sake of those > > macros, we can of course do so. > > Yes. It's not like this is some big loophole; it's unlikely that you > can do anything proprietary with tm.h files. The bottom line is that > the run-time libraries need to be free of any GPLv3 code that doesn't > have the exception to avoid frightening people. That's critical.
Then there are other files beyond tm.h that are included in libgcc code that need the exception adding, such as coretypes.h and include/ansidecl.h (via tconfig.h). Then there are lots of other miscellaneous license issues: files that have been added with GPLv2 on the host side since the main transition was done, host side files (in libiberty in particular) that haven't been transitioned to GPLv3, files over 10 lines with no copyright or license notices (some quite large, some probably on the target side as well as the host side), the GFDL revision in the manual not being the most current one (and the set of Invariant Sections in the manual not being those the FSF wanted there as of five years ago and put in the last printed edition), .... I don't know what issues are or are not considered how critical. -- Joseph S. Myers jos...@codesourcery.com
