public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alex Rosenberg <alexr@spies.com>
To: Per Bothner <per@bothner.com>, Joe Buck <jbuck@synopsys.com>
Cc: <dewar@gnat.com>, <gcc@gcc.gnu.org>, <geoffk@redhat.com>
Subject: Re: Compiler for Red Hat Linux 8
Date: Wed, 18 Jul 2001 23:00:00 -0000	[thread overview]
Message-ID: <B77BC590.45815%alexr@spies.com> (raw)
In-Reply-To: <m21yndbhm8.fsf@kelso.bothner.com>

on 7/18/01 10:41 PM, Per Bothner at per@bothner.com wrote:

> Joe Buck <jbuck@synopsys.com> writes:
> 
>> Per Bothner wrote:
>>> If A gives B a GPL'd compiler under the proviso of a NDA prohibiting
>>> A from distributing the compiler to third parties that is a very
>>> different matter.  I don't think that in itself violate the GPL.
>> 
>> Nope, read it again.  The GPL requires that all recipients be given a
>> license to redistribute.
> 
> But A is not the recipient - A is the one providing the compile to B.
> B is of course free to redistribute the compiler.  But we are talking
> about the case where the NDA binds *A*, not B.  Think A==RedHat;
> B==Intel; RedHat signs NDA and develops compiler port; Intel receives
> compiler from GCC.  RedHat is bound by the NDA; Intel is free to
> r-distribute GCC under GPL, and is not bound by the NDA;  viola no
> conflict.
> 
> Now if Intel then distributes GCC to a third party under an NDA,
> *then* there is a confloct.

It sounds like you've just described a common situation. Notably, this
sounds like the Playtation 2 situation.

+------------------------------------------------------------+
| Alexander M. Rosenberg           < mailto:alexr@_spies.com > |
| Nobody cares what I say. Remove the underscore to mail me. |


  reply	other threads:[~2001-07-18 23:00 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18 14:41 dewar
2001-07-18 15:29 ` Geoff Keating
2001-07-18 17:50   ` Joe Buck
2001-07-18 18:59 ` Michael Eager
2001-07-18 19:26   ` Justin Guyett
2001-07-19  9:05     ` Mark Mitchell
2001-07-19 19:28   ` akbar A.
2001-07-18 22:10 ` Per Bothner
2001-07-18 22:19   ` Joe Buck
2001-07-18 22:38     ` Per Bothner
2001-07-18 23:00       ` Alex Rosenberg [this message]
2001-07-19 14:05       ` Jonathan Larmour
  -- strict thread matches above, loose matches on Subject: below --
2001-07-19 23:16 Bernard Dautrevaux
2001-07-19 10:49 dewar
2001-07-19  4:33 dewar
2001-07-19  1:36 Bernard Dautrevaux
2001-07-19  2:40 ` Joseph S. Myers
2001-07-19  3:02 ` Roman Zippel
2001-07-19  3:12 ` Russ Allbery
2001-07-19  0:29 Bernard Dautrevaux
2001-07-19  1:16 ` Toon Moene
2001-07-18 20:02 dewar
2001-07-18 14:33 Geoff Keating
2001-07-18 13:21 Benjamin Kosnik
2001-07-17 20:00 Benjamin Kosnik
2001-07-17 17:37 mike stump
2001-07-17 13:04 Geoff Keating
2001-07-17 15:52 ` Joe Buck
2001-07-17 17:48   ` Per Bothner
2001-07-18  8:55     ` Joseph S. Myers
2001-07-17 18:24 ` Craig Rodrigues
2001-07-18  2:41 ` Andreas Jaeger
2001-07-18  9:03   ` H . J . Lu
2001-07-18 12:01     ` Joe Buck
2001-07-18 12:46       ` H . J . Lu
2001-07-18 13:22         ` Joe Buck
2001-07-18 13:31           ` H . J . Lu
2001-07-18 14:28             ` David Edelsohn
2001-07-18 15:03               ` Joern Rennecke
2001-07-18 15:12                 ` David Edelsohn
2001-07-18 15:24                   ` Joe Buck
2001-07-18 17:05                     ` H . J . Lu
2001-07-19  4:56                     ` Toon Moene
2001-07-18 15:41                 ` Joseph S. Myers
2001-07-18 16:23                   ` H . J . Lu
2001-07-18 12:18     ` Sergey Ostrovsky
2001-07-18 15:19       ` Ken Whaley
2001-07-18 15:30         ` Toon Moene
2001-07-18 15:59           ` Ken Whaley
2001-07-18 16:08             ` Toon Moene
2001-07-18 13:30   ` Gerald Pfeifer
2001-07-19  5:17     ` Andreas Jaeger
2001-07-19 12:23       ` Gerald Pfeifer
2001-07-18 19:07   ` LinuxVN
2001-07-18 13:44 ` Toon Moene

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B77BC590.45815%alexr@spies.com \
    --to=alexr@spies.com \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@redhat.com \
    --cc=jbuck@synopsys.com \
    --cc=per@bothner.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).