From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org,
Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Robert Yang : dbus-native: dbus-native: do_compile failed on selinux.c on CentOS 5.10
Date: Wed, 18 Jun 2014 10:03:42 +0200 [thread overview]
Message-ID: <20140618080342.GF2117@jama> (raw)
In-Reply-To: <20140617075959.D3DE350478@opal.openembedded.org>
[-- Attachment #1: Type: text/plain, Size: 4589 bytes --]
On Tue, Jun 17, 2014 at 07:59:59AM +0000, git@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: 7a2d2d81d8694806060f7bccfbdba42dc356d477
> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=7a2d2d81d8694806060f7bccfbdba42dc356d477
>
> Author: Robert Yang <liezhi.yang@windriver.com>
> Date: Mon May 26 21:39:46 2014 -0400
>
> dbus-native: dbus-native: do_compile failed on selinux.c on CentOS 5.10
>
> Found this error on CentOS 5.10, other distros may also has this
> problem, I think that we can disable the selinux for dbus-native:
>
> bus/selinux.c:327: error: array type has incomplete element type
This actually breaks dbus-native compilation for others, because it enables docs
| xmlto: xmllint validation tool not found or not executable.
| xmlto: Skipping validation... Please make sure xmllint is installed.
| xmlto: Can't continue, xsltproc tool not found or not executable.
| make[2]: *** [dbus-monitor.1] Error 3
| make[2]: *** Waiting for unfinished jobs....
| xmlto: xmllint validation tool not found or not executable.
| xmlto: Skipping validation... Please make sure xmllint is installed.
| xmlto: xmllint validation tool not found or not executable.
| xmlto: Skipping validation... Please make sure xmllint is installed.
| xmlto: xmllint validation tool not found or not executable.
| xmlto: Skipping validation... Please make sure xmllint is installed.
| xmlto: Can't continue, xsltproc tool not found or not executable.
| xmlto: Can't continue, xsltproc tool not found or not executable.
| xmlto: Can't continue, xsltproc tool not found or not executable.
| xmlto: xmllint validation tool not found or not executable.
| xmlto: Skipping validation... Please make sure xmllint is installed.
| xmlto: xmllint validation tool not found or not executable.
| xmlto: Skipping validation... Please make sure xmllint is installed.
| xmlto: Can't continue, xsltproc tool not found or not executable.
| make[2]: *** [dbus-faq.html] Error 3
| make[2]: *** [dbus-uuidgen.1] Error 3
| xmlto: xmllint validation tool not found or not executable.
| xmlto: Skipping validation... Please make sure xmllint is installed.
| xmlto: Can't continue, xsltproc tool not found or not executable.
| make[2]: *** [dbus-daemon.1] Error 3
| make[2]: *** [dbus-launch.1] Error 3
| make[2]: *** [dbus-send.1] Error 3
| xmlto: Can't continue, xsltproc tool not found or not executable.
| xmlto: xmllint validation tool not found or not executable.
| xmlto: Skipping validation... Please make sure xmllint is installed.
| xmlto: Can't continue, xsltproc tool not found or not executable.
| make[2]: *** [dbus-cleanup-sockets.1] Error 3
| make[2]: *** [dbus-run-session.1] Error 3
| make[2]: Leaving directory `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/dbus-native/1.8.2-r0/build/doc'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/dbus-native/1.8.2-r0/build'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/dbus-native/1.8.2-r0/temp/log.do_compile.2550)
NOTE: recipe dbus-native-1.8.2-r0: task do_compile: Failed
>
> [YOCTO #6374]
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> ---
>
> meta/recipes-core/dbus/dbus.inc | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
> index 5b2a056..01108c9 100644
> --- a/meta/recipes-core/dbus/dbus.inc
> +++ b/meta/recipes-core/dbus/dbus.inc
> @@ -86,6 +86,8 @@ EXTRA_OECONF = "--disable-tests \
> --disable-systemd \
> --without-dbus-glib"
>
> +EXTRA_OECONF_class-native = "--disable-selinux"
> +
> PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'systemd', '', d)} \
> ${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'x11', '', d)}"
> PACKAGECONFIG_class-native = ""
>
> --
> _______________________________________________
> Openembedded-commits mailing list
> Openembedded-commits@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-commits
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next parent reply other threads:[~2014-06-18 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140617075959.D3DE350478@opal.openembedded.org>
2014-06-18 8:03 ` Martin Jansa [this message]
2014-06-18 8:28 ` [oe-commits] Robert Yang : dbus-native: dbus-native: do_compile failed on selinux.c on CentOS 5.10 Robert Yang
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=20140618080342.GF2117@jama \
--to=martin.jansa@gmail.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-commits@lists.openembedded.org \
--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.