Path: utzoo!attcan!uunet!seismo!dimacs.rutgers.edu!mips!mips.COM!wilkes
From: wilkes@mips.COM (John Wilkes)
Newsgroups: comp.unix.i386
Subject: Re: System V and Xenix compatibility
Message-ID: <40069@mips.mips.COM>
Date: 11 Jul 90 18:37:33 GMT
References: <40800022@uicsl.csl.uiuc.edu> <17032@haddock.ima.isc.com>
Sender: news@mips.COM
Lines: 26

In article <40800022@uicsl.csl.uiuc.edu>, brando@uicsl.csl.uiuc.edu writes:
> /* Written  1:38 pm  Jul  5, 1990 by peterf@haddock.ima.isc.com in
uicsl.csl.uiuc.edu:comp.unix.i386 */
> /* ---------- "System V and Xenix compatibility" ---------- */
> 	>Lotus 1-2-3 (you may have heard of it), to System V and Xenix.
> 	>We developed on 386/ix and used gcc and gmake.  The executable
> /* End of text from uicsl.csl.uiuc.edu:comp.unix.i386 */
> 
> Correct me if I'm wrong, but I thought the whole point of the gcc compiler
> was that if you use it, the code you write is also covered by their licensing
> agreement

I believe that you are confusing use of the compiler with use of the GNU
library.  If your code is linked with the GNU library, then the
resultant executable contains GNU code, and is thus covered by the
license.  As I remember the discussions, one could avoid the licensing
restrictions by shipping a separate object file and instructions for
linking, including all the GNU lib source, etc. without having to
provide source for your proprietary whatzit.  IMO, this is sleazy.

I am neither a spokesman for the GNU Project nor a lawyer, and it is
quite likely that I am entirely incorrect.

John Wilkes

wilkes@mips.com   -OR-   {ames, decwrl, pyramid}!mips!wilkes