From: Martin Jansa <martin.jansa@gmail.com>
To: Chen Qi <Qi.Chen@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 02/10] systemd: add libdw to RDEPENDS
Date: Thu, 14 Aug 2014 10:54:32 +0200 [thread overview]
Message-ID: <20140814085432.GG14848@jama> (raw)
In-Reply-To: <d77cfaf8b63e3dd1d7b05ff4b547b6a4a4fc6b47.1408005909.git.Qi.Chen@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
On Thu, Aug 14, 2014 at 04:46:01PM +0800, Chen Qi wrote:
> Add libdw to RDEPENDS of systemd to avoid build-deps QA warning.
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> meta/recipes-core/systemd/systemd_215.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/systemd/systemd_215.bb b/meta/recipes-core/systemd/systemd_215.bb
> index 770787b..a52a042 100644
> --- a/meta/recipes-core/systemd/systemd_215.bb
> +++ b/meta/recipes-core/systemd/systemd_215.bb
> @@ -244,7 +244,7 @@ FILES_${PN} = " ${base_bindir}/* \
> FILES_${PN}-dbg += "${rootlibdir}/.debug ${systemd_unitdir}/.debug ${systemd_unitdir}/*/.debug ${base_libdir}/security/.debug/"
> FILES_${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ ${sysconfdir}/rpm/macros.systemd"
>
> -RDEPENDS_${PN} += "kmod dbus util-linux-mount udev (= ${EXTENDPKGV})"
> +RDEPENDS_${PN} += "libdw kmod dbus util-linux-mount udev (= ${EXTENDPKGV})"
Shouldn't it be build-time dependency?
If it's detected from sysroot in do_configure then it has to be in
DEPENDS to get deterministic results.
> RDEPENDS_${PN} += "volatile-binds"
>
> RRECOMMENDS_${PN} += "systemd-serialgetty systemd-compat-units udev-hwdb\
> --
> 1.7.9.5
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-08-14 8:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 8:45 [PATCH 00/10] upgrade systemd to 215 and other misc fixes Chen Qi
2014-08-14 8:46 ` [PATCH 01/10] systemd: upgrade to 215 Chen Qi
2014-08-14 8:46 ` [PATCH 02/10] systemd: add libdw to RDEPENDS Chen Qi
2014-08-14 8:54 ` Martin Jansa [this message]
2014-08-14 9:39 ` Richard Purdie
2014-08-14 11:32 ` Martin Jansa
2014-08-15 3:00 ` ChenQi
2014-08-15 9:09 ` Martin Jansa
2014-08-14 8:46 ` [PATCH 03/10] systemd: make runlevel work in non-runlevel targets Chen Qi
2014-08-14 8:46 ` [PATCH 04/10] update-rc.d: fix logic in populate_packages_updatercd Chen Qi
2014-08-14 8:46 ` [PATCH 05/10] alsa-state: fix pkg_postinst and set INHIBIT_UPDATERCD_BBCLASS Chen Qi
2014-08-14 8:46 ` [PATCH 06/10] keymaps: fix for systemd Chen Qi
2014-08-14 8:46 ` [PATCH 07/10] systemd: add kbd-keymaps to RRECOMMENDS of systemd-vconsole-setup Chen Qi
2014-08-14 8:46 ` [PATCH 08/10] v86d: set INHIBIT_UPDATERCD_BBCLASS if 'sysvinit' not in DISTRO_FEATURES Chen Qi
2014-08-14 13:07 ` Otavio Salvador
2014-08-15 1:57 ` ChenQi
2014-08-14 8:46 ` [PATCH 09/10] systemd: add support for executing scripts under /etc/rcS.d Chen Qi
2014-08-14 8:46 ` [PATCH 10/10] dhcp: add dhcpd.service Chen Qi
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=20140814085432.GG14848@jama \
--to=martin.jansa@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox