Date: Tue, 19 Dec 2017 15:05:09 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 224447] devel/glibmm ustring.h:256:13: error: expected ';' at end of declaration list Message-ID: <bug-224447-6497-xuL8tgrIWq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224447-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-224447-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224447 --- Comment #3 from Chris Hutchinson <portmaster@bsdforge.com> --- Thanks for the quick reply! (In reply to Ting-Wei Lan from comment #2) > (In reply to Chris Hutchinson from comment #0) >=20 > 1. GNOME never uses GitHub as its official repo. GitHub repo is just a > mirror and the official repo is at https://git.gnome.org/browse/glibmm/. Thanks for the correction. >=20 > 2. glibmm 2.6 is a very old version. The latest version which is compatib= le > with glibmm-2.4 ABI is glibmm 2.52. FreeBSD ports include glibmm 2.50.1, = so > I think if the update is really needed, the request should be 'update to > 2.52.1', not 'update to 2.6' which is actually a downgrade to a version > released more than 10 years ago. Well, that sounds about right. But looking at the 2.52.1 source. I see that the same errors will occur. clang expects ~ustring(); but gets ~ustring() noexcept; expects virtual ~Exception(); but gets virtual ~Exception() noexcept =3D 0; ... >=20 > I believe the problem is that you don't enable C++11 support in your port. > glibmm requires C++11 since version 2.46. That's a good point. Maybe I'm just doing it wrong. But throwing USES=3D compiler:c++11-lang and CXXFLAGS+=3D -Wc++11-extensions -Wc++11-long-long didn't get me any closer. Thanks again, for taking the time to respond. --Chris --=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-224447-6497-xuL8tgrIWq>