Re: tor-0.2.1.22 renegotiating problem

[Victor Dorneanu <victor%dornea.nu@localhost>]

Magnus Eriksson wrote:
> Just for the record; that did not work for me.  Tor still goes to
> /usr/lib for its SSL needs, and I get the same "unexpected close"
> messages as you did with .22.
>
> On a hunch, I tried mucking about with SSLBASE, setting it to /usr/pkg
> instead of /usr, but that also didn't have any effect.
>
> I guess I'd have to figure out a way to reorder the paths given in the
> linking stage?  (-R/usr/lib comes first right now)
> ...

Ok.. Here's what I did:

-------------------------------------

$ cat distinfo 

$NetBSD$
SHA1 (tor-0.2.1.24.tar.gz) = 7b51c9e2f9ad5b70dea2fbe73728cd64213fc505

....

$ head config.log 

This file contains any messages produced by compilers while

running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was

generated by GNU Autoconf 2.61.  Invocation command line was

  $ ./configure --with-openssl-dir=/usr/pkg --sysconfdir=/usr/pkg/etc 
--localstatedir=/var --enable-eventdns --enable-threads --prefix=/usr/pkg 
--build=x86_64--netbsd --host=x86_64--netbsd --mandir=/usr/pkg/man

## --------- ##

## Platform. ##

(now I run configure again with the same arguments as previously mentioned)

$ ./configure ...

...

checking for openssl directory... /usr/pkg

checking whether we need extra options to link openssl... -Wl,-R/usr/pkg/lib

tor_cv_library_openssl_dir is /usr/pkg

...


-------------------------------------

There you go. tor will use "/usr/pkg/lib" and *NOT* "/usr/lib" to lookup
the openssl libraries. You could check the output - like I did - and see
against which libraries tor will be linked after compilation.

-- 
Victor Dorneanu

Contact
- Web/Blog: http://dornea.nu
 
GnuPG information
- KeyID = 0xD20870F4 (pgp.mit.edu)
- Key fingerprint = DD6B 5E09 242F 7410 3F90 492A 4CBA FD13 D208 70F4