From: Saul Wold <sgw@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] dbus-ptest: Disable python module check
Date: Mon, 15 Jul 2013 16:48:11 -0700 [thread overview]
Message-ID: <51E48A3B.6030607@linux.intel.com> (raw)
In-Reply-To: <1373919029-19108-5-git-send-email-mark.hatle@windriver.com>
On 07/15/2013 01:10 PM, Mark Hatle wrote:
> Disable the python module check, as the host python modules are
> not needed for generating the target tests.
>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
> .../dbus/dbus-1.6.8/python-config.patch | 25 ++++++++++++++++++++++
> meta/recipes-core/dbus/dbus-ptest_1.6.10.bb | 1 +
You have a patch in the dbus-1.6.8 directory for a version 1.6.10, patch
not found!
Sau!
> 2 files changed, 26 insertions(+)
> create mode 100644 meta/recipes-core/dbus/dbus-1.6.8/python-config.patch
>
> diff --git a/meta/recipes-core/dbus/dbus-1.6.8/python-config.patch b/meta/recipes-core/dbus/dbus-1.6.8/python-config.patch
> new file mode 100644
> index 0000000..2944002
> --- /dev/null
> +++ b/meta/recipes-core/dbus/dbus-1.6.8/python-config.patch
> @@ -0,0 +1,25 @@
> +When building the dbus-ptest package, we have to enable python. However
> +checking if the host-system python has the necessary library isn't useful.
> +
> +Disable the python module check for cross compiling.
> +
> +Upstream-Status: Inappropriate [oe specific]
> +
> +Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> +
> +--- dbus-1.6.8/configure.ac.orig 2013-07-11 14:15:58.834554799 -0500
> ++++ dbus-1.6.8/configure.ac 2013-07-11 14:14:40.969554848 -0500
> +@@ -257,13 +257,6 @@
> + # full test coverage is required, Python is a hard dependency
> + AC_MSG_NOTICE([Full test coverage (--enable-tests=yes) requires Python, dbus-python, pygobject])
> + AM_PATH_PYTHON([2.6])
> +- AC_MSG_CHECKING([for Python modules for full test coverage])
> +- if "$PYTHON" -c "import dbus, gobject, dbus.mainloop.glib"; then
> +- AC_MSG_RESULT([yes])
> +- else
> +- AC_MSG_RESULT([no])
> +- AC_MSG_ERROR([cannot import dbus, gobject, dbus.mainloop.glib Python modules])
> +- fi
> + else
> + # --enable-tests not given: do not abort if Python is missing
> + AM_PATH_PYTHON([2.6], [], [:])
> diff --git a/meta/recipes-core/dbus/dbus-ptest_1.6.10.bb b/meta/recipes-core/dbus/dbus-ptest_1.6.10.bb
> index 6c0f404..a8e82ef 100644
> --- a/meta/recipes-core/dbus/dbus-ptest_1.6.10.bb
> +++ b/meta/recipes-core/dbus/dbus-ptest_1.6.10.bb
> @@ -14,6 +14,7 @@ SRC_URI = "http://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.gz \
> file://ptest.patch \
> file://dbus-1.init \
> file://run-ptest \
> + file://python-config.patch \
> "
>
> SRC_URI[md5sum] = "de4970c20629aeb958a12132415b3630"
>
next prev parent reply other threads:[~2013-07-15 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 20:10 [PATCH 0/4] A few misc patch Mark Hatle
2013-07-15 20:10 ` [PATCH 1/4] sanity.bbclass: Update gcc sanity check Mark Hatle
2013-07-15 20:10 ` [PATCH 2/4] terminal.bbclass: Fix BB_RUNFMT processing Mark Hatle
2013-07-15 20:10 ` [PATCH 3/4] busybox: fix ip reference in simple.script Mark Hatle
2013-07-15 20:10 ` [PATCH 4/4] dbus-ptest: Disable python module check Mark Hatle
2013-07-15 23:48 ` Saul Wold [this message]
2013-07-16 0:23 ` Mark Hatle
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=51E48A3B.6030607@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=mark.hatle@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox