I assume Squid 4.0.1 has make errors because it was released just a few days ago? 4.0.1 also does not seem to be in the package install, only 3+ is in pkg install. How long until it is usually in the pkg install database? I tried the usual manual download, config, make, etc. And it seems to have errors on the "make", perhaps about 3/4 into the make, on a new FreeBSD OS install 10.2. Please advise. Below is the error starting... Code: In file included from Elements.cc:14: In file included from ../../src/HttpReply.h:14: In file included from ../../src/HttpMsg.h:18: In file included from ../../src/HttpHeader.h:13: ../../src/http/RegisteredHeaders.h:197:10: error: no type named 'vector' in namespace 'std' std::vector<const HeaderTableRecord *> idCache; ~~~~~^ ../../src/http/RegisteredHeaders.h:197:16: error: expected member name or ';' after declaration specifiers std::vector<const HeaderTableRecord *> idCache; ~~~~~~~~~~~^ ../../src/http/RegisteredHeaders.h:192:18: error: use of undeclared identifier 'idCache' return *(idCache[static_cast<int>(id)]); ^ 3 errors generated. *** Error code 1 Stop. make[3]: stopped in /usr/home/freebsd/squid-4.0.1/src/ftp *** Error code 1 Stop. make[2]: stopped in /usr/home/freebsd/squid-4.0.1/src *** Error code 1 Stop. make[1]: stopped in /usr/home/freebsd/squid-4.0.1/src *** Error code 1 Stop. make: stopped in /usr/home/freebsd/squid-4.0.1
Also it was reported here: http://bugs.squid-cache.org/show_bug.cgi?id=4352
Hi everyone! I haven't tried to build it. Angel Hess, have you tried this patch? http://www.squid-cache.org/Versions/v4/changesets/squid-4-14358.patch
Btw, the Squid-4 release notes ( http://wiki.squid-cache.org/Squid-4 ) state: | This series of Squid requires a C++11 capable compiler. The currently | known compilers which meet this criteria and build Squid-4 reliably | are GCC 4.9+ and Clang 3.5+ Don't know what are the ramifications, but FreeBSD 10.2 comes with an older version of clang 3.4.1.
(In reply to Mark.Martinec from comment #3) Yes, I hope it's just a recommendation, not a requarement.
(In reply to timp87 from comment #4) It may likely require: USES= compiler:c++11-lang
(In reply to timp87 from comment #2) I tried the patch. It seemed to compile, but extremely slowly, and make install not great. I do not want a patch, really. I just want to be able to use "pkg install squid" or "pkg install squid4". Will this be available at some point?
(In reply to Angel Hess from comment #6) I understand. That's what we all want.
(In reply to Angel Hess from comment #6) I don't promise, but I'll try to build when 4.0.2 is released and maybe even try to make a port if noone else does it.
@Pavel, I know in the past once Squid 3.x+1 was released Squid 3.x was considered EOL. This made having just 'www/squid' in ports make sense. From the looks of things at http://www.squid-cache.org/Versions/ it would seem that both are considered officially supported releases. Do you have an idea if both are going to be officially supported by upstream for some time?
(In reply to Jason Unovitch from comment #9) Well, I don't know. Sorry.
While we encourage collaboration, Bugzilla really isn't the place to be QA'ing a build failure for a port that doesn't exist in the ports tree yet. The reason is that it's unrelated to the www/squid port, and there's nothing that the current MAINTAINER (or any committers) can do to resolve it (close the issue). @Tim, over to you (assigned) to take care of from here.
Created attachment 163064 [details] www/squid40: initial version Hi! I made an initial port for squid4.0.x. It's only for testing purpose. What should be handled/checked or just thoughts: - CONFLICTS_INSTALL is not set (depends on how it will be added to ports tree); - Track http://bugs.squid-cache.org/show_bug.cgi?id=4376. Add files/patch-ecap-needs-attention for now. - Track http://bugs.squid-cache.org/show_bug.cgi?id=4377. No fix for now. - Wait for 4.0.3 release. Then check if 'XXX: On FreeBSD we don't need to involve krb5-config.' part of files/patch-configure is still needed. Some appropriate fixes are commited.
While waiting for 4.0.3 I'd like to illuminate my thoughts. Squid-4 is on RC stage right now. I'd copy www/squid to www/squid3 and update www/squid to 4th version when it was released. It would be better than just updating www/squid to 4 because it's a major version change. squid3 should be in ports tree at least for some time until we realize that squid4 is ready as a real replacement or it's EOL.
(In reply to timp87 from comment #13) Pavel, This makes sense to me. The only thing that comes to mind is asking on the Squid mailing lists what kind of support overlap Squid 3.5 will have after 4.0 is out of beta status. We should attempt to match the EOL in ports with the upstream EOL of the 3.x series. - Set 'open' while here as 'new' isn't entirely and we are waiting on upstream to call 4.x production ready before taking any action. We'll call this 'in progress' when 4.x is production ready and we start working on the port.
Created attachment 163693 [details] www/squid40: 4.0.3 It's squid-4.0.3. Same checklist as in comment #12, but last two are fixed by upstream.
Created attachment 167410 [details] www/squid40: 4.0.7
Created attachment 167474 [details] www/squid40: 4.0.7 new I've set options that don't need additional dependencies to ON by default. There is still one problem with Kerberos
Created attachment 169519 [details] www/squid40: 4.0.9 Catch up www/squid changes. Update to latest squid 4.0.9 version. Previously mentioned issues are no fixed.
(In reply to timp87 from comment #18) Sorry, I mean 'issues are fixed'
Created attachment 169847 [details] www/squid patch 1. Add conflicts to take into account new www/squid-devel 2. Change the way firewalls are choosen. Set ipfw as default.
Created attachment 169848 [details] www/squid-devel shar Add squid-4.0.9 as www/squid-devel
A commit references this bug: Author: matthew Date: Sun May 1 20:27:58 UTC 2016 New revision: 414422 URL: https://svnweb.freebsd.org/changeset/ports/414422 Log: Squid is a fully-featured HTTP/1.0 proxy which is almost (but not quite) HTTP/1.1 compliant. Squid offers a rich access control, authorization and logging environment to develop web proxy and content serving applications. WWW: http://www.squid-cache.org/ PR: 203860 Submitted by: timp87@gmail.com Changes: head/www/Makefile head/www/squid-devel/ head/www/squid-devel/Makefile head/www/squid-devel/distinfo head/www/squid-devel/files/ head/www/squid-devel/files/extra-patch-build-8-9 head/www/squid-devel/files/extra-patch-gen-stacktrace head/www/squid-devel/files/patch-compat_compat.h head/www/squid-devel/files/patch-compat_shm.cc head/www/squid-devel/files/patch-configure head/www/squid-devel/files/patch-src-cf.data.pre head/www/squid-devel/files/patch-src_DiskIO_Mmapped_MmappedFile.cc head/www/squid-devel/files/patch-src__ip__Intercept.cc head/www/squid-devel/files/patch-src_adaptation_ecap_ServiceRep.cc head/www/squid-devel/files/patch-src_ipc_mem_Segment.cc head/www/squid-devel/files/patch-src_tools.cc head/www/squid-devel/files/pkg-install.in head/www/squid-devel/files/pkg-message.in head/www/squid-devel/files/squid.in head/www/squid-devel/pkg-descr head/www/squid-devel/pkg-plist
A commit references this bug: Author: matthew Date: Sun May 1 20:31:29 UTC 2016 New revision: 414423 URL: https://svnweb.freebsd.org/changeset/ports/414423 Log: Add conflicts against the new squid-devel port Rework transparent proxy / firewall related options PR: 203860 Submitted by: timp87@gmail.com (maintainer) Changes: head/www/squid/Makefile
Committed, thanks!