Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/4] package/lttng-libust: use BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS dependency
Date: Sun, 13 Dec 2015 19:47:49 +0100	[thread overview]
Message-ID: <1450032471-3405-2-git-send-email-s.martin49@gmail.com> (raw)
In-Reply-To: <1450032471-3405-1-git-send-email-s.martin49@gmail.com>

Using this newly introduced symbol lets to simplify the dependency code.

This change also adds the missing architecture dependencies on the second
comment.

Signed-off-by: Samuel Martin <s.martin49@gmail.com>

---
changes v1->v2:
- new patch
---
 package/lttng-libust/Config.in | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/package/lttng-libust/Config.in b/package/lttng-libust/Config.in
index 3c26055..26838bb 100644
--- a/package/lttng-libust/Config.in
+++ b/package/lttng-libust/Config.in
@@ -5,7 +5,7 @@ config BR2_PACKAGE_LTTNG_LIBUST
 	select BR2_PACKAGE_UTIL_LINUX_LIBUUID
 	depends on BR2_USE_WCHAR # util-linux
 	# liburcu only works on some architectures and requires threads support"
-	depends on BR2_arm || BR2_armeb || BR2_aarch64 || BR2_i386 || BR2_powerpc || BR2_x86_64
+	depends on BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS
 	depends on !BR2_TOOLCHAIN_HAS_GCC_BUG_58854 # liburcu/gcc-4.8.x bug
 	depends on BR2_TOOLCHAIN_HAS_THREADS
 	depends on !BR2_STATIC_LIBS
@@ -18,9 +18,10 @@ config BR2_PACKAGE_LTTNG_LIBUST
 	  http://lttng.org
 
 comment "lttng-libust needs a toolchain w/ dynamic library, wchar, threads"
-	depends on BR2_arm || BR2_armeb || BR2_aarch64 || BR2_i386 || BR2_powerpc || BR2_x86_64
+	depends on BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS
 	depends on BR2_STATIC_LIBS || !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
 	depends on !BR2_TOOLCHAIN_HAS_GCC_BUG_58854 # liburcu/gcc-4.8.x bug
 
 comment "lttng-libust needs a toolchain not affected by GCC bug 58854"
+	depends on BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS
 	depends on BR2_TOOLCHAIN_HAS_GCC_BUG_58854
-- 
2.6.4

  reply	other threads:[~2015-12-13 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 18:47 [Buildroot] [PATCH v2 1/4] package/liburcu: introduce BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS symbol Samuel Martin
2015-12-13 18:47 ` Samuel Martin [this message]
2015-12-13 20:09   ` [Buildroot] [PATCH v2 2/4] package/lttng-libust: use BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS dependency Yann E. MORIN
2015-12-13 18:47 ` [Buildroot] [PATCH v2 3/4] package/lttng-tools: " Samuel Martin
2015-12-13 20:15   ` Yann E. MORIN
2015-12-13 18:47 ` [Buildroot] [PATCH v2 4/4] package/netsniff: fix missing depend on statements Samuel Martin
2015-12-13 20:16   ` Yann E. MORIN
2015-12-13 20:05 ` [Buildroot] [PATCH v2 1/4] package/liburcu: introduce BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS symbol Yann E. MORIN
2015-12-13 21:37 ` Thomas Petazzoni

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=1450032471-3405-2-git-send-email-s.martin49@gmail.com \
    --to=s.martin49@gmail.com \
    --cc=buildroot@busybox.net \
    /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