Le mardi 01 juillet 2014, 06:42:09 grischka a écrit :
And the author is?
libtcc1.c:148:
/* most of this code is taken from libgcc2.c from gcc */
Hum, no comment :-D
Since libtcc1.c is part of a library (and tcc doesn't have LTO) I'd
rather suggest to put everything not
Thomas Preud'homme wrote:
If both of you answer yes, could you commit the change Grischka?
Change the FSF header in lib/libtcc1.c? I'm not sure they would
agree. However it allows being linked into any program anyway.
Why would they have to agree? They are not author of this file. Only the
On 2014-06-28 19:32:38 +0800, Thomas Preud'homme wrote:
Le vendredi 27 juin 2014, 20:45:55 Vincent Lefevre a écrit :
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
Le dimanche 29 juin 2014, 12:40:04 Vincent Lefevre a écrit :
On 2014-06-28 19:32:38 +0800, Thomas Preud'homme wrote:
Le vendredi 27 juin 2014, 20:45:55 Vincent Lefevre a écrit :
I'm not sure, due to the GPL system library exception.
There is some disagreement over what that exception
Thomas Preud'homme wrote:
It should yes. Grischka, Shinichiro, James: do you agree to relicense your
contributions to lib/libtcc1.c under the BSD variants in RELICENSING file?
Is not that what people listed in RELICENSING already did agree to?
If both of you answer yes, could you commit the
On 2014-06-29 23:57:08 +0200, grischka wrote:
Change the FSF header in lib/libtcc1.c? I'm not sure they would
agree. However it allows being linked into any program anyway.
How about *adding* the BSD copyright notice to this header?
i.e. any future commit should be done under these two
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.
TCC is distributed with a file COPYING, corresponding to the
Lesser GPL. This is incorrect. Such a file is normally called
COPYING.LIB, and COPYING should contain the GPL. This is
important because some files are distributed under the GPL only:
il-opcodes.h
lib/libtcc1.c
texi2pod.pl
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.
So ... anyone want to straighten
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
10 matches
Mail list logo
