Bug 73397 - dns/bind9 is broken with no openssl in base
Summary: dns/bind9 is broken with no openssl in base
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Doug Barton
Depends on:
Reported: 2004-11-02 00:20 UTC by Oliver Lehmann
Modified: 2005-03-13 23:13 UTC (History)
1 user (show)

See Also:

patch-dns::bind9::Makefile (550 bytes, text/plain)
2004-11-02 00:20 UTC, Oliver Lehmann
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Lehmann freebsd_committer 2004-11-02 00:20:22 UTC
	dns/bind9 fails to build when no openssl is installed from ports,
	and there is no openssl in the base system.

Fix: apply that patch
How-To-Repeat: 	make -DWITHOUT_OPENSSL installworld
	remove old openssl binaries+libs
	install security/openssl
	try to install dns/bind9
Comment 1 Oliver Lehmann freebsd_committer 2004-11-02 00:23:46 UTC
Responsible Changed
From-To: freebsd-ports-bugs->dougb

reassign to dougb
Comment 2 Doug Barton freebsd_committer 2005-03-13 11:26:53 UTC
State Changed
From-To: open->feedback

I'm confused about your proposed solution ... if there is 
no openssl at all (which is what I understand your test 
case to be), then OPENSSLBASE will be set to what? 

Not having any openssl at all would significantly change 
the port, as several things wouldn't get built or installed, 
and the parts that are installed would have limited 
functionality. I have not had any users complain about this 
issue, so before proceeding I need to know what problem 
you are trying to solve.  


Comment 3 Oliver Lehmann freebsd_committer 2005-03-13 12:26:43 UTC
Sorry, there where one wrong "no" in my description. What I meant was
having openssl installed from ports so it lies in LOCALBASE and not in
the base system made bind9 failing to build.
But I can't reproduce it now, so you may close that PR... nevertheless,
changing --with-openssl to --with-openssl=${OPENSSLBASE} might be a good
catch anyway since it will respects WITH_OPENSSL_PORT or WITH_OPENSSL_BASE
and I can't see anything wrong with changing it.

 Oliver Lehmann
Comment 4 Doug Barton freebsd_committer 2005-03-13 23:12:38 UTC
State Changed
From-To: feedback->closed

Thanks for your explanation. Given that you can't reproduce 
the problem, I'm loathe to change something that's worked 
for years for users in all 3 openssl conditions.  

If the problem pops up again, let's re-examine this.