Re: GPL and statically linking with non-GPL standard C library

[Byron A Jeff]

In article <f601968d.0405260448.5c463ca5@posting.google.com>,
Alexander R. Pruss <ap85@georgetown.edu> wrote:

I'm not a lawyer. I repeat IANAL.

-I'd like to distribute GPL code compiled with Borland's C compiler,
-and statically linked with Borland's C library.  Is this permitted? 

No.

-The question comes down to the GPL exception: "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."

Clear as crystal.

-
-However, it seems to me the Borland C compiler and its standard
-libraries are not a major component of the Windows operating system. 

Correct. That's why it's clear as crystal.

-They're not, after all, made by the same people who made the operating
-system.  So it seems that distributing binaries of GPL code statically
-linked against a standard C library that is not itself distributed
-under a GPL-compatible license is not allowed (and so I must go with
-mingw32 or something like that).

Correct. 

-
-Would it make a difference if I used the newly released free Microsoft
-C compiler and its libs?  

Nope. Not a part of the standard distribution of Windows and certainly isn't
a GPL compatible license.

-It would be easier to make a case that it's a part of the OS, no?

No.

-
-Is my reading right?  The GPL FAQ doesn't help very much here.

You have it nailed. Simply use mingw and have the compiler accompany the
system and be done with it.

BAJ