On 06/13/2017 09:03 AM, L.P.H. van Belle wrote: > Looks the same like. > > http://squid-web-proxy-cache.1019090.n4.nabble.com/Compiling-squid-3-5-4-with-ecap-enabled-td4671325.html The "undefined references" problem on that thread looks the same, but the "PKG_CONFIG_PATH is the path to the pkg-config binary" solution(?) to that problem sounds wrong because PKG_CONFIG_PATH is where pkg-config looks for .pc files, not where pgk-config binary itself lives. AFAICT, Naveen is using PKG_CONFIG_PATH correctly, and I see no serious problems with Naveen's build commands. I do not know why the generated Makefile gets bogus variable values. Could be some kind of pkg-config or PKG_CHECK_MODULES bug or compatibility problem. Hopefully, pkg-config debugging I asked for in my previous email will point us in the right direction. Alex. >> -----Oorspronkelijk bericht----- >> Van: squid-users >> [mailto:squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx] Namens >> Norbert Naveen >> Verzonden: dinsdag 13 juni 2017 16:46 >> Aan: 'Alex Rousskov'; squid-users@xxxxxxxxxxxxxxxxxxxxx >> Onderwerp: Re: Error Compiling squid-3.5.26 >> with libecap-1.0.1 on CentOS Linux release 7.3.1611 >> >> Hello >> The Make output can be found at >> https://drive.google.com/open?id=0B_dDVNpzSGEKcFlMSlBVZWs5c2c >> >> >> And the output of # grep 'EXT_LIBECAP_.*=' >> src/adaptation/ecap/Makefile EXT_LIBECAP_CFLAGS = >> /usr/local/lib EXT_LIBECAP_LIBS = /usr/local/lib >> >> >> I did the below to no effect >> make -k clean; >> ./configure --enable-ecap >> make > /tmp/build.log 2>&1 >> >> Build Log is available at >> https://drive.google.com/open?id=0B_dDVNpzSGEKM3JSUHNJLWJlWjA >> >> Thanks >> Naveen >> >> -----Original Message----- >> From: Alex Rousskov [mailto:rousskov@xxxxxxxxxxxxxxxxxxxxxxx] >> Sent: Tuesday, June 13, 2017 2:12 AM >> To: norbert.naveen@xxxxxxxxx; squid-users@xxxxxxxxxxxxxxxxxxxxx >> Subject: Re: Error Compiling squid-3.5.26 with >> libecap-1.0.1 on CentOS Linux release 7.3.1611 >> >> On 06/12/2017 11:29 AM, Norbert Naveen wrote: >> >>> I have attached Outputs of both Configure and Make And libecap.pc >>> contents are as below >> >> Your ./configure output and libecap.pc contents look good to >> me, but there is no sign of the eCAP library (-lecap) being >> linked with Squid during "make". If running "make clean; >> ./configure ...; make" does not fix this, then please find a >> way to post a link to the _entire_ build log. Something along >> these lines should be able to capture it: >> >> $ make -k clean; (./configure ...; make) > /tmp/build.log 2>&1 >> >> You may want to compress /tmp/build.log. Please post a link >> to some public file sharing site here instead of the file >> itself. Even compressed, it may be too big to email. >> >> Also, what does the following command output? >> >> $ grep 'EXT_LIBECAP_.*=' src/adaptation/ecap/Makefile >> >> (adjust the Makefile path if necessary if you are not >> building Squid its source directory) >> >> >> Cheers, >> >> Alex. >> >> _______________________________________________ >> squid-users mailing list >> squid-users@xxxxxxxxxxxxxxxxxxxxx >> http://lists.squid-cache.org/listinfo/squid-users >> > > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users > _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
