Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lloyd Sargent <lsargent@txdigital.com>
To: buildroot@busybox.net
Subject: [Buildroot] DBUS keeps getting installed...
Date: Wed, 8 Apr 2009 13:59:34 -0500	[thread overview]
Message-ID: <200904081359.35038.lsargent@txdigital.com> (raw)
In-Reply-To: <87prfnyoxt.fsf@macbook.be.48ers.dk>

> >>>>> "Lloyd" == Lloyd Sargent <lsargent@txdigital.com> writes:
>
> Hi,
>
>  Lloyd> Okay, I'm really puzzled. In my initial build I had
>  Lloyd> DBUS. Well, it was taking too many resources so I removed it.
>
>  Lloyd> Or so I thought.
>
>  Lloyd> In my next build, there was DBUS again!
>
>  Lloyd> So I checked the .config file:
>
>  Lloyd> # BR2_PACKAGE_DBUS is not set
>
>  Lloyd> Perhaps I misread something, but I was under the impression
>  Lloyd> that if DBUS was not set, then it wouldn't be included in the
>  Lloyd> build?
>
> That's true. Do you do a clean rebuild (rm -rf *build_*) or just edit
> the configuration and run make again? Packages don't automatically get
> removed from the target file system if you deselect them again.

AH! This I was not aware of (or did not properly understand).

This is most likely the issue.

> The other option is some other package needing dbus, and hence forcing
> it to be built, but then it should normally also depend / select it in
> Kconfig, so you should see it in your .config

No, nothing I'm building requires dbus.

      reply	other threads:[~2009-04-08 18:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 17:13 [Buildroot] DBUS keeps getting installed Lloyd Sargent
2009-04-08 17:47 ` sjhill at realitydiluted.com
2009-04-08 18:13   ` Lloyd Sargent
2009-04-08 17:58 ` Thomas Petazzoni
2009-04-08 18:20   ` Lloyd Sargent
2009-04-08 18:51     ` Peter Korsgaard
2009-04-08 18:34 ` Peter Korsgaard
2009-04-08 18:59   ` Lloyd Sargent [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=200904081359.35038.lsargent@txdigital.com \
    --to=lsargent@txdigital.com \
    --cc=buildroot@busybox.net \
    /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