Re: Why can't Johnny compile?

Patrick Finnegan (pat@purdueriots.com)
Sat, 16 Nov 2002 01:04:35 -0500 (EST)


On Sat, 16 Nov 2002, Jeff Garzik wrote:

> Most of the stuff that doesn't compile (or link) is typically stuff that
> is lesser used, or never used. A lot of the don't-compile complaints
> seem to be vocal-minority type complaints or "why can't I build _every_
> module in the kernel?" complaints. Ref allmodconfig, above.
>
> If people want to get rivafb or an ancient ISA net driver building
> again... patches welcome. But I don't think calls for the kernel to
> compile 100 percent of the drivers is realistic or even reasonable.
> Some of the APIs, particularly SCSI, are undergoing API stabilization.
> And SCSI is an excellent example of drivers where
> I-dont-have-test-hardware patches to fix compilation may miss subtle
> problems -- and then six months later when the compileable-but-broken
> SCSI driver is used by a real user, we have to spend more time in the
> long run tracking down the problem.

Wouldn't it then seem reasonable to remove things from the kernel that
have been broken for a long time, and no one seems to care enough to fix?
I know of at least one driver (IOmega Buz v4l) that seems to have fallen
into disrepair possibly since before 2.4.0, and as far as I know has not
been repaired since then.

Pat

--
Purdue Universtiy ITAP/RCS
Information Technology at Purdue
Research Computing and Storage
http://www-rcd.cc.purdue.edu

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/