Opened 6 weeks ago

Last modified 5 weeks ago

#33437 needs_information defect

Unsuccessful compilation of tor on FreeBSD system with libssl.so.11

Reported by: stillicide Owned by:
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version: 0.4.2.6
Severity: Normal Keywords: FreeBSD, openssl, 043-backport 042-backport
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

+Sebastian | so, this looks like a configure error in detecting available openssl correctly. Please file a bug


I'm running into a compilation error related to openssl while compiling tor-0.4.2.6 on FreeBSD 11.3 (amd64). Log files are attached.

Notes:

  • compilation of 0.4.2.6 with libssl.so.9 was successful
  • compilation of 0.4.2.6 with libssl.so.11 was unsuccessful

Child Tickets

Attachments (5)

make.log (11.1 KB) - added by stillicide 6 weeks ago.
stdout of GNU make
config.log (1.5 MB) - added by stillicide 6 weeks ago.
config.log produced prior to compilaton
make_v_1_unsuccessful.txt (306.1 KB) - added by stillicide 5 weeks ago.
the stdout of "make V=1" on the machine which is unable to build successfully (the same machine which produced config.log and make.log)
config_successful.log (1.5 MB) - added by stillicide 5 weeks ago.
the config.log from the machine which is able to build successfully
make_v_1_successfull.txt (1.6 MB) - added by stillicide 5 weeks ago.
the stdout of "make V=1" on the machine which is able to build successfully

Change History (10)

Changed 6 weeks ago by stillicide

Attachment: make.log added

stdout of GNU make

Changed 6 weeks ago by stillicide

Attachment: config.log added

config.log produced prior to compilaton

comment:1 Changed 6 weeks ago by nickm

Component: Core TorCore Tor/Tor
Keywords: 043-backport 042-backport added
Milestone: Tor: 0.4.4.x-final

comment:2 Changed 6 weeks ago by stillicide

Note: This is not a duplicate of #27901, running autoreconf (2.69) prior to build did not resolve the issue.

comment:3 Changed 5 weeks ago by nickm

Hi! To help debug this, some more info could be helpful.

First off, can we get the result of running "make V=1" so that we see the exact command line that is failing?

Second, can we get the results of "make V=1" and the config.log from the case that _succeeds_, so we can see a bit more about what is different between the two cases?

Thanks!

comment:4 Changed 5 weeks ago by nickm

Status: newneeds_information

Changed 5 weeks ago by stillicide

Attachment: make_v_1_unsuccessful.txt added

the stdout of "make V=1" on the machine which is unable to build successfully (the same machine which produced config.log and make.log)

Changed 5 weeks ago by stillicide

Attachment: config_successful.log added

the config.log from the machine which is able to build successfully

Changed 5 weeks ago by stillicide

Attachment: make_v_1_successfull.txt added

the stdout of "make V=1" on the machine which is able to build successfully

comment:5 in reply to:  3 Changed 5 weeks ago by stillicide

Replying to nickm:

First off, can we get the result of running "make V=1" so that we see the exact command line that is failing?

Second, can we get the results of "make V=1" and the config.log from the case that _succeeds_, so we can see a bit more about what is different between the two cases?

Hi Nick, I've attached the requested log files. Thanks for your help!

make_v_1_unsuccessful.txt​ (306.1 KB) - added by stillicide 12 minutes ago.
    the stdout of "make V=1" on the machine which is unable to build successfully (the same machine which produced config.log and make.log) 
config_successful.log​ (1.5 MB) - added by stillicide 8 minutes ago.
    the config.log from the machine which is able to build successfully 
make_v_1_successfull.txt​ (1.6 MB) - added by stillicide 0 seconds ago.
    the stdout of "make V=1" on the machine which is able to build successfully 

I can provide access to the machine as well if it would help the debugging process. I'm dove on IRC.

Last edited 5 weeks ago by stillicide (previous) (diff)
Note: See TracTickets for help on using tickets.