src/authorizer.cc: In member function 'int authorizer::login_connection(conn*, const char*, const char*)': src/authorizer.cc:157:21: error: call of overloaded 'copy_if(std::vector<ruleset*>::iterator, std::vector<ruleset*>::iterator, std::back_insert_iterator<std::vector<ruleset*> >, match_helper)' is ambiguous match_helper(this)); ^ In file included from src/authorizer.cc:15:0: include/util/generic.h:84:6: note: candidate: Out util::copy_if(In, In, Out, Pred) [with In = __gnu_cxx::__normal_iterator<ruleset**, std::vector<ruleset*> >; Out = std::back_insert_iterator<std::vector<ruleset*> >; Pred = match_helper] Out copy_if(In first, In last, Out res, Pred p) ^~~~~~~ In file included from /usr/local/lib/gcc6/include/c++/algorithm:62:0, from src/authorizer.cc:14: /usr/local/lib/gcc6/include/c++/bits/stl_algo.h:734:5: note: candidate: _OIter std::copy_if(_IIter, _IIter, _OIter, _Predicate) [with _IIter = __gnu_cxx::__normal_iterator<ruleset**, std::vector<ruleset*> >; _OIter = std::back_insert_iterator<std::vector<ruleset*> >; _Predicate = match_helper] copy_if(_InputIterator __first, _InputIterator __last, ^~~~~~~ build log: http://sprunge.us/PicF
Created attachment 184746 [details] Proposed patch The attached patch forces the use of an older C++ standard to fix the build; since the project seems to be unmaintained upstream I don't think it's worth making the code work with C++11.
Comment on attachment 184746 [details] Proposed patch Approved by: portmgr (blanket, build/run-time fixes)
A commit references this bug: Author: rakuco Date: Tue Aug 1 09:01:14 UTC 2017 New revision: 447014 URL: https://svnweb.freebsd.org/changeset/ports/447014 Log: Explicitly build with -std=gnu++03. This fixes the build with GCC 6, which defaults to -std=gnu++14. The project, which seems to be unmaintained upstream, is incompatible with C++11 and later. PR: 219298 Approved by: portmgr (blanket approval) Changes: head/irc/ezbounce/Makefile
Setting merge-quarterly-. The rationale from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484#c23 also applies to this bug.