All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Rob Landley <rob@landley.net>,
	"Ihar 'Philips' Filipau" <filia@softhome.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined.
Date: Wed, 20 Aug 2003 20:02:29 -0400	[thread overview]
Message-ID: <3F440C15.1050301@pobox.com> (raw)
In-Reply-To: <20030820234810.GA24970@mail.jlokier.co.uk>

Jamie Lokier wrote:
> Well, I've done quite a bit of
> 
> 	#ifdef __i386__
> 	#define __NR_futex	240
> 	#elif defined (__alpha__)
> 	#define __NR_futex	394
> 	#elif defined (__mips__)
> 	... etc. ...
> 	#endif
> 
> In order to distribute programs which compile with a distro's libc but
> will take advantage of features in later kernels when run on them.
> 
> That's really unpleasant.  So, in revenge, here's an annoying question:

agreed.


> If userspace applications are ultimately compiled using Linux header
> files, indirectly included via Glibc or some other libc, and the
> kernel header files are GPL (version 2 only; not LGPL or any later
> GPL), isn't distributing those binary applications a gross violation
> of the GPL in some cases?

It's come up before, so it's not necessarily an original, annoying 
question ;-)

My non-lawyer guess would be, the structures and defines are required 
for Linux interoperability; that may be a factor.  static inline 
functions in headers, i.e. real code, is another matter too.

One way or another (direct inclusion, or via glibc-kernheaders pkg) the 
headers today are GPL'd not LGPL'd... so I suppose it remains the realm 
of lawyers...

IANAL,

	Jeff




  reply	other threads:[~2003-08-21  0:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lRjc.6o4.3@gated-at.bofh.it>
     [not found] ` <lRjg.6o4.15@gated-at.bofh.it>
     [not found]   ` <lWLS.39x.5@gated-at.bofh.it>
     [not found]     ` <lWLZ.39x.29@gated-at.bofh.it>
2003-08-18 18:54       ` [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined Ihar 'Philips' Filipau
2003-08-18 19:04         ` Jeff Garzik
2003-08-19 12:32           ` Rob Landley
2003-08-19 17:26             ` Jeff Garzik
2003-08-19 21:38               ` Will uclibc be supported in 2.6? (was Re: [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined.) Rob Landley
2003-08-19 21:47                 ` Jeff Garzik
2003-08-20  1:42               ` [PATCH] Re: [PATCH] scsi.h uses "u8" which isn't defined Erik Andersen
2003-08-20 23:48             ` Jamie Lokier
2003-08-21  0:02               ` Jeff Garzik [this message]
2003-08-22  0:32                 ` Rob Landley
2003-08-22  0:50                   ` Chris Friesen
2003-08-22  1:58                     ` Rob Landley
2003-08-22  0:54                   ` Jeff Garzik
2003-08-18 20:40         ` Sam Ravnborg
2003-08-18 12:36 Andries.Brouwer
  -- strict thread matches above, loose matches on Subject: below --
2003-08-18 12:19 Andries.Brouwer
2003-08-18 12:24 ` Christoph Hellwig
2003-08-18 18:08   ` Sam Ravnborg
2003-08-18 18:14     ` Jeff Garzik
2003-08-18 15:21 ` Linus Torvalds
2003-08-18 15:32   ` Jeff Garzik
2003-08-18 16:13 ` Patrick Mansfield

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=3F440C15.1050301@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=filia@softhome.net \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.