Re: [squid-users] Re: Re: Re: squid_ldap_group against nested groups/Ous

On 13/11/10 22:30, Eugene M. Zheganin wrote:
> Hi.
>
> On 05.11.2010 21:01, Markus Moeller wrote:
>> Hi
>>
>> I get the same successful results on 64 bit FreeBSD 8.0.
>>
>> $ uname -a
>> FreeBSD freebsd-80-64.freebsd.home 8.0-RELEASE FreeBSD 8.0-RELEASE #0:
>> Sat Nov 21 15:02:08 UTC 2009
>> root_at_mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
>>
>> $ ldd squid_kerb_ldap
>> squid_kerb_ldap:
>> libgssapi.so.10 => /usr/lib/libgssapi.so.10 (0x800652000)
>> libheimntlm.so.10 => /usr/lib/libheimntlm.so.10 (0x80075b000)
>> libkrb5.so.10 => /usr/lib/libkrb5.so.10 (0x800860000)
>> libhx509.so.10 => /usr/lib/libhx509.so.10 (0x8009cd000)
>> libcom_err.so.5 => /usr/lib/libcom_err.so.5 (0x800b0c000)
>> libcrypto.so.6 => /lib/libcrypto.so.6 (0x800c0e000)
>> libasn1.so.10 => /usr/lib/libasn1.so.10 (0x800ea6000)
>> libroken.so.10 => /usr/lib/libroken.so.10 (0x801025000)
>> libcrypt.so.5 => /lib/libcrypt.so.5 (0x801136000)
>> libldap-2.4.so.7 => /usr/local/lib/libldap-2.4.so.7 (0x80124f000)
>> liblber-2.4.so.7 => /usr/local/lib/liblber-2.4.so.7 (0x801390000)
>> libc.so.7 => /lib/libc.so.7 (0x80149d000)
>> libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x8016d7000)
>> libssl.so.6 => /usr/lib/libssl.so.6 (0x8017ef000)
>>
>> Is it possible that you have another kerberos package installed ? How
>> does your ldd look ? I installed a standard freebsd 8.0 84 bit plus
>> ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/8.0-RELEASE/packages/net/openldap-sasl-client-2.4.18.tbz
>> for ldap with sasl support.
>>
> First of all, sorry for a delayed answer, I'm not of that kind of
> persons that ask for help and never read answers. I had a couple of
> harsh weeks with crashes and late working. :)
>
> Yes, I have multiple krb5 installations on machines where the build
> didn't succeed due to incompatible types, you were right. Also I have
> updated the production proxy that was on FreeBSD 7.2 to 8.1 (and had a
> harsh week due to wonderful em(4) issue, fixed in -STABLE), but now the
> building on this machine is fine, except one warning that can be easily
> fixed by removing -Werror (once again, why -Werror ?).
>
> If you're interested the warning is about:
>
> [...]
> gcc -DHAVE_CONFIG_H -I. -I/usr/include -I/usr/local/include -g -O2 -Wall
> -Wno-unknown-pragmas -Wextra -Wcomment -Wpointer-arith -Wcast-align
> -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
> -Wmissing-declarations -Wdeclaration-after-statement -Wshadow -MT
> support_group.o -MD -MP -MF .deps/support_group.Tpo -c -o
> support_group.o support_group.c
> support_group.c: In function 'utf8dup':
> support_group.c:43: warning: declaration of 'dup' shadows a global
> declaration
> /usr/include/unistd.h:330: warning: shadowed declaration is here
> [...]

Because warnings indicate problems as much as errors. Ignoring them in
leads to major problems later. We depend on people like yourself
reporting them at the warning stage before that happens.

In this case its warning about some confusion between a system dup() and
a second local one which may differ in some critical way on some systems.

Thanks for the report.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.9
   Beta testers wanted for 3.2.0.3