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.
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 <[email protected] <mailto:[email protected]>>
===================================================================
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
Michael Krufky wrote:
> Cyber Dog wrote:
>
>> #
>> # 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):
I forgot to mention... You CAN apply the patch in my previous message if
it bothers you enough, but it won't have any real affect on your kernel,
as those built-in.o are all empty anyway.
>
> 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 <[email protected]
> <mailto:[email protected]>>
...and I hate it when Thunderbird does stuff like this when I cut&paste
email addresses :-(
--
Michael Krufky