From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new package: proxychains
Date: Tue, 8 Jan 2013 20:18:08 +0100 [thread overview]
Message-ID: <20130108201808.7ee86751@skate> (raw)
In-Reply-To: <50EC6C03.2040504@petroprogram.com>
Dear Stefan Fr?berg,
On Tue, 08 Jan 2013 20:57:07 +0200, Stefan Fr?berg wrote:
> Hmmm... could this be a some weird parallel compiling problem ????
No. proxychains is a program that LD_PRELOAD a library to overload some
of the C library functions. So it reimplements some functions of the C
library, but in this case, it reimplements getnameinfo() with a
prototype that doesn't match the one of the C library.
Maybe an idea would be to upgrade to proxychains 4.4:
http://sourceforge.net/projects/proxychains/forums/forum/644747/topic/6519406.
The main page of proxychains mentions 3.1 as the latest version, but it
is not the case. The official Git repo at
https://github.com/rofl0r/proxychains contains many more recent
versions. Most likely the problem is already fixed in a more recent
version than 3.1.
Could you test a more recent version and submit the corresponding patch?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-08 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 0:20 [Buildroot] [PATCH] new package: proxychains Stefan Fröberg
2012-12-23 21:17 ` Peter Korsgaard
2013-01-08 17:09 ` Thomas Petazzoni
2013-01-08 18:17 ` Stefan Fröberg
2013-01-08 18:47 ` Stefan Fröberg
2013-01-08 18:57 ` Stefan Fröberg
2013-01-08 19:18 ` Thomas Petazzoni [this message]
2013-01-08 19:31 ` Stefan Fröberg
2013-01-08 21:10 ` Stefan Fröberg
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=20130108201808.7ee86751@skate \
--to=thomas.petazzoni@free-electrons.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