Date: Sat, 28 Feb 2015 12:39:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 198091] Fix devel/google-sparsehash build with clang 3.6.0 Message-ID: <bug-198091-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198091 Bug ID: 198091 Summary: Fix devel/google-sparsehash build with clang 3.6.0 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: vd@FreeBSD.org Reporter: dim@FreeBSD.org Assignee: vd@FreeBSD.org Flags: maintainer-feedback?(vd@FreeBSD.org) Created attachment 153611 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=153611&action=edit Use swap member function instead of free swap function, to appease clang 3.6.0 During the exp-run in bug 197395, it was found that devel/google-sparsehash gives errors with clang 3.6.0: http://package18.nyi.freebsd.org/data/headamd64PR197395-default/2015-02-27_12h37m16s/logs/errors/google-sparsehash-2.0.2_2.log The error is because clang 3.6.0 has become more strict about matching non-type template parameters. However, I am not completely sure if the construction google-sparsehash is using is legal or not, and whether clang is correct to refuse it. It looks like different versions of gcc have different opinions on the legality of non-type template parameter deduction. I will submit a bug report upstream with clang to figure that out, but in the mean time, I want to propose using the attached patch, which makes hashtable_test.cc use the swap member functions, instead of the free swap functions. --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Auto-assigned to maintainer vd@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198091-13>