From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Could not find dbus-daemon in our root file system
Date: Sun, 1 Aug 2010 14:43:56 -0700 [thread overview]
Message-ID: <20100801214356.GB30928@gmail.com> (raw)
In-Reply-To: <76E258664B189C4CBEF125491CA11ECC9455F8DE76@KCINPUNHJCMS01.kpit.com>
On (17/07/10 13:11), Soumya R wrote:
> Hi All,
>
> I am working on openembedded form past few days for Au1350 mipsel architecture. I need to include
> dbus-daemon where should i include this?. I have included dbus-deamon-proxy_git.bb in dbus in recipes and also
> in task-qte-toolcain-target.bb..I have build a root file system and toolchain from it.. But i could not find the dbus-deamon
> binary in our rfs.. Please suggest me if i am doing anything wrong..
you need to add dbus to your image task thru RDEPENDS
>
>
> Regards,
> soumya
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-08-01 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 7:41 Could not find dbus-daemon in our root file system Soumya R
2010-08-01 21:43 ` Khem Raj [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=20100801214356.GB30928@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.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