Re: .i2c-old.ver.d: No such file or directory

Ricky Beam (jfbeam@bluetronic.net)
Wed, 19 Jun 2002 14:01:07 -0400 (EDT)


On Mon, 17 Jun 2002, Kai Germaschewski wrote:
>On Mon, 17 Jun 2002, Toby Inkster wrote:
>> Below are the last few lines of output before the errors start. I can send my .config if anyone thinks it might help.
...
>> i2c-old.c:17:27: linux/i2c-old.h: No such file or directory
>
>The problem is that the i2c code is currently broken, it includes
>linux/i2c-old.h which doesn't exist. You'll see the error much more
>clearly if you run "make KBUILD_VERBOSE= dep" ;)

Yes. This is due to the "New and Improved Build System (tm)". (It's not
really new -- kbuild has been around as an option for a long time. And
it's very certainly *not* currently an improvement.) Get used to a lot
being broken in interesting ways for a while.

I just love the way the road to progress is paved with a high density of
nuclear land mines. What a very lovely mess kbuild integration is creating.

I like the idea of "build in one pass", but that's kind of annoying in a
very broken development branch. When I enter "make bzImage" that and only
that is what I (and almost everyone who builds kernels) expect to be built.

As one who used to manage source code for a living, let me share a simple
rule: never break the build system; when the build is broken, NO ONE gets
anything done. One cannot completely replace a build environment over
night. (esp. when there are as many fingers in the pie as Linux.)

--Ricky

-
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/