Hi, As you might know/remember, I'm using tor on my Linksys WRT54G(S) router running OpenWRT. I packaged tor 0.0.9.1 for openwrt before (and I will for 0.0.9.2 too), but I also took a CVS checkout since alledgedly it uses less resources. That's nothing exciting, but to crosscompile for a different architecture I have to hack around a couple of annoyances in the whole autoconf thing. Attached you'll find the patch I'm using to get tor to build for my architecture. I introduced a configuration parameter (--disable-ssl-check) which skips the actual checking of the ssl include/library paths. Note that if you use it, you'll have to make really sure OpenSSL's development stuff is installed on your system (or in --with-ssl-dir) :-) This makes my life easier for crosscompiling, maybe it's of use to someone else too. Thanks.
--- tor-cvs.orig/configure.in 2005-01-09 23:26:15.000000000 +0000
+++ tor-cvs/configure.in 2005-01-09 23:25:17.000000000 +0000
@@ -74,7 +74,11 @@
# Basic test to check for compatible version and correct linking
# *does not* test for RSA - that comes later.
- AC_TRY_RUN(
+
+AC_ARG_ENABLE(ssl-check,
+ [ --disable-ssl-check do not test for openssl, assume --with-ssl-dir is sane],
+ [found_crypto=1],
+ [ AC_TRY_RUN(
[
#include <string.h>
#include <openssl/rand.h>
@@ -89,8 +93,8 @@
[
found_crypto=1
break;
- ], []
- )
+ ], [])
+])
if test ! -z "$found_crypto" ; then
break;
@@ -203,7 +207,7 @@
return memcmp(&p1,&p2,sizeof(char*))?1:0; }]])],
[tor_cv_null_is_zero=yes],
[tor_cv_null_is_zero=no],
- [tor_cv_null_is_zero=cross])])
+ [tor_cv_null_is_zero=yes])])
if test $tor_cv_null_is_zero = yes; then
AC_DEFINE([NULL_REP_IS_ZERO_BYTES], 1,
Attachment:
signature.asc
Description: This is a digitally signed message part