Torsocks on FreeBSD

Adlesshaven adlesshaven at embarqmail.com
Tue Nov 25 08:00:26 UTC 2008


Sorry it took awhile to get back to you.
./configure works fine now, when I do make it gives me this list of errors:

# make
make  all-recursive
Making all in src
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H  -I. 
-I. -I..      -g -O2 -Wall -MT common.lo -MD -MP -MF ".deps/common.Tpo" 
-c -o common.lo common.c;  then mv -f ".deps/common.Tpo" 
".deps/common.Plo"; else rm -f ".deps/common.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -Wall -MT common.lo -MD -MP -MF 
.deps/common.Tpo -c common.c  -fPIC -DPIC -o .libs/common.o
In file included from common.c:43:
./common.h:55: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before 'get_uint16'
./common.h:57: error: expected declaration specifiers or '...' before 
'uint16_t'
./common.h:62: error: expected declaration specifiers or '...' before 
'uint16_t'
common.h:93: error: conflicting types for 'set_uint16'
./common.h:57: error: previos declaration of 'set_uint16' was here
*** Error code 1

Stop in /usr/build/torsocks-read-only/src.
*** Error code 1

Stop in /usr/build/torsocks-read-only.
*** Error code 1

Stop in /usr/build/torsocks-read-only.




Robert Hogan wrote:
> On Saturday 15 November 2008 20:34:45 you wrote:
>   
>> I'm trying to set up Torsocks on FreeBSD. The configure script fails
>> with the error "libdl is required".
>>
>>  From googling it looks like libdl is a part of glibc, but glibc isn't
>> listed in ports. The FreeBSD mailing list archives mention that libc
>> does an equivalent thing, but I don't know how to tell configure to use
>> it.
>>
>> Sorry for the newbie question, but how do I get Torsocks to work with
>> FreeBSD?
>>
>> Theres a Tsocks port so it shouldn't be too difficult...
>>     
>
> OK, I've fixed the libdl issue. Can you try:
>
> svn checkout http://torsocks.googlecode.com/svn/trunk/ torsocks-read-only
>
> and let me know how you get on?
>
> to build do:
>
> make -f Makefile.cvs
> ./configure
> make
>
>
>   



More information about the tor-talk mailing list