This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Linkage of GPLed GCC to Closed Source via XML or Perl

Thanks for you ideas,
see below for my comments.
--- Alexandre Oliva <> wrote:
> On Mar  2, 2002, James Michael DuPont

> IANAL, so don't take this as legal advice, but my
> understanding is
> that the issue is not as simple as *claiming* that
> the output of your
> tool is derived work in order to have rights over
> defining its
> license. 
Yes, that is why this advise to get a lawer keeps on
coming up, my opinion is not that important later when
the issue comes up in court. 
I keep on bringing up my opinon to try and gain on a
consensus on what to do next.

> Whether something is a derived work of
> something else or not
> is covered by copyright law.  Even if you'd add some
> boilerplate
> license code to any output your program emits, or
> even intertwine your
> own code with it so as to make it more and more
> dependent on your
> program, which would make it easier to show that
> it's work derived
> from yours, if the user managed to extract all parts
> that were
> copyrighted by you from your output, they might have
> a point in
> claiming they can choose the license of the
> remainder of the output
> however they like.
This is what I brought up on gnu.discuss.misc.
The issue comes back down to deparsing the asts once
they are  in the external form, then the result of
that would only be the input code, andthe code to
deparse  might be a derived work.

> So make sure you get RMS to talk to FSF lawyers
> about this before you do something that might harm
the GNU project, if you can't afford a lawyer

I aggree %100 and I have already started this process.
As I pointed out, there are other usages of the
compiler that might fall under this problemm. 
1.The dumping of graphs to graphvis (which is not GPL)
2.The parsing of the original c-dump output using
3.The usage of GCC_XML in CABLE to create function and
typewrapper code.

These other projects and functions of gcc might be
affected by such a desision and really IMHO will have
to be looked into by the FSF independently of my

Thanks for your advise, before I do any more licencing
I will be sure to submit the idea to FSF before
publishing it.


James Michael DuPont

Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]