From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] shadowsocks-libev: Adding the pthreads dependency
Date: Sun, 17 Jun 2018 15:43:41 +0200 [thread overview]
Message-ID: <20180617154341.29dba5b2@windsurf> (raw)
In-Reply-To: <20180611181823.2722-2-xuminready@gmail.com>
Hello,
On Mon, 11 Jun 2018 11:18:22 -0700, Min Xu wrote:
> Signed-off-by: Min Xu <xuminready@gmail.com>
Here again, the commit log was empty, which is not good. It should have
explained *why* you did this change.
> ---
> package/shadowsocks-libev/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/shadowsocks-libev/Config.in b/package/shadowsocks-libev/Config.in
> index d02e5a9..82c88e9 100644
> --- a/package/shadowsocks-libev/Config.in
> +++ b/package/shadowsocks-libev/Config.in
> @@ -1,5 +1,6 @@
> config BR2_PACKAGE_SHADOWSOCKS_LIBEV
> bool "shadowsocks-libev"
> + depends on BR2_TOOLCHAIN_HAS_THREADS # require pthreads
> depends on BR2_USE_MMU # fork()
> select BR2_PACKAGE_C_ARES
> select BR2_PACKAGE_LIBEV
When you add a dependency on a toolchain option, you need to add the
corresponding Config.in comment:
+comment "shadowsocks-libev needs a toolchain w/ threads"
+ depends on BR2_USE_MMU
+ depends on !BR2_TOOLCHAIN_HAS_THREADS
I've added that, extended the commit log and applied.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-17 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 18:18 [Buildroot] [PATCH v2 1/3] shadowsocks-libev: Drop the useless hash Min Xu
2018-06-11 18:18 ` [Buildroot] [PATCH v2 2/3] shadowsocks-libev: Adding the pthreads dependency Min Xu
2018-06-17 13:43 ` Thomas Petazzoni [this message]
2018-06-18 7:13 ` xu min
2018-06-11 18:18 ` [Buildroot] [PATCH v2 3/3] shadowsocks-libev: Adding the __sync related dependency Min Xu
2018-06-17 13:35 ` [Buildroot] [PATCH v2 1/3] shadowsocks-libev: Drop the useless hash 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=20180617154341.29dba5b2@windsurf \
--to=thomas.petazzoni@bootlin.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