This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Use longlong.h?
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Joern Rennecke <amylaar at spamcop dot net>
- Cc: Jeff Johnston <jjohnstn at redhat dot com>, newlib at sourceware dot org, gcc at gnu dot org
- Date: Wed, 7 Jan 2009 15:28:07 +0000 (UTC)
- Subject: Re: Use longlong.h?
- References: <20081217193540.5gm514vmcgkgkk0w-nzlynne@webmail.spamcop.net> <4963E926.1030207@redhat.com> <20090107071502.ty3pfzpk2socc80o-nzlynne@webmail.spamcop.net>
On Wed, 7 Jan 2009, Joern Rennecke wrote:
> Yes, that is the longlong.h I was referring to. I thought that it had the
> gcc library exception, so that we could simply autoconf its use in newlib.
> However, looking at the file, I see that you are correct, it is GPL without
> a library exception.
> This is not only a problem with the use in newlib I was thinking of, but
> also with its usage in gcc by libgcc, because it means that programs linked
> with libgcc have to be GPL licensed when distributed unless the user has a
> separate license from the included code from the author which allows
> distribution other licenses.
As code shared by GCC and glibc I would suggest the same license notice as
soft-fp (LGPL >= 2.1 + exception) to allow an identical file to be shared.
(Indeed, soft-fp uses this header.) The version in GMP diverged long ago
so sharing the file with that may not be feasible.
--
Joseph S. Myers
joseph@codesourcery.com