RE: [squid-users] Re: Squid Compile Errors

FYI - configure options being used:

./configure --enable-icap-client --enable-ssl --with-openssl=/usr/local/ssl --prefix=/apps/cwapps/squid-3119 --enable-storeio=diskd,aufs,ufs --with-aio-threads=N --enable-removal-polices=heap,lru --enable-icmp --enable-snmp --enable-cache-digests --enable-useragent-log --enable-referer-log --enable-follow-x-forwarded-for --disable-ident-lookups --enable-auth-basic=LDAP,MSNY,POP3,SMB --enable-auth-ntlm=smb_lm,no_check

Thanks and regards,
Justin

-----Original Message-----
From: Justin Lawler
Sent: Wednesday, March 21, 2012 12:16 PM
To: 'GarethC'; squid-users_at_squid-cache.org
Subject: RE: [squid-users] Re: Squid Compile Errors

Hi Gareth,

OpenLDAP installed, as well as 'SUNWlldap'

root_at_mib01 /> pkginfo | grep [lL][dD][aA][pP]
application SMColdap openldap
system SUNWlldap LDAP Libraries

I see the libnet.so libraries as part of the java runtime on the machine. I guess these are different?

Looks like best way is to install libnet anyway.

Thanks for the help!
Justin

-----Original Message-----
From: GarethC [mailto:gareth_at_garethcoffey.com]
Sent: Tuesday, March 20, 2012 11:55 PM
To: squid-users_at_squid-cache.org
Subject: [squid-users] Re: Squid Compile Errors

Hi Justin,

I've compiled Squid on Solaris systems before and there can be the odd dependency nightmare.
I haven't compiled Squid with ldap_auth but after a bit of digging it looks like you may need to install libnet (no dependencies other than possibly
libpcap) as this is a dependency of libldap.

What version of LDAP are you running on the box? (i.e. OpenLDAP?)

If you run 'cd /; find ./ -name libnet.so' on your other Solaris box, if it's found it may suggest libnet was installed from source as opposed to package based.

Thanks,
Gareth

-----
Follow me on...

My Blog
Twitter
LinkedIn
Facebook

--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Compile-Errors-tp4487870p4489311.html
Sent from the Squid - Users mailing list archive at Nabble.com.
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp