From: Min Xu <xuminready@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] shadowsocks-libev: Adding the __sync related dependency
Date: Mon, 11 Jun 2018 11:18:23 -0700 [thread overview]
Message-ID: <20180611181823.2722-3-xuminready@gmail.com> (raw)
In-Reply-To: <20180611181823.2722-1-xuminready@gmail.com>
To fixup libcork linking errors:
"undefined reference to `__sync_val_compare_and_swap_4'"
Fixes
http://autobuild.buildroot.net/results/552b09ffe951c429422529c895f4c3ec723cf5ab
http://autobuild.buildroot.net/results/4810526381e15a194767753d324875bfbf5e3dde
http://autobuild.buildroot.net/results/9cb76805c2f2952aa434d143831ee03c7d43aa52
http://autobuild.buildroot.net/results/d00c5f9e1e7a6a40fac5763a06977b351b7875da
http://autobuild.buildroot.net/results/0612f2dc09a8763fdf2111ee8d0c223c8531262a
Signed-off-by: Min Xu <xuminready@gmail.com>
---
package/shadowsocks-libev/Config.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/shadowsocks-libev/Config.in b/package/shadowsocks-libev/Config.in
index 82c88e9..972e329 100644
--- a/package/shadowsocks-libev/Config.in
+++ b/package/shadowsocks-libev/Config.in
@@ -1,5 +1,7 @@
config BR2_PACKAGE_SHADOWSOCKS_LIBEV
bool "shadowsocks-libev"
+ depends on BR2_TOOLCHAIN_HAS_SYNC_4 # for libcork
+ depends on BR2_TOOLCHAIN_HAS_SYNC_8 || !BR2_ARCH_IS_64 # for libcork
depends on BR2_TOOLCHAIN_HAS_THREADS # require pthreads
depends on BR2_USE_MMU # fork()
select BR2_PACKAGE_C_ARES
--
2.11.0
next prev parent reply other threads:[~2018-06-11 18:18 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
2018-06-18 7:13 ` xu min
2018-06-11 18:18 ` Min Xu [this message]
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=20180611181823.2722-3-xuminready@gmail.com \
--to=xuminready@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