Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] czmq: needs MMU
Date: Mon, 5 May 2014 03:33:09 -0500	[thread overview]
Message-ID: <20140505033309.1dfc5aa8@core2quad.morethan.org> (raw)
In-Reply-To: <97ed4f06546e84c2b326a01447f77519460dfeff.1399262283.git.baruch@tkos.co.il>

On Mon,  5 May 2014 06:58:03 +0300
Baruch Siach <baruch@tkos.co.il> wrote:

>  config BR2_PACKAGE_CZMQ
>  	bool "czmq"
>  	select BR2_PACKAGE_ZEROMQ
> +	depends on BR2_USE_MMU # fork()

  ^ ^ ^ ^
>  	depends on BR2_INSTALL_LIBSTDCPP # zeromq
>  	depends on BR2_INET_IPV6 # zeromq
>  	depends on BR2_LARGEFILE # util-linux
>  	depends on BR2_USE_WCHAR # util-linux
>  	depends on BR2_TOOLCHAIN_HAS_THREADS # zeromq
> -	# uClibc toolchains provided by ADI don't have AI_ADDRCONFIG
> -	# support
> -	depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2
> && \
> -		!BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R1
>  	help
>  	  High-level C Binding for 0MQ
>  
>  	  http://czmq.zeromq.org/
>  
>  comment "czmq needs a toolchain w/ C++, IPv6, largefile, wchar,
> threads"
> -	depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2
> && \
> -		!BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R1
> +	depends on BR2_USE_MMU

  ^ ^ ^ ^
>  	depends on !(BR2_INSTALL_LIBSTDCPP && BR2_INET_IPV6 &&
> BR2_LARGEFILE \ && BR2_USE_WCHAR && BR2_TOOLCHAIN_HAS_THREADS)
>

Shouldn't the option and the comment have opposite conditions?
I.E: Either display the option or the comment?

Mike

  parent reply	other threads:[~2014-05-05  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05  3:58 [Buildroot] [PATCH] czmq: needs MMU Baruch Siach
2014-05-05  6:45 ` Peter Korsgaard
2014-05-05  8:33 ` Mike Zick [this message]
2014-05-05  8:41   ` Baruch Siach

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=20140505033309.1dfc5aa8@core2quad.morethan.org \
    --to=minimod@morethan.org \
    --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