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

[teor]

> On 1 Jul 2015, at 04:23 , Seth <list at sysfu.com> wrote:
> 
>> If you can run a verbose build that shows the linker command used to link the tor binary, that would be helpful.
>> 
>> Can you try:
>> CC="/usr/bin/gcc -v" ./configure --with-openssl-dir=/usr/local/lib
>> 
>> If this works, can you please provide the output of make, after the line:
>>  CCLD     src/or/tor
>> 
>> This will help me see what arguments are actually being passed to the linker.
> 
> Did not work, but capture make output after requested line attached anyhow.

OK, thanks for working through these steps.

All my suggestions failed, so there's apparently a bug in the linker command-line created by the latest Tor ./configure script, potentially related to multiple LibreSSL installs on OpenBSD.

We couldn't fix it by changing the $PATH, so it may not be related to the openssl binary at all.

But hang on, I've been assuming you're using bash. The default shell on OpenBSD is (pd)ksh, so this may affect the syntax for setting and exporting environmental variables.

Whether you're using bash or not, can you please retry the following steps with explicit environmental variable assignments on the ./configure command-line. (This might also have affected whether your previous LDFLAGS setting was used by ./configure, but LDFLAGS shouldn't be needed.)

> 2. Using --with-openssl-dir=/usr/local with /usr/local/bin first in the path
> ./configure --with-openssl-dir=/usr/local PATH=/usr/local/bin:$PATH …

> 4. Using --with-openssl-dir=/usr/local with the latest version of tor and /usr/local/bin first in the path
> ./configure --with-openssl-dir=/usr/local PATH=/usr/local/bin:$PATH …

> If you can run a verbose build that shows the linker command used to link the tor binary, that would be helpful.
> 
> Can you try:
> ./configure --with-openssl-dir=/usr/local/lib CC="/usr/bin/gcc -v" …
> 
> If this works, can you please provide the output of make, after the line:
>  CCLD     src/or/tor
> 
> This will help me see what arguments are actually being passed to the linker.


I really need to see the exact linker command-line to diagnose this issue. (Or, more likely, to log the issue and refer it to our OpenSSL/LibreSSL experts via the Tor Trac system.)

Can you please send me the results of a verbose build (more precisely, a verbose link) with your system compiler/linker?

Tim

Tim Wilson-Brown (teor)

teor2345 at gmail dot com
pgp 0xABFED1AC
https://gist.github.com/teor2345/d033b8ce0a99adbc89c5

teor at blah dot im
OTR D5BE4EC2 255D7585 F3874930 DB130265 7C9EBBC7

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.nycbug.org/pipermail/tor-bsd/attachments/20150701/2ac7d5ff/attachment.bin>