tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] incorrect/missing license files


From: Thomas Preud'homme
Subject: Re: [Tinycc-devel] incorrect/missing license files
Date: Sat, 28 Jun 2014 19:32:38 +0800
User-agent: KMail/4.12.4 (Linux/3.14-1-amd64; KDE/4.13.1; x86_64; ; )

Le vendredi 27 juin 2014, 20:45:55 Vincent Lefevre a écrit :
> On 2014-06-27 11:30:54 -0500, Evan Langlois wrote:
> > Stupid legal question.   If TCC is GPL (rather than lesser GPL) and you
> > link with libtcc, then you would end up with software that was GPL.  This
> > may be significant.   Additionally, and start-up object files that TCC
> > generates may be considered "linking with tcc".
> 
> I'm not sure, due to the GPL system library exception.

There is some disagreement over what that exception means. As far as I know, 
it only applies if the software is usually found on systems. I doubt tcc 
applies here.

However, given the list of files under GPL, it seems perfectly possible to 
build a libtcc that is not GPL. Let's look at the list again:

*  il-opcodes.h

No problem if you don't build this target

*  lib/libtcc1.c

All the author of this file (except 2 lines of mingodad) agreed to relicense 
their work. I know the RELICENSING file only consider file copyright and 
consider that someone cannot have a copyright by contributing to an existing 
file. I believe this is wrong but from the exchange on this list, it seems 
obvious that all the contributor of this file agree to relicense whatever is 
needed in tcc.

  texi2pod.pl

Not needed to build libtcc, only for the documentation.

  win32/tools/tiny_impdef.c

Written by grischka. Grischka, maybe you could write a star * in RELICENSING 
for the file/feature part?

Best regards,

Thomas

Attachment: signature.asc
Description: This is a digitally signed message part.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]