From: "Hiroaki.Fuse@sony.com" <Hiroaki.Fuse@sony.com>
To: "libc-stable@sourceware.org" <libc-stable@sourceware.org>
Cc: "Hiroaki.Fuse@sony.com" <Hiroaki.Fuse@sony.com>
Subject: glibc-2.35-0ubuntu3 library in Ubuntu 22.04 include GPLv2 header file
Date: Mon, 3 Jul 2023 08:11:59 +0000 [thread overview]
Message-ID: <TYCPR01MB69631D6C8C625D00510BE74EEA29A@TYCPR01MB6963.jpnprd01.prod.outlook.com> (raw)
Dear all members,
I use Ubuntu 22.04 distribution for development.
While checking glibc license, I found that the license of following file is GPLv2
- glibc-2.35-0ubuntu3/include/programs/xmalloc.h
This file was created by following commit to original git repository. (2013-02-18)
- https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=6ff444c4184433586a8879376bd5006eb793499a
And "nss/nss_module.c" in glibc-2.35 includes "nscd/nscd.h" and "nscd/nscd.h" includes "include/programs/xmalloc.h"
nss/nss_module.c
- https://sourceware.org/git/?p=glibc.git;a=blob;f=nss/nss_module.c;h=f00bbd9e1ad255538526778a8ae732c9d8c64320;hb=refs/heads/release/2.35/master
nscd/nscd.h
- https://sourceware.org/git/?p=glibc.git;a=blob;f=nscd/nscd.h;h=f15321585b379b1c494b5688578f22d11761408a;hb=refs/heads/release/2.35/master
This mean that the license of "nss/nss_modules.c" is also GPLv2.
Because "libc.so.6" links the "nss/nss_modules.o", glibc-2.35-0ubuntu3 in Ubuntu 22.04 is also GPLv2.
I am confused because "glibc-2.35-0ubuntu3/README" in source code says following sentence.
The GNU C Library is free software. See the file COPYING.LIB for copying
conditions, and LICENSES for notices about a few contributions that require
these additional notices to be distributed. License copyright years may be
listed using range notation, e.g., 1996-2015, indicating that every year in
the range, inclusive, is a copyrightable year that would otherwise be listed
individually.
COPYING.LIB file is LGPLv2.1
I also checked the history of "nss/nss_module.c" and found following commit. (2020-12-04)
- https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f8847d83e17774ed5e9c0f75ef693680b91bcae4
Before above commit "nss/nss_module.c" did not include "nscd/nscd.h". In this case glibc is LGPLv2.1 .
I want to know the glibc maintainers opinions.
Regards,
next reply other threads:[~2023-07-03 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 8:11 Hiroaki.Fuse [this message]
2023-07-03 9:03 ` Florian Weimer
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=TYCPR01MB69631D6C8C625D00510BE74EEA29A@TYCPR01MB6963.jpnprd01.prod.outlook.com \
--to=hiroaki.fuse@sony.com \
--cc=libc-stable@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).