public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Godefroy <thgodef@nerim.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG in Linux 2.6.16/2.6.16.1 (compilation failure of third party software)
Date: Wed, 29 Mar 2006 01:21:22 +0200	[thread overview]
Message-ID: <20060329012122.0c533fc6.thgodef@nerim.net> (raw)
In-Reply-To: <1143586271.11792.118.camel@mindpipe>

On Tue, 28 Mar 2006 17:51:11 -0500, Lee Revell wrote:

> On Tue, 2006-03-28 at 20:29 +0200, Thierry Godefroy wrote:
> > Paragon_NTFS_3.x.v5.1 fails to compile (with gcc v3.4.3) with the following
> > errors:
> 
> It's not a bug when an upgrade causes third party kernel modules not to
> compile - your code needs to be updated to work with 2.6.16.

Oh, yeah ?... Really ?... Please, read the errors before drawing hasted conclusions...
The errors occur after the mere #inclusion of Linux headers. Here is a simple "code"
which will trigger the error:

#ifndef __KERNEL__
#define __KERNEL__
#endif

#include <linux/module.h>

int main() {
	return 0;
}

And I don't see anything wrong in that code...

> Linux makes no effort to guarantee source or binary compatibility with
> out of tree kernel modules, or userspace code that includes kernel
> headers.

That's a pity... Non-regression should be guaranteed. The problem with Linux
is that each new version brings a load of incompatibilities with third parties
drivers (graphic cards, win/smart modems, wifi cards, etc, etc), most of which
using proprietary code which sources are unavailable to the end user. The fact
that Linux keeps breaking those drivers code is not going to encourage hardware
vendors to make Linux drivers for their products. For example, ATI takes a
couple of months to catchup with the kernel changes, and each time they release
a new driver the next Linux release breaks it. :-(

Thierry Godefroy.


  reply	other threads:[~2006-03-28 23:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 18:29 BUG in Linux 2.6.16/2.6.16.1 (compilation failure of third party software) Thierry Godefroy
2006-03-28 22:51 ` Lee Revell
2006-03-28 23:21   ` Thierry Godefroy [this message]
2006-03-29  4:42     ` Arjan van de Ven
     [not found] <5Vr7d-4VR-15@gated-at.bofh.it>
2006-03-28 23:03 ` Robert Hancock
     [not found] ` <5Vvkv-2MB-27@gated-at.bofh.it>
     [not found]   ` <5VvNw-3B1-3@gated-at.bofh.it>
2006-03-29  2:20     ` Robert Hancock

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=20060329012122.0c533fc6.thgodef@nerim.net \
    --to=thgodef@nerim.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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