On Thu, 1 Jun 2006, Mauro Carvalho Chehab wrote:
> > > > Isn't it just a matter of using make xconfig or make gconfig or make
> > > > menuconfig to select the drivers to build, and then not selecting
> > > > micro PCM 20? Or just edit v4l/.myconfig by and and set the MIRO
> > > > variables to 'n'?
> In fact, if you don't select miro pcm20 at make
> menuconfig/xconfig/gconfig, it will update both .config and .myconfig
> files, allowing you to compile kernel without support for those boards
> with just
> make
This is a problem when someone doesn't have the kernel source, just the
distribution binary, since they don't have the conf programs. I think that
some distributions come with enough code in /lib/modules/`uname -r`/build to
be able to build out-of-tree drivers, but don't have conf/qconf/lxdialog and
so on. make allmodconfig doesn't need these programs, so users are ok there,
but it turns on drivers they can't build, so they still have problems.
> distro dependent, since it will depend on where are the .config file to
> be applied. This is generally under /boot/config-x.y.z, but not always.
> Also, if you use to compile with another kernel (using make build), what
> config should be used?
Shouldn't it always be in $(KDIR)/.config? If you try to build against a
non-configured kernel source tree, you will not get very far.
> > > I hope this explanation helps somebody to construct a fix to be merged
> > > into the repository. (hint, hint)
> The explanation is ok. Maybe you may convert it into a BUILD file, so
> that we can include it at the repository :)
Is that directed to Michael Krufky, who wrote that sentence, or to me?
> > I haven't had so much luck with my changes to the build system getting merged.
> I think I've commited some proposed changes by you.
The part of the build system that builds the kernel's conf programs doesn't
work with many 2.6.x series kernels. I had a patch which made it work with
all 2.6 kernels and was, I think, a better way to go about it. Maybe I will
try again.