From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: glib2.0 and dbus dependency
Date: Fri, 11 Jan 2013 17:30:55 +0800 [thread overview]
Message-ID: <50EFDBCF.6030003@windriver.com> (raw)
In-Reply-To: <1757330.jo1AhcIeyl@yiqingliang-pc>
On 01/11/2013 02:31 AM, Yi Qingliang wrote:
> when compiling using 4 threads, I got following error.
> the glib2.0-native want find dbus header file.
> If I compiled dbus/dbus-natigve, and then compile glib2.0 OK.
>
> when grep glib2.0 bb files, I can't find dbus in dependency, why?
>
>
Hi,
What's the error message?
Cheers,
Chen Qi
>
>
> ERROR: Function failed: do_compile (see /mnt/src/arm9plf-
> build/tmp/work/x86_64-linux/glib-2.0-native/1_2.34.3-
> r0/temp/log.do_compile.28193 for further information)
> ERROR: Task 1851 (virtual:native:/mnt/src/optimus/poky/meta/recipes-
> core/glib-2.0/glib-2.0_2.34.3.bb, do_compile) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 929 tasks of which 925 didn't need to be rerun
> and 1 failed.
> Waiting for 0 running tasks to finish:
>
> Summary: 1 task failed:
> virtual:native:/mnt/src/optimus/poky/meta/recipes-
> core/glib-2.0/glib-2.0_2.34.3.bb, do_compile
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2013-01-11 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 18:31 glib2.0 and dbus dependency Yi Qingliang
2013-01-10 10:42 ` Martin Jansa
2013-01-11 9:18 ` Yi Qingliang
2013-01-11 1:52 ` Martin Jansa
2013-01-11 10:06 ` Yi Qingliang
2013-01-11 9:30 ` ChenQi [this message]
2013-01-12 9:21 ` Yi Qingliang
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=50EFDBCF.6030003@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.