Re: Fwd: Problems with Squid 2.2S4 on Solaris x86/2.5

Earlier today, Reuben Farrelly wrote:

> I may have partially solved my problem. I recompiled squid last night to
> add a new option to the compile, and this appeared while compiling:
>
> >gcc -g -Wall -D_REENTRANT -I. -I../include -I../include -c comm.c
> >comm.c: In function `comm_connect_addr':
> >comm.c:443: warning: passing arg 4 of `getsockopt' from incompatible pointer type
> >gcc -g -Wall -D_REENTRANT -I. -I../include -I../include -c comm_select.c
>
> Could this be related? Anyone else with squid 2.2S4 on Solaris 2.5 seen
> this problem as well?

Just as an extra data point - I get this warning (and others) whilst compiling
(Squid/2.2.STABLE4, FSF GCC 2.8.1), but I'm using Solaris 2.5.1 (not 2.5) on
an UltraSPARC (not x86). Like you, I'm using async I/O and cache digests (no
WebDAV patch), but I don't see this entry in my cache.log file:

> >1999/07/30 01:38:35| commBind: Cannot bind socket FD 22 to
> >203.100.224.20:0: (22) Invalid argument

At least, not today anyway (I don't keep cache.log beyond midnight).

> >Yet in squid.conf:
> > tcp_outgoing_address 203.100.224.20
[...]
> >iprb0:2: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
> > inet 203.100.224.20 netmask ffffff00 broadcast 203.100.224.255

I'm not using "tcp_outgoing_address" or aliased interfaces, either.

Cheers..

dave
Received on Sun Aug 01 1999 - 04:38:55 MDT