This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Libiberty licensing
- To: dstarner98 at aasaa dot ofe dot org, law at cygnus dot com
- Subject: Re: Libiberty licensing
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Date: Mon, 18 Oct 1999 11:29:29 -0400 (EDT)
- Cc: gcc at gcc dot gnu dot org
> From: Jeffrey A Law <law@cygnus.com>
>
> In message <19991017214949.A21083@x8b4e53cd.dhcp.okstate.edu>you write:
> > Recently, a new file was added to libiberty - hashtab.c. The
> > license on the top of the file says that libiberty is under the
> > GNU Library General Public License (which corresponds to other
> > older files). strtod.c says that libiberty is under the GNU
> > GPL, with a linking exception. floatformat.c claims to be part
> > of GDB, but is linked into libiberty and is under the GPL with
> > no exception. What license is libiberty supposed to be under?
> >
> > As a final note, I find that calloc.c has no license or copyright
> > information attached, which may be a problem no matter what license
> > libiberty is under.
>
> There is no single license for libiberty. Each file has its own license.
> jeff
Since I wrote calloc.c, I added a notice releasing it into the public
domain, as is the case much of the rest of libiberty's simple
replacement functions.
Note, I don't think calloc.c is actually linked in on any system in
use today since they all have it already in their libc. :-)
--Kaveh
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Qwest Internet Solutions