[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #5009 [Obfsproxy]: obfsproxy does not build from instructions on debian squeeze

#5009: obfsproxy does not build from instructions on debian squeeze
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:  asn
     Type:  defect     |         Status:  new
 Priority:  normal     |      Milestone:     
Component:  Obfsproxy  |        Version:     
 Keywords:             |         Parent:     
   Points:             |   Actualpoints:     
-----------------------+----------------------------------------------------
Changes (by asn):

 * cc: nickm (added)


Comment:

 I think that if you build and install libevent2, obfsproxy will find the
 locally installed header files and libraries in /usr/local/ automatically.
 That's what happens in a Debian system of mine.

 {{{
 $ wget
 https://github.com/downloads/libevent/libevent/libevent-2.0.16-stable.tar.gz
 $ tar xvf libevent-2.0.16-stable.tar.gz
 $ cd libevent-2.0.16-stable
 $ ./configure && make
 # make install

 $ cd ~
 $ git clone git://git.torproject.org/obfsproxy.git
 $ cd obfsproxy/
 $ ./autogen.sh && ./configure && make
 }}}

 If that doesn't work, doing:
 {{{
 $ export libevent_CFLAGS="/usr/local/include"
 $ export libevent_LIBS="/usr/local/lib"
 }}}
 could help.

 obfsproxy doesn't have a --with-libevent-dir switch in its configure
 script, and I think it's intentional, because the correct way of doing
 this is by using `pkg-config`. I'm not sure what `pkg-config` is exactly
 -- I think it's a package with some rules for each library that tells you
 where to find its objects and headers -- but that's what I remember Nick
 saying in IRC.
 That said, we should add `pkg-config` to the to-apt-get-install-list.

 BTW, I've heard reports of people having problems with `ntohl` during
 `configure`, and I remember seeing something similar in an Ubuntu system
 some months ago. I believe it's caused by the script in `m4/winsocks.m4`,
 which was added by Zack, because ''ntohl and a bunch of related functions
 require a special library on Windows.''. Could this also cause problems in
 Linux? Unfortunately, I don't know autotools, and I won't be able to play
 with this for the next some days. Nick, any ideas?

 Roger, can you try the above instructions in your setup, and see if it
 works? During the week, I'll try to correct them and make a website
 version out of them.

 (CCing nickm in case he knows anything about the autotools stuff.)

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5009#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs