[squid-users] Problem with running squid 3.5 on windows 7

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19/12/2014 12:32 p.m., Eldar Akchurin wrote:
> 
> 
> 
> Hi, I have cross-compiled squid 3.5 with mingw32-w64 on Ubuntu. The
> properties are: c:\squid\sbin>squid -v Squid Cache: Version
> 3.5.0.3-20141209-r13687 Service Name: squid Test build configure
> options:  '--host=i686-w64-mingw32' '--prefix=c:/squid'
> 'CXXFLAGS=-DWI NVER=0x601 -D_WIN32_WINNT=0x601 -fpermissive'
> 'CFLAGS=-DWINVER=0x601 -D_WIN32_WI NNT=0x601 -fpermissive'
> 'BUILDCXX=g++' 'BUILDCXXFLAGS=-DFOO' '--enable-build-inf o=Test
> build' 'host_alias=i686-w64-mingw32' --enable-ltdl-convenience
> 
> When I try to run it on windows 7 64, it gives a critical error at
> start, below is the debug trace
<snip>


> 2014/12/19 00:17:40.171| Address.cc(379) lookupHostIP: Given Non-IP
> '127.0.0.1': No such host is known. 2014/12/19 00:17:40.171|
> aclIpParseIpData: unknown first address in '127.0.0.1/3 2' 
> 2014/12/19 00:17:40.171| tools.cc(543) leave_suid: leave_suid: PID
> 4792 called FATAL: Bungled Default Configuration line 6: acl
> localhost src 127.0.0.1/32 ::1 Squid Cache (Version
> 3.5.0.3-20141209-r13687): Terminated abnormally. CPU Usage: 0.000
> seconds = 0.000 user + 0.000 sys Maximum Resident Size: 0 KB Page
> faults with physical i/o: 0 Could you please advice what I'm doing
> wrong or whether this is a bug? Thank you!-eAdd to Calendar
> 

Thank you for testing this all out Eldar. It seems you have gotten a
little further than I have with this (I diverted to working on native
MinGW build issues).

This is a bug. Though where it is coming from is still unknown. The
operation being performed is that Squid is passing the IP text string
to the system getaddrinfo() resolver API for conversion to a number.

First thing to check is whether Squid is actually using the native OS
API or the stub replacement bundled in compat/. The config.log file
generated during build will have an entry indicating whether
getaddrinfo() was found or not in the MinGW headers. If the detection
failed there will be some debug info about what broke.

Amos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUk5aTAAoJELJo5wb/XPRjiLkIAL0nS83JZLdTV7DfMFsDFqRJ
yU7rFKWwqXp8P64K5Woedwga4JMpUrkxvbQ1t+wqS3mKWX3hJ72+M71juVeyt7pr
pMZYGkoSZNXwhh/i73BxH2hVX7lysI8WKUw0NgBW7cZYe7KleLIODf8GWQhmXhJi
vQh5uAfeYO6W/V+wwiRpY47H49yuU3UpypzsZ4P2i88+QvKZaef0T4ZJN8Wlresg
ldc7vwBTqQ7p810s87dUrYAuCYZJKqYj/cQnUX86dEgkfxZSPwbDHS8qQdUxAvMb
DqIZRp+H7hdO2DK1Sh1FCwyDEEbkuc0O/GurH6Nnw9IVpSAmWr4l8l82WdDXd4o=
=4unG
-----END PGP SIGNATURE-----