Ian Lance Taylor schrieb:
On Sat, Aug 25, 2012 at 12:33 AM, Florian Weimer <fw@xxxxxxxxxxxxx> wrote:
* Byron Blue:
This is the question:
GCC uses the GNU license scheme. This operating system would be
embedding in our industrial computers and I do not (of course) want
the source code for our operating system to be open source - available
to our competitors. The GNU site is not quite clear in this area and
being new I would not want to "break the rules". Could I ask you for a
bit of clarification on this issue?
Unless you take special precautions, GCC copies parts of itself into
compiled executables.
This is false as stated. It is true that GCC provides runtime
libraries, and that in some cases the linker (not part of GCC) will
combine portions of those runtime libraries with the compiled code to
produce the final executable.
The compiled executables must therefore be
licensed in a way that is compatible with the GPL.
This is completely false.
However, there is
an exception for many parts which can be copied in this way.
Here you seem to be talking about the runtime libraries. All parts of
the runtime libraries have the exception, not "many parts."
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.
All I could find is a remark on a different but related issue,
namely including GPLed headers in non-GPL software.
Richard Stallman wrote 2003-01-09 in [1]:
[...] I've talked with our lawyer about one specific issue that
you raised: that of using simple material from header files.
Someone recently made the claim that including a header file
always makes a derivative work.
That's not the FSF's view. Our view is that just using structure
definitions, typedefs, enumeration constants, macros with simple
bodies, etc., is NOT enough to make a derivative work. It would take
a substantial amount of code (coming from inline functions or macros
with substantial bodies) to do that.
My assumption is that the policy on including GPL headers without
the runtime exception in GPL sources with the runtime exception is
to be treated similarly.
However, I am not a lawyer and what I think is completely irrelevant.
It there some *official* page that gives explanations on the questions
above?
[1] http://lkml.indiana.edu/hypermail/linux/kernel/0301.1/0362.html
