Ok, found the root cause. The -no-gcc flag, which I'd very much like us to use to detect gcc-isms is causing this. The problem is probably in glibc, not in squid. We can change this to -gcc-sys; the effect is that the __GNUC__ etc. macros get only defined when compiling system headers. This ensures compatibility but should also allow us to detect gcc-isms and fail if we by mistake use one.
What do you think? On Wed, Jan 15, 2014 at 3:42 PM, Kinkie <gkin...@gmail.com> wrote: > I'm trying a build downgrading the icc from 14.0 to 13.1 (which used > to work). Let's see. > > > On Tue, Jan 14, 2014 at 11:00 PM, Francesco Chemolli <gkin...@gmail.com> > wrote: >> Maybe. >> I'll try reverting to an older icc version tomorrow. >> >> Thanks for the googling! >> >> >> >> >> On 14 Jan 2014, at 22:59, Amos Jeffries <squ...@treenet.co.nz> wrote: >> >>> I've taken a look at this link failure for ICC on CentOS: >>> >>> On 2014-01-15 10:47, n...@squid-cache.org wrote: >>>> See <http://build.squid-cache.org/job/3.HEAD-amd64-CentOs-icc/1235/changes> >>> >>> >>>> AclRegs.o: In function >>>> `_INTERNAL_20_______src_AclRegs_cc_a4e5ab95::__gthread_active_p()': >>>> /usr/include/c++/4.4.7/x86_64-redhat-linux/bits/gthr-default.h:242: >>>> undefined reference to >>>> `_INTERNAL_20_______src_AclRegs_cc_a4e5ab95::__gthrw_pthread_cancel(unsigned >>>> long)' >>>> AclRegs.o:(.rodata+0x0): undefined reference to >>>> `_INTERNAL_20_______src_AclRegs_cc_a4e5ab95::__gthrw_pthread_cancel(unsigned >>>> long)' >>> >>> It seems to be explained by this discussion from 2010: >>> http://software.intel.com/en-us/forums/topic/289533 >>> >>> So perhapse the ICC version and GCC versions installed headers are clashing >>> yet again? >>> >>> Amos >> > > > > -- > /kinkie -- /kinkie
