[Tor-BSD] Having issues forcing Tor release 0.2.6.9 to build with update libssl.so.32.0 library

Seth list at sysfu.com
Mon Jun 29 18:19:30 EDT 2015


On Mon, 15 Jun 2015 01:51:30 -0700, teor <teor2345 at gmail.com> wrote:
> Can you please provide any configure or make output containing ssl or  
> crypto?
> What is the entire output in config.log for openssl configuration?

Sorry for the delay, your email response got buried.

Please see attached files for complete log and one with only ssl and  
crypto strings.

> I am aware of issues in previous releases (0.2.5?) on OS X where tor  
> would ./configure openssl based on the location of the first openssl  
> binary in the $PATH, and not the location of the libraries or the SSL  
> directory. I thought these had been fixed, but we might have a  
> regression.
>
> Is there an openssl binary in /usr/bin?

$ ls -l /usr/bin/open*
lrwxr-xr-x  1 root  wheel      22 Jun 15 11:49 /usr/bin/openssl ->  
/usr/local/bin/openssl
-r-xr-xr-x  1 root  bin    498904 Mar  9 03:52 /usr/bin/openssl2.1

> In /usr/local/bin?

$ ls -l /usr/local/bin/open*
-rwxr-xr-x  1 root  wheel  1461810 Jun 15 11:47 /usr/local/bin/openssl

> What is your $PATH when ./configure is called?

/home/<username>/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games:.

> What is the $PATH used in the openssl configure step? (This may require  
> grepping logs or modifying ./configure)

Not sure I understand. Do you when ./configure was run to build LibreSLL  
2.2.0? If so, it would be the same as above.

> There may also be an issue with the linker command generated by  
> ./configure:
>
> What is $LDFLAGS when ./configure is called?

Same as the ./configure command I posted in  beginning of thread:  
LDFLAGS=-L/usr/local/lib

> What is $CC when ./configure is called?

$ sudo echo $CC

(No value set)

> Can you please provide the exact command-line used for linking tor,  
> particularly any -L or -l directives? (This may require grepping logs or  
> modifying a Makefile)

Not sure I understand the question, as I didn't do any manual linking.  
Only introduced CFLAGS and LDFLAGS when running ./configure

> And a quick sanity check:
>
> Does tor link entirely to /usr/lib when ./configure  
> --with-openssl-dir=/usr is used?

Yes.

$ ldd /usr/local/bin/tor
/usr/local/bin/tor:
         Start            End              Type Open Ref GrpRef Name
         00000c1110200000 00000c11107c3000 exe  1    0   0       
/usr/local/bin/tor
         00000c138730b000 00000c1387720000 rlib 0    1   0       
/usr/lib/libz.so.5.0
         00000c13a42bf000 00000c13a46e7000 rlib 0    1   0       
/usr/lib/libm.so.9.0
         00000c139fbb1000 00000c139ffbd000 rlib 0    1   0       
/usr/lib/libevent.so.4.1
         00000c13c83cc000 00000c13c882b000 rlib 0    1   0       
/usr/lib/libssl.so.32.0
         00000c131e761000 00000c131ed36000 rlib 0    1   0       
/usr/lib/libcrypto.so.32.0
         00000c13a8db0000 00000c13a91c2000 rlib 0    2   0       
/usr/lib/libpthread.so.18.1
         00000c137dbb8000 00000c137e0a4000 rlib 0    1   0       
/usr/lib/libc.so.78.1
         00000c137f900000 00000c137f900000 rtld 0    1   0       
/usr/libexec/ld.so

> What about ./configure without an --with-openssl-dir argument?

$ sudo ./configure --disable-asciidoc --disable-gcc-hardening  
--sysconfdir=/etc; sudo make check; sudo make install

$ ldd /usr/local/bin/tor
/usr/local/bin/tor:
         Start            End              Type Open Ref GrpRef Name
         0000158897500000 0000158897ac3000 exe  1    0   0       
/usr/local/bin/tor
         0000158ad2d31000 0000158ad3146000 rlib 0    1   0       
/usr/lib/libz.so.5.0
         0000158aa4f01000 0000158aa5329000 rlib 0    1   0       
/usr/lib/libm.so.9.0
         0000158ab7aeb000 0000158ab7ef7000 rlib 0    1   0       
/usr/lib/libevent.so.4.1
         0000158aaf91f000 0000158aafd7e000 rlib 0    1   0       
/usr/lib/libssl.so.32.0
         0000158ab910e000 0000158ab96e3000 rlib 0    1   0       
/usr/lib/libcrypto.so.32.0
         0000158ac1459000 0000158ac186b000 rlib 0    2   0       
/usr/lib/libpthread.so.18.1
         0000158b5cdee000 0000158b5d2da000 rlib 0    1   0       
/usr/lib/libc.so.78.1
         0000158b64600000 0000158b64600000 rtld 0    1   0       
/usr/libexec/ld.so
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tor-2.6.9-openbsd-5.7-libressl-2.2.0-config.log
Type: application/octet-stream
Size: 442140 bytes
Desc: not available
URL: <http://lists.nycbug.org/pipermail/tor-bsd/attachments/20150629/7513ef6c/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tor-2.6.9-openbsd-5.7-libressl-2.2.0-config-ssl-crypto-only.log
Type: application/octet-stream
Size: 3073 bytes
Desc: not available
URL: <http://lists.nycbug.org/pipermail/tor-bsd/attachments/20150629/7513ef6c/attachment-0003.obj>


More information about the Tor-BSD mailing list