First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 182725
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Network Proxy Developers <net-proxy@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: fcla.marktplaats@gmail.com
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 182725 depends on: Show dependency tree
Show dependency graph
Bug 182725 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-06-20 19:52 0000
The new squidguard v. 1.2.1 won't compile.
It barfs on missing ldap lib.

I do not have ldap (and don't want it).
There does not seems to be an USE flag for squidguard to enable/disable ldap
during compilation.
The squidguard docs state that ldap support only will be compiled when the
option --wth-ldap is provided to configure. This is not the case. It seems
squidguard always tries to compile now with ldapsupport.

Below the actual error message when emerging squidguard 1.2.1:

checking for ldap_init in -lldap... no

LDAP library not found


Reproducible: Always

Steps to Reproduce:
1. sync portage
2. emerge squidguard


Actual Results:  
checking for ldap_init in -lldap... no

LDAP library not found


Expected Results:  
compile

------- Comment #1 From Alin Năstac 2007-06-24 10:43:56 0000 -------
Fixed in 1.2.1-r1. Thanks!

First Last Prev Next    No search results available      Search page      Enter new bug