public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@linuxtv.org>
To: Cyber Dog <cyberdog3k@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why is DVB stuff compiling?
Date: Mon, 17 Oct 2005 23:02:04 -0400	[thread overview]
Message-ID: <435465AC.3070506@linuxtv.org> (raw)
In-Reply-To: <cbb8f04c0510171929j3378220cp48831caa1b8d478@mail.gmail.com>

Cyber Dog wrote:

>I'm a bit confused here.  I have a custom kernel configuration, and
>I've trimmed out most of the multimedia aspects sound/video/etc
>because this is for a server machine.  I was just recompiling, and I
>noticed there was still some media stuff compiling:
>
> LD      drivers/input/serio/built-in.o
>  LD      drivers/media/common/built-in.o
>  LD      drivers/media/dvb/b2c2/built-in.o
>  LD      drivers/media/dvb/bt8xx/built-in.o
>  LD      drivers/media/dvb/cinergyT2/built-in.o
>  LD      drivers/media/dvb/dvb-core/built-in.o
>  LD      drivers/media/dvb/dvb-usb/built-in.o
>  LD      drivers/media/dvb/frontends/built-in.o
>  LD      drivers/media/dvb/pluto2/built-in.o
>  LD      drivers/media/dvb/ttpci/built-in.o
>  LD      drivers/media/dvb/ttusb-budget/built-in.o
>  LD      drivers/media/dvb/ttusb-dec/built-in.o
>  LD      drivers/media/dvb/built-in.o
>  LD      drivers/media/radio/built-in.o
>  LD      drivers/media/video/built-in.o
>  LD      drivers/media/built-in.o
>  LD      drivers/misc/built-in.o
>  CC      drivers/net/Space.o
>
>This confuses me, because as I said, I'm not including multimedia in
>the kernel.  I checked the config and I see the following:
>
>#
># Multimedia devices
>#
># CONFIG_VIDEO_DEV is not set
>
>#
># Digital Video Broadcasting Devices
>#
># CONFIG_DVB is not set
>
>Which is what I would expect.  So why are these things compiling into
>the kernel even if they're not selected? Or am I missing something
>about the process?  Kernel 2.6.13.3 here.  Thanks.
>  
>
If you go look, you will notice that all of those built-in.o are zero 
bytes large.  We've already fixed this in kernel 2.6.14 by preventing 
the build of these empty units with the following patch (you can safely 
apply it to 2.6.13.y):

Don't build empty built-in.o when DVB/V4L is not configured.
Thanks to Sam Ravnborg and Keith Owens.

Signed-off-by: Johannes Stezenbach <js@linuxtv.org <mailto:js@linuxtv.org>>
===================================================================
RCS file: /cvs/linuxtv/dvb-kernel/linux/drivers/media/Makefile,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- dvb-kernel/linux/drivers/media/Makefile	2003/01/09 10:28:42	1.1
+++ dvb-kernel/linux/drivers/media/Makefile	2005/07/24 17:30:02	1.2
@@ -2,4 +2,7 @@
 # Makefile for the kernel multimedia device drivers.
 #
 
-obj-y        := video/ radio/ dvb/ common/
+obj-y := common/
+obj-$(CONFIG_VIDEO_DEV) += video/
+obj-$(CONFIG_VIDEO_DEV) += radio/
+obj-$(CONFIG_DVB)       += dvb/




Regards,

Michael Krufky


  reply	other threads:[~2005-10-18  3:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  2:29 Why is DVB stuff compiling? Cyber Dog
2005-10-18  3:02 ` Michael Krufky [this message]
2005-10-18  3:07   ` Michael Krufky

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=435465AC.3070506@linuxtv.org \
    --to=mkrufky@linuxtv.org \
    --cc=cyberdog3k@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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