From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 current BK] Unnecesary code gets compiled in during build?
Date: Fri, 18 Feb 2005 12:03:51 -0800 [thread overview]
Message-ID: <42164A27.8010402@osdl.org> (raw)
In-Reply-To: <132340039.20050218204824@dns.toxicfilms.tv>
Maciej Soltysiak wrote:
> Hi,
>
> I am compiling 2.6.11-rc4-cset
>
> And I see during the compilation:
> 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/dibusb/built-in.o
> LD drivers/media/dvb/dvb-core/built-in.o
> LD drivers/media/dvb/frontends/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
>
> Although I know I have not added dvb, nor radio.
> How come this shows up?
It makes the kbuild system easier ?
It's probably fixable (I haven't looked), but I have
noticed the same thing that you are seeing.
Patches are welcome... if it needs to be fixed.
Did you notice how large those built-in.o files are?
> I am attaching my .config, it does not have DVB set.
--
~Randy
prev parent reply other threads:[~2005-02-18 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 19:48 [2.6 current BK] Unnecesary code gets compiled in during build? Maciej Soltysiak
2005-02-18 20:03 ` Randy.Dunlap [this message]
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=42164A27.8010402@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solt2@dns.toxicfilms.tv \
/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;
as well as URLs for NNTP newsgroup(s).