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

[Barry Margolin]

In article <x5u0y3yt3x.fsf@lola.goethe.zz>, David Kastrup <dak@gnu.org> 
wrote:

> byron@cc.gatech.edu (Byron A Jeff) writes:
> 
> > In article <x5n03v2vdi.fsf@lola.goethe.zz>, David Kastrup  <dak@gnu.org> 
> > wrote:
> > -ap85@georgetown.edu (Alexander R. Pruss) writes:
> > -
> > -> I'd like to distribute GPL code compiled with Borland's C compiler,
> > -> and statically linked with Borland's C library.  Is this permitted?
> > -
> > -According to what?  The GPL clearly tells you that you have to add the
> > -source code of your stuff.
> > 
> > I think you missed the point. The OP wants to compile and statically link 
> > GPL code with a proprietary compiler and library.
> 
> Which was the only way to get binaries for GPL programs at one time.
> What point am I missing?

They were typically distributed as source code, not pre-linked 
executables.  And even when they were pre-linked, they were linked with 
libraries that are normally available with with the OS, so the exception 
applied.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***