From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Libiberty license roundup (questions/potential problems)
Date: Fri, 23 May 2003 22:59:00 -0000 [thread overview]
Message-ID: <20030523225905.GA30461@doctormoo> (raw)
Looking at libiberty, it seems to be under a mass of different licences.
There are several problems here. The first are the (non-autogenerated) files
with no explicit copyright notice or licence. I would assume that they were
under the terms of the "rest of libiberty", except that it's not clear
what that is.
The second are the two files with copyright and no license listed.
The third are the BSD files with no explicit modification permission.
The fourth are the various files which aren't sure what they're part of; I'd
like permission to just fix those all to claim to be part of libiberty, unless
there's some reason not to.
The fifth is the question of why some are LGPL, some are GPL, some are GPL
with linking exception, and one is LGPL with linking exception. Effectively
the library as a whole is under GPL in general, it would seem; what purpose
do the other licenses serve?
* Verbatim only
COPYING.LIB (copy of LGPL 2.1)
copying-lib.texi (copy of LGPL 2.1)
* GNU FDL 1.2 or later (with TeX permission)
libiberty.texi
* No license or copyright on individual file
ChangeLog
README
aclocal.m4
bcopy.c
config.in (autogenerated)
config.table
configure.in
copysign.c
ffs.c
fnmatch.txh
functions.texi (autogenerated)
getpagesize.c
getpwd.c
makefile.vms
memchr.c
mpw-make.sed (probably obsolete?)
obstacks.texi
pexecute.txh
strdup.c
tmpnam.c
vmsbuild.com
vprintf.c
waitpid.c
* No license, FSF copyright
vfprintf.c
* No license, University of California copyright
xatexit.c
* LGPL 2 or later
(as part of "libiberty library")
Makefile.in
argv.c
asprintf.c
choose-temp.c
concat.c
fdmatch.c
gather-docs
getruntime.c
hashtab.c
hex.c
lbasename.c
maint-tool
make-temp-file.c
mempcpy.c
mpw.c
pex-common.h
pex-djgpp.c
pex-mpw.c
pex-msdos.c
pex-os2.c
pex-unix.c
pex-win32.c
safe-ctype.c
spaces.c
stpncpy.c
vasprintf.c
xexit.c
xmalloc.c
(as part of the "GNU C Library")
regex.c
(Boilerplate is for "GNU C Library is free software...", but up top says
"based on ... in the GNU C Library", not "This file is part of...",
so a little confused.)
mkstemps.c
putenv.c
setenv.c
* GPL 2 or later
(as "this program")
_doprnt.c
fnmatch.c
getopt.c
getopt1.c
md5.c
objalloc.c
obstack.c
physmem.c
ternary.c
(as part of "GNU CC")
fibheap.c
partition.c
sort.c
splay-tree.c
(as part of GDB)
floatformat.c
(as part of "libiberty library")
lrealpath.c
(as part of "libiberty library", but confused. Says "You should have
received a copy of the GNU General Public License along with GNU CC"...)
strtod.c
(This one's messed up. It says "This file is part of libiberty.
GCC is free software...")
make-relative-prefix.c
* GPL 2 or later, with special linking exception
(as part of "libiberty library")
clock.c
snprintf.c
vsnprintf.c
vsprintf.c
(as part of "GNU CC")
cp-demangle.c
dyn-string.c
* LGPL 2 or later, with special linking exception (!)
(as part of "libiberty library")
cplus-dem.c
* public domain
alloca.c
atexit.c
basename.c
bcmp.c
bzero.c
calloc.c
getcwd.c
insque.c
memcmp.c
memcpy.c
memmove.c
memset.c
rename.c
sigsetmask.c
strchr.c
strerror.c
strncmp.c
strrchr.c
strsignal.c
strstr.c
vfork.c
xmemdup.c
xstrdup.c
xstrerror.c
* BSD (U of C)
(usual long version of BSD license)
bsearch.c
random.c
strtol.c
strtoul.c
(unusual, shorter version of the license, missing the "with
or without modification" clause)
strcasecmp.c
strncasecmp.c
next reply other threads:[~2003-05-23 22:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 22:59 Nathanael Nerode [this message]
2003-05-23 23:06 ` DJ Delorie
2003-05-23 23:59 ` Mike Stump
2003-05-24 1:23 ` Andrew Cagney
2003-05-24 1:34 ` DJ Delorie
2003-05-28 19:27 ` Andrew Cagney
2003-05-28 22:08 ` Joe Buck
2003-05-30 17:27 ` David O'Brien
2003-05-30 18:59 ` DJ Delorie
2003-05-28 22:11 Robert Dewar
2003-05-28 22:23 ` Joe Buck
2003-05-28 22:23 Robert Dewar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030523225905.GA30461@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox