All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 12/12] ndctl: v62 -> v63
Date: Tue, 27 Nov 2018 16:32:46 +0800	[thread overview]
Message-ID: <adbe1ab36459d98a9ef1a101cfbd94a7967f81ac.1543307294.git.hongxu.jia@windriver.com> (raw)
In-Reply-To: <cover.1543307294.git.hongxu.jia@windriver.com>

- Upstream introduce --with-systemd to replace --with-systemd-unit-dir
  [86ab28b ndctl, build: Introduce --with-{bash,systemd}]
  It fixed previously "No package 'systemd' found" failure

- Remove COMPATIBLE_HOST to build on more machines.

Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
---
 meta-oe/recipes-core/ndctl/{ndctl_git.bb => ndctl_v63.bb} | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)
 rename meta-oe/recipes-core/ndctl/{ndctl_git.bb => ndctl_v63.bb} (81%)

diff --git a/meta-oe/recipes-core/ndctl/ndctl_git.bb b/meta-oe/recipes-core/ndctl/ndctl_v63.bb
similarity index 81%
rename from meta-oe/recipes-core/ndctl/ndctl_git.bb
rename to meta-oe/recipes-core/ndctl/ndctl_v63.bb
index b20915f..17f3405 100644
--- a/meta-oe/recipes-core/ndctl/ndctl_git.bb
+++ b/meta-oe/recipes-core/ndctl/ndctl_v63.bb
@@ -10,21 +10,20 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=e66651809cac5da60c8b80e9e4e79e08"
 
 inherit autotools-brokensep pkgconfig module-base bash-completion systemd
 
-# v62
-SRCREV = "11f560f4048c1d38b7011a49566871a1e8a07c94"
+SRCREV = "cb2d678dd6d286dd96d31548c32449a8b883ae32"
 SRC_URI = "git://github.com/pmem/ndctl.git"
 
 DEPENDS = "virtual/kernel kmod udev json-c"
 
-PV = "v62+git${SRCPV}"
 S = "${WORKDIR}/git"
 
 EXTRA_OECONF += "--enable-test --enable-destructive --disable-docs"
 
+PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd','',d)}"
+PACKAGECONFIG[systemd] = "--with-systemd, --without-systemd, systemd"
+
 do_configure_prepend() {
     ${S}/autogen.sh
 }
 
 SYSTEMD_SERVICE_${PN} = "ndctl-monitor.service"
-
-COMPATIBLE_HOST='(x86_64).*'
-- 
2.7.4



      parent reply	other threads:[~2018-11-27  8:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  8:32 [PATCH 00/12] Upgrade 12 recipes Hongxu Jia
2018-11-27  8:32 ` [meta-gnome][PATCH 01/12] dconf: 0.28.0 -> 0.30.1 Hongxu Jia
2018-11-27  8:32 ` [meta-python][PATCH 02/12] python3-pykickstart: 3.15 -> 3.18 Hongxu Jia
2018-11-27  8:32 ` [meta-python][PATCH 03/12] python3-blivetgui: 2.1.8 -> 2.1.9 Hongxu Jia
2018-11-27  8:32 ` [meta-python][PATCH 04/12] python3-blivet: 3.0.1 -> 3.1.1 Hongxu Jia
2018-11-27  8:32 ` [meta-oe][PATCH 05/12] libreport: 2.9.5 -> 2.9.6 Hongxu Jia
2018-11-27  8:32 ` [meta-oe][PATCH 06/12] volume-key: 0.3.11 -> 0.3.12 Hongxu Jia
2018-11-27  8:32 ` [meta-oe][PATCH 07/12] efibootmgr: 0.16 -> 17 Hongxu Jia
2018-11-27  8:32 ` [meta-oe][PATCH 08/12] libbytesize: 1.3 -> 1.4 Hongxu Jia
2018-11-27  8:32 ` [meta-oe][PATCH 09/12] efivar: correct version number 0.36 -> 36 Hongxu Jia
2018-11-27  8:32 ` [meta-oe][PATCH 10/12] lvm2/libdevmapper: 2.02.180 -> 2.03.01 Hongxu Jia
2018-11-27  8:32 ` [meta-oe][PATCH 11/12] libblockdev: 2.18 -> 2.20 Hongxu Jia
2018-11-27  8:32 ` Hongxu Jia [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=adbe1ab36459d98a9ef1a101cfbd94a7967f81ac.1543307294.git.hongxu.jia@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.