Greetings Folks,

  Just wanted to ask out if there's anyone that is successful on
building proxychains on OpenBSD? I tried building it on my box (4.6
stable) with the following output:

$ gmake
gmake  all-recursive
gmake[1]: Entering directory `/home/pfunix/tor/proxychains-3.1'
Making all in proxychains
gmake[2]: Entering directory `/home/pfunix/tor/proxychains-3.1/proxychains'
Making all in docs
gmake[3]: Entering directory `/home/pfunix/tor/proxychains-3.1/proxychains/docs'
Making all in en
gmake[4]: Entering directory
`/home/pfunix/tor/proxychains-3.1/proxychains/docs/en'
gmake[4]: Nothing to be done for `all'.
gmake[4]: Leaving directory
`/home/pfunix/tor/proxychains-3.1/proxychains/docs/en'
gmake[4]: Entering directory `/home/pfunix/tor/proxychains-3.1/proxychains/docs'
gmake[4]: Nothing to be done for `all-am'.
gmake[4]: Leaving directory `/home/pfunix/tor/proxychains-3.1/proxychains/docs'
gmake[3]: Leaving directory `/home/pfunix/tor/proxychains-3.1/proxychains/docs'
gmake[3]: Entering directory `/home/pfunix/tor/proxychains-3.1/proxychains'
/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..
-g -O2 -c libproxychains.c
mkdir .libs
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2
-Wp,-MD,.deps/libproxychains.pp -c libproxychains.c  -fPIC -DPIC -o
.libs/libproxychains.o
libproxychains.c:295: error: conflicting types for `getnameinfo'
/usr/include/netdb.h:311: error: previous declaration of `getnameinfo'
gmake[3]: *** [libproxychains.lo] Error 1
gmake[3]: Leaving directory `/home/pfunix/tor/proxychains-3.1/proxychains'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/home/pfunix/tor/proxychains-3.1/proxychains'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/home/pfunix/tor/proxychains-3.1'
gmake: *** [all-recursive-am] Error 2


googling brings me to just this post.
http://kerneltrap.org/mailarchive/openbsd-misc/2009/9/25/6273573



anyhelp would be awesomely appreciated.
-b

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Reply via email to