On 18 Jun 2016, at 19:13, Yuri <[email protected]> wrote: > > I regularly get the fallout messages for my net-im/ring-daemon port. It > breaks on 10.1 with the c++11 -related message: > > In file included from > /wrkdirs/usr/ports/net-im/ring-daemon/work/ring-daemon-56ec56f/src/manager.h:45: > /wrkdirs/usr/ports/net-im/ring-daemon/work/ring-daemon-56ec56f/src/account_factory.h:121:107: > error: chosen constructor is explicit in copy-initialization > std::map<std::string, std::function<std::shared_ptr<Account>(const > std::string&)> > generators_ = {}; > > ^~ > /usr/include/c++/v1/map:838:14: note: constructor declared here > explicit map(const key_compare& __comp = key_compare()) > > > net-im/ring-daemon doesn't break on 10.3 system though. It has > USES=compiler:c++14-lang. > > There are two questions: > 1. Why clang36 works differently on 10.1 and 10.3?
In this particular case, because 10.1 doesn't have r278724 [1], which updated libc++ in stable/10 to the latest version in head. This was an upstream libc++ bug [2], fixed in upstream r202994 [3]. I think this can be worked around by removing the '=' sign, but I can't verify it at the moment. -Dimitry [1] https://svnweb.freebsd.org/changeset/base/278724 [2] https://llvm.org/bugs/show_bug.cgi?id=15724 [3] http://llvm.org/viewvc/llvm-project?view=revision&revision=202994
signature.asc
Description: Message signed with OpenPGP using GPGMail
