From: Chuck Ebbert <76306.1226@compuserve.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Johannes Stezenbach <js@linuxtv.org>, Adrian Bunk <bunk@stusta.de>
Subject: Why build empty object files in drivers/media?
Date: Thu, 21 Jul 2005 23:06:21 -0400 [thread overview]
Message-ID: <200507212309_MC3-1-A534-95EE@compuserve.com> (raw)
I have this in my .config file for 2.6.13-rc3:
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
And yet these completely empty files are being built:
$ find drivers/media -name built-in.o | xargs ls -go
-rw-rw-r-- 1 305 Jul 16 00:20 drivers/media/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/common/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/b2c2/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/bt8xx/built-in.o
-rw-rw-r-- 1 305 Jul 16 00:20 drivers/media/dvb/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/cinergyT2/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/dvb-core/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/dvb-usb/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/frontends/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/pluto2/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/ttpci/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/ttusb-budget/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/dvb/ttusb-dec/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/radio/built-in.o
-rw-rw-r-- 1 8 Jul 16 00:20 drivers/media/video/built-in.o
$ size drivers/media/built-in.o
text data bss dec hex filename
0 0 0 0 0 drivers/media/built-in.o
__
Chuck
next reply other threads:[~2005-07-22 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 3:06 Chuck Ebbert [this message]
2005-07-22 19:46 ` Sam Ravnborg
2005-07-22 21:18 ` Olaf Dietsche
2005-07-23 0:09 ` Sam Ravnborg
2005-07-24 6:10 ` Keith Owens
[not found] ` <20050724085845.GA8018@mars.ravnborg.org>
2005-07-24 17:29 ` Johannes Stezenbach
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=200507212309_MC3-1-A534-95EE@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=bunk@stusta.de \
--cc=js@linuxtv.org \
--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
all inboxes | Powered by JetHome®