All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Lin <axel.lin@ingics.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] proxychains-ng: needs dynamic library support
Date: Sat, 05 Oct 2013 12:30:59 +0800	[thread overview]
Message-ID: <1380947459.27085.0.camel@phoenix> (raw)

Fix below build error if BR2_PREFER_STATIC_LIB is set:

src/libproxychains.c:34:19: fatal error: dlfcn.h: No such file or directory
compilation terminated.
make[1]: *** [src/libproxychains.o] Error 1

In additional, the README file also mentions that this program works only on
dynamically linked programs.

Signed-off-by: Axel Lin <axel.lin@ingics.com>
---
 package/proxychains-ng/Config.in | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/package/proxychains-ng/Config.in b/package/proxychains-ng/Config.in
index 99e49bd..97eaa0c 100644
--- a/package/proxychains-ng/Config.in
+++ b/package/proxychains-ng/Config.in
@@ -1,10 +1,11 @@
 config BR2_PACKAGE_PROXYCHAINS_NG
 	bool "proxychains-ng"
 	depends on BR2_TOOLCHAIN_HAS_THREADS
+	depends on !BR2_PREFER_STATIC_LIB
 	help
 	  Force any tcp connections to flow through a proxy (or proxy chain)
 
 	  https://github.com/rofl0r/proxychains
 
-comment "proxychains-ng needs a toolchain with thread support"
-	depends on !BR2_TOOLCHAIN_HAS_THREADS
+comment "proxychains-ng needs a toolchain with thread and dynamic library support"
+	depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_PREFER_STATIC_LIB
-- 
1.8.1.2

             reply	other threads:[~2013-10-05  4:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05  4:30 Axel Lin [this message]
2013-10-05  4:31 ` [Buildroot] [PATCH 2/2] proxychains-ng: bump to version 4.6 Axel Lin
2013-10-05 19:11 ` [Buildroot] [PATCH 1/2] proxychains-ng: needs dynamic library support Peter Korsgaard

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=1380947459.27085.0.camel@phoenix \
    --to=axel.lin@ingics.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.