[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1182524599.14289.31.camel@gaivota>
Date: Fri, 22 Jun 2007 12:03:19 -0300
From: Mauro Carvalho Chehab <mchehab@...radead.org>
To: Jan Engelhardt <jengelh@...putergmbh.de>
Cc: Andreas Herrmann <andreas.herrmann3@....com>,
Roman Zippel <zippel@...ux-m68k.org>,
Oliver Neukum <oneukum@...e.de>,
linux-usb-devel@...ts.sourceforge.net, video4linux-list@...hat.com,
Toralf Förster <toralf.foerster@....de>,
luca.risolia@...dio.unibo.it, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Kconfig troubles when using menuconfig - Was: [patch]Re:
[linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in
zc0301_core.c
Em Sex, 2007-06-22 às 15:51 +0200, Jan Engelhardt escreveu:
> On Jun 22 2007 15:46, Andreas Herrmann wrote:
> >Hi,
> >
> >I am not sure whether it is related or not
> >But if you select USB as module but build your v4l_usb driver
> >into the kernel you also get compile errors.
> >Attached is a patch which will prevent this by changing the menuconfig
> >from bool to tristate.
> A config option that is not referenced in the Makefile...
> should it really be a tristate? In my opinion, changing it
> to tristate is just a workaround, but I don't know kconfig
> well enough to make bool Do The Right Thing in these situations myself :(
If USB is built as a module, the V4L USB modules should also be built as
a module. Otherwise, you will have compile errors, since some required
symbols on the drivers won't be linked into the kernel.
--
Cheers,
Mauro
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists