Messages in this thread | | | Date | Sat, 16 Nov 2002 00:49:43 -0500 | From | Jeff Garzik <> | Subject | Re: Why can't Johnny compile? |
| |
Dan Kegel wrote:
> john slee wrote: > > > now 2.5-bk is far from it. last i checked allmodconfig (a couple of > > days ago) there was major breakage all over llc, scsi, video, sound, ... > > which kinda masks any breakages you might have introduced. > > Hrmph. Y'know, maybe it's time for us to collectively put our > feet down, get 2.5-linus to the point where everything compiles, > and keep it there. After all, we are supposedly trying to > *stabilize* 2.5. It isn't stable if it doesn't compile...
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.
But like I said, patches welcome.
Jeff
- 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/
| |