On 20 January 2015 at 15:17, Amos Jeffries <squ...@treenet.co.nz> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I have just fixed a few clang detected build errors and 3.5 is now > building cleanly here on FreeBSD 10 with the default Clang. > > Please try to build the latest 3.5 snapshot (which will be labeled > r13735 or higher). It should build fine with either the system default > clang compiler or your GCC 4.9 install, but not with the system > default GCC 4.4. > > I will check on that. However, I earlier today managed to compile 3.5.0.4 using clang. The problem I have been facing now is about 'forwarding loop detected' over and over... checking on my PF rules hasn't yielded anything. And I am now wondering why 3.4.11 wasn't seeing these forwarding loops.. > > (gdb) bt #0 0x0000000803a30469 in swapcontext () from > > /lib/libthr.so.3 #1 0x0000000803a30062 in sigaction () from > > /lib/libthr.so.3 #2 <signal handler called> #3 0x0000000803d6b04a > > in kevent () from /lib/libc.so.7 #4 0x000000000086335c in > > Comm::DoSelect (msec=981) at ModKqueue.cc:264 > > > Looks like a bug in the system threading library. Though why Squid is > triggering it is unknown. Maybe related to the two GCC versions with > different libc perhapse? > I only have one gcc version on my system -gcc49 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 "I can't hear you -- I'm using the scrambler."
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
