Date: Wed, 25 Jan 2017 22:37:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 216468] textproc/pugixml causes inconsistencies with c++11 and later Message-ID: <bug-216468-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216468 Bug ID: 216468 Summary: textproc/pugixml causes inconsistencies with c++11 and later Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: riggs@FreeBSD.org CC: ybungalobill@gmail.com CC: ybungalobill@gmail.com Flags: maintainer-feedback?(ybungalobill@gmail.com) Created attachment 179316 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D179316&action= =3Dedit Enable c++11 on pugixml pugixml installs a bogus pugixml.hpp file that contains the following secti= on: ... // Copy constructor/assignment operator xpath_node_set(const xpath_node_set& ns); xpath_node_set& operator=3D(const xpath_node_set& ns); #if __cplusplus >=3D 201103 // Move semantics support xpath_node_set(xpath_node_set&& rhs); xpath_node_set& operator=3D(xpath_node_set&& rhs); #endif ... Right now, pugixml is built without c++11 support. Subsequently, the result= ing library does not contain this move constructor. If a dependent port, however, is built with -std=3Dc++11/14/1z, it will par= se the pugixml.hpp header and erroneously assume that the pugixml.(a|so) contain t= he move constructor. Subsequently, the build will fail with a linker error. Attached patch enables c++11 for the pugixml port and allow dependent ports with -std=3Dc++11/14/1z to build again. --=20 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-216468-13>