From: Adrian Bunk <bunk@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] dvb: build failure fix
Date: Mon, 28 Apr 2008 21:04:57 +0300 [thread overview]
Message-ID: <20080428180457.GY2813@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080428162421.GA16566@elte.hu>
On Mon, Apr 28, 2008 at 06:24:21PM +0200, Ingo Molnar wrote:
>
> fix build failure found via x86.git randconfig testing:
>
> drivers/built-in.o: In function `tda829x_attach':
> : undefined reference to `tda827x_attach'
> drivers/built-in.o: In function `tda829x_attach':
> : undefined reference to `tda18271_attach'
>
> build failure is due to this nasty dependency:
>
> CONFIG_DVB_CORE=m but CONFIG_TUNER_TDA8290=y.
>
> the solution is to follow the DVB_CORE constraint in the Kconfig. It's
> not pretty but works.
It might work around the problem in your specific configuration, but
it's not the correct solution.
Please send your .config .
> Kconfig should be enhanced instead with a new keyword: "depends on
> instructure ..." that makes it clear that the dependent module can only
> be of equal or lesser link mode - but not =y while the infrastructure
> module is =m. But i digress.
What are you smoking?
That's exactly what "depends on" always did and still does.
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> drivers/media/Kconfig | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> Index: linux/drivers/media/Kconfig
> ===================================================================
> --- linux.orig/drivers/media/Kconfig
> +++ linux/drivers/media/Kconfig
> @@ -106,21 +106,21 @@ if VIDEO_TUNER_CUSTOMIZE
>
> config TUNER_XC2028
> tristate "XCeive xc2028/xc3028 tuners"
> - depends on I2C && FW_LOADER
> + depends on I2C && FW_LOADER && ((DVB_CORE = m && m) || (DVB_CORE = y))
>...
Your funny additions are equivalent to "&& DVB_CORE".
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-04-28 18:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 16:24 Ingo Molnar
2008-04-28 18:04 ` Adrian Bunk [this message]
2008-04-28 19:53 ` Ingo Molnar
2008-04-28 21:01 ` Adrian Bunk
2008-04-28 21:25 ` Mauro Carvalho Chehab
2008-04-28 21:29 ` mkrufky
2008-04-29 12:14 ` Ingo Molnar
2008-04-30 19:17 ` Mauro Carvalho Chehab
2008-04-30 19:28 ` Adrian Bunk
2008-04-30 19:31 ` mkrufky
2008-04-30 19:52 ` Mauro Carvalho Chehab
2008-04-30 20:01 ` Adrian Bunk
2008-04-30 22:32 ` mkrufky
2008-04-28 19:47 ` Mauro Carvalho Chehab
2008-04-28 20:30 ` Ingo Molnar
2008-04-28 21:03 ` Mauro Carvalho Chehab
2008-04-28 21:17 ` Ingo Molnar
2008-04-28 21:20 ` Ingo Molnar
2008-04-28 21:23 ` Ingo Molnar
2008-04-28 21:25 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080428180457.GY2813@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®