Opened 9 years ago

Last modified 5 weeks ago

#1354 assigned defect (None)

Configuring Tor with --with*dir gives wrong directories

Reported by: Sebastian Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version: 0.2.1.25
Severity: Normal Keywords: tor-client build packages autoconf
Cc: Sebastian, nickm Actual Points:
Parent ID: #6311 Points:
Reviewer: Sponsor:

Description (last modified by nickm)

I'm trying to configure Tor like this:

./configure --enable-gcc-warnings --with-openssl-dir=/opt/local
--with-zlib-dir=/usr --with-libevent-dir=/usr/local

What happens is that the zlib.h that gets included is from
/opt/local/include, instead of the one in /usr/include.

During configure, I get this as output, though:

checking for zlib directory... /usr/include
checking whether we need extra options to link zlib... (none)

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (22)

comment:1 Changed 9 years ago by nickm

Owner: set to nickm
Status: newassigned

comment:2 Changed 9 years ago by nickm

Description: modified (diff)
Milestone: Tor: 0.2.3.x-final

comment:3 Changed 7 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: 0.2.4.x-final

Fixing our dependency code to be smarter would rock, but it is so not going to happen for 0.2.3.x

comment:4 Changed 7 years ago by nickm

FWIW, my current favored approach here would be to cut the gordian knot and use pkg-config and deprecate our current TOR_SEARCH_LIBRARY nonsense. See bug #6311

comment:5 Changed 7 years ago by nickm

Keywords: tor-client added

comment:6 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:7 Changed 7 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

Ugh. The right solution to this requires #6311, which is not happening for 0.2.4.

comment:8 Changed 6 years ago by nickm

Cc: Sebastian,nickmSebastian, nickm

Closed #9230 as closely related.

comment:9 Changed 5 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:10 Changed 5 years ago by teor

#13817 logs a similar issue for OpenSSL/LibreSSL

comment:11 Changed 5 years ago by teor

Parent ID: #6311

Assigning #6311 as the parent of tasks that could be resolved by pkg-config

comment:12 Changed 4 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.7.x-final

Tentatively move some tickets to 0.2.7

comment:13 Changed 4 years ago by nickm

Keywords: 027-triaged-1-out added

Marking triaged-out items from first round of 0.2.7 triage.

comment:14 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.???

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

comment:15 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:16 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:17 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:18 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:19 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:20 Changed 2 years ago by nickm

Keywords: 027-triaged-1-out removed

comment:21 Changed 2 years ago by nickm

Keywords: build packages autoconf added
Priority: LowHigh
Severity: Normal

comment:22 Changed 5 weeks ago by nickm

Owner: nickm deleted

I am not actually working on these tickets, so they shouldn't be assigned to me.

Note: See TracTickets for help on using tickets.