Opened 14 months ago

Last modified 5 months ago

#31565 needs_information defect

static Tor building against openssl-1.1.1 fails: configure unable to find linkable OpenSSL

Reported by: shredder Owned by:
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor, openssl, 1.1.1, static, mingw 043-should backport
Cc: boklm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Trying to cross build static Tor on Linux with mingw (to use on Windows-x86). It seems configure cannot find OpenSSL if its version is not 1.0.2. Tried openssl-1.1.0 and openssl-1.1.1, and also different Tor versions from 0.3.5.XX to 0.4.0.5 and 0.4.1.5. Building against openssl-1.0.2 works.

Child Tickets

Attachments (1)

buildenv.txt (991 bytes) - added by shredder 14 months ago.
building environment exports

Download all attachments as: .zip

Change History (11)

Changed 14 months ago by shredder

Attachment: buildenv.txt added

building environment exports

comment:1 Changed 14 months ago by dgoulet

Milestone: Tor: unspecified
Version: Tor: unspecified

comment:2 Changed 9 months ago by arma

Cc: boklm added

I'm told by somebody on irc today that openssl 1.0.2 is now unsupported. So the folks trying to maintain "static Tor binary on Windows" build scripts, such as
https://gitlab.com/euphrosyne/tor-mingw/blob/master/guide
are now out of options.

I wonder how rbm solves this one; I'm cc'ing boklm to find out. Maybe it's simply by not making it that static.

comment:3 Changed 9 months ago by nickm

It might help enormously to have the config.log outputs from running the configure script in both cases: once with 1.0.2 and once with 1.1.1.

comment:4 Changed 9 months ago by nickm

Keywords: 043-should backport added
Milestone: Tor: unspecifiedTor: 0.4.3.x-final

comment:5 in reply to:  2 Changed 9 months ago by boklm

Replying to arma:

I wonder how rbm solves this one; I'm cc'ing boklm to find out. Maybe it's simply by not making it that static.

Yes, in Tor Browser, tor is dynamically linked to openssl, so we don't have this issue.

comment:6 Changed 9 months ago by nickm

It would help here to have the contents of config.log after successfully finding openssl-1.0.2 for a static build, and the contents of config.log after failing to find openssl-1.1.1 for a static build.

(Please compress before uploading)

comment:7 Changed 9 months ago by nickm

Status: newneeds_information

comment:9 Changed 7 months ago by nickm

There's a work-in-progress patch for this issue at #33624

comment:10 Changed 5 months ago by nickm

Milestone: Tor: 0.4.3.x-finalTor: 0.4.4.x-final

0.4.3 was released: Move non merge-ready 0.4.3 tickets to 044.

Note: See TracTickets for help on using tickets.