Re: LGPL v3 compatibilty (original) (raw)
- To: debian-legal@lists.debian.org
- Subject: Re: LGPL v3 compatibilty
- From: Walter Landry <walter@geodynamics.org>
- Date: Mon, 16 Jul 2007 13:27:30 -0700 (PDT)
- Message-id: <[🔎] 20070716.132730.58820216.walter@geodynamics.org>
- In-reply-to: <[🔎] yw1xlkdg6taa.fsf@thrashbarg.mansr.com>
- References: <[🔎] yw1x7ip094rl.fsf@thrashbarg.mansr.com> <[🔎] 20070716.120132.59474575.walter@geodynamics.org> <[🔎] yw1xlkdg6taa.fsf@thrashbarg.mansr.com>
Måns_Rullgård mans@mansr.com wrote:
Inside the kernel stdio is meaningless, so I'd hardly expect to find that header there. The only places in the kernel source where stdio.h is included are in tools, such as kconfig, only to be used for building the kernel or for testing purposes. This use of standard C header files is of course completely outside the scope of any license.
As for stdarg.h, it is provided by the compiler, and generally (including GCC) licensed without restrictions on use.
Thanks. That clarifies things. I could see how this might still be a problem if there are third party tools that use some internal kernel structures [1] and link to glibc, but I do not know of any such cases. I would expect such tools to be rare since it would be pretty fragile.
Cheers, Walter Landry wlandry@ucsd.edu
[1] If the tools use normal kernel interfaces, then the kernel's license disavows any claims on how they can be distributed.
Reply to:
- References:
- Re: LGPL v3 compatibilty
* From: Måns Rullgård mans@mansr.com - Re: LGPL v3 compatibilty
* From: Walter Landry wlandry@ucsd.edu - Re: LGPL v3 compatibilty
* From: Måns Rullgård mans@mansr.com
- Re: LGPL v3 compatibilty
- Prev by Date:Re: FYI, re `BCS OS Licence'
- Next by Date:Why is firebird in Debian?
- Previous by thread:Re: LGPL v3 compatibilty
- Next by thread:Re: LGPL v3 compatibilty
- Index(es):