public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Michael DuPont <mdupont777@yahoo.com>
To: Joe Buck <Joe.Buck@synopsys.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Linkage of GPLed GCC to Closed Source via XML or Perl
Date: Fri, 01 Mar 2002 08:01:00 -0000	[thread overview]
Message-ID: <20020301160142.37810.qmail@web13305.mail.yahoo.com> (raw)
In-Reply-To: <200202281555.HAA18124@atrus.synopsys.com>

It is very simple now. I am not trying to get around
the GPL, Joe, so you can see that your statement
should be retracted.

The output of the introspector is source code in xml
format. That is covered by the GPL. Later queried from
the database, it is also source code, just in a
different form.

FROM THE GNU FAQ : 
"In what cases is the output of a GPL program covered
by the GPL too?
Only when the program copies part of itself into the
output."

Well the xml output of the modifications to the GCC
contain  : 
1. the structure of the tree_node from the tree.h
2. the source code of the program that is compiled.

That is basically source code, just in a different
form. Therefore the introspector is not only a derived
work, but its output is also a form a source code that
is gpled.

Mike

=====
James Michael DuPont

__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com

  reply	other threads:[~2002-03-01 16:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28  4:04 James Michael DuPont
2002-02-28  8:07 ` Joe Buck
2002-03-01  8:01   ` James Michael DuPont [this message]
2002-03-01  8:55     ` Joe Buck
2002-03-02  1:21       ` James Michael DuPont
2002-03-03 18:35         ` Bryce McKinlay
2002-03-03 18:58           ` Diego Novillo
2002-03-03 22:52             ` James Michael DuPont
2002-03-03 22:52           ` James Michael DuPont
2002-03-03 19:39         ` Alexandre Oliva
2002-03-03 23:46           ` James Michael DuPont
2002-02-28  8:54 James Michael DuPont
2002-02-28 10:27 ` Joe Buck
2002-02-28 11:22 Bernard Dautrevaux
2002-02-28 12:17 ` Joe Buck
2002-02-28 11:46 mike stump
2002-02-28 12:40 James Michael DuPont
2002-02-28 20:32 Robert Dewar
2002-02-28 20:44 Robert Dewar
2002-02-28 21:56 Robert Dewar
2002-02-28 22:51 ` Daniel Berlin
2002-03-01  9:34 Bernard Dautrevaux
2002-03-02  1:26 ` James Michael DuPont
2002-03-03 19:06 Robert Dewar
2002-03-03 19:14 ` Diego Novillo
2002-03-03 23:27 ` James Michael DuPont
2002-03-04  5:40   ` Diego Novillo
2002-03-04  1:52 Robert Dewar
2002-03-04  1:56 ` James Michael DuPont
2002-03-07 13:10 ` Florian Weimer
2002-03-07 14:32 Robert Dewar

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=20020301160142.37810.qmail@web13305.mail.yahoo.com \
    --to=mdupont777@yahoo.com \
    --cc=Joe.Buck@synopsys.com \
    --cc=gcc@gcc.gnu.org \
    /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).