From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/4] package/liburcu: introduce BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS symbol
Date: Sun, 13 Dec 2015 21:05:57 +0100 [thread overview]
Message-ID: <20151213200557.GA27971@free.fr> (raw)
In-Reply-To: <1450032471-3405-1-git-send-email-s.martin49@gmail.com>
Samuel, All,
On 2015-12-13 19:47 +0100, Samuel Martin spake thusly:
> This new hidden symbol will allow simplifying the architecture dependencies
> on package that depends on liburcu. These packages will be updated in follow-up
> patches.
>
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Regards,
Yann E. MORIN.
> ---
> changes v1->v2:
> - new patch
> ---
> package/liburcu/Config.in | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/package/liburcu/Config.in b/package/liburcu/Config.in
> index a4e8dc8..36d5353 100644
> --- a/package/liburcu/Config.in
> +++ b/package/liburcu/Config.in
> @@ -1,6 +1,11 @@
> +config BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS
> + bool
> + depends on BR2_arm || BR2_armeb || BR2_aarch64 || BR2_i386 || BR2_powerpc || BR2_x86_64
> + default y
> +
> config BR2_PACKAGE_LIBURCU
> bool "liburcu"
> - 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
> help
> @@ -18,7 +23,7 @@ config BR2_PACKAGE_LIBURCU
> http://lttng.org/urcu
>
> comment "liburcu needs a toolchain w/ 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_TOOLCHAIN_HAS_GCC_BUG_58854 # liburcu/gcc-4.8.x bug
> depends on !BR2_TOOLCHAIN_HAS_THREADS
>
> --
> 2.6.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-12-13 20:05 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 ` [Buildroot] [PATCH v2 2/4] package/lttng-libust: use BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS dependency Samuel Martin
2015-12-13 20:09 ` 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 ` Yann E. MORIN [this message]
2015-12-13 21:37 ` [Buildroot] [PATCH v2 1/4] package/liburcu: introduce BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS symbol 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=20151213200557.GA27971@free.fr \
--to=yann.morin.1998@free.fr \
--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