Bug 46507

Summary: Failure to Build Postfix-Current due to SASL
Product: Ports & Packages Reporter: Scott M.Likens <damm>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Scott M.Likens 2002-12-24 05:10:02 UTC
	Problem with Selecting SASL2 + TLS + LDAP, includes MySQL without
	making MySQL a dependancy.

Fix: 

Modify configure.postfix with removing

                       if [ -f ${PREFIX}/lib/libsasl.a ]; then
if nm ${PREFIX}/lib/libsasl.a | grep -wq
"mysql_verify_password"; then
echo "POSTFIX_CCARGS+=  -DHAS_MYSQL -I\${LOCALBASE}/include/mysql" 
echo "POSTFIX_AUXLIBS+= \${LOCALBASE}/lib/mysql/libmysqlclient.a -lm -lz" 

that and it's counterparts.  It incorrect, same with verifiying SASL2, i 
have no such function, yet it still includes MySQL in it.

Thanks.
How-To-Repeat: 	Select SASL2 with SASL2 built without MySQL Support, without 
	MySQL added either.
Comment 1 Tilman Keskinoz freebsd_committer freebsd_triage 2003-05-09 11:41:47 UTC
Class Changed
From-To: maintainer-update->sw-bug

Accurate class
Comment 2 Tilman Keskinoz freebsd_committer freebsd_triage 2003-05-09 11:41:54 UTC
Does the maintainer know about this problem?
Comment 3 Vivek Khera 2003-05-09 15:53:37 UTC
>>>>> "TL" == Tilman Linneweh <arved@FreeBSD.org> writes:

TL> Does the maintainer know about this problem?

Yes.  I keep getting conflicting reports.  Some say you need some lib,
some say you don't it.  I don't have the proper information to know
when you must link libkrb and when you don't need it, and what
additional libs might be needed.  Most people have old outdated libkrb
sitting around which causes the problem.  I think buildworld should
nuke old libkrb if it is not being installed....

I'm preparing an update to postfix 2.0.9 which will remove the -ldes
link since that's old too!
Comment 4 Gerald Pfeifer freebsd_committer freebsd_triage 2003-05-20 22:29:11 UTC
State Changed
From-To: open->closed

I discussed this with this port's maintainer, and he suggested to close this 
PR with the following comment: "Maintainer unable to reproduce error with 
SASL1"