Date: Tue, 19 Dec 2017 08:17:01 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 223538] emulators/visualboyadvance-m 2.0.0b2_4 build error with /usr/local/include/glibmm-2.4 and -Wc++11-extensions Message-ID: <bug-223538-13-JHqr3VWOg8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223538-13@https.bugs.freebsd.org/bugzilla/> References: <bug-223538-13@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=3D223538 Chris Hutchinson <portmaster@bsdforge.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |portmaster@bsdforge.com --- Comment #2 from Chris Hutchinson <portmaster@bsdforge.com> --- I'm also running into this problem with (at least) one of the ports I maintain. The GNOME repo[1] for glibmm has several newer versions, and looking over the source, it appears version 2.6 will overcome at least most of the greif endured in this version. I suppose another option would be to pass C(PP)FLAGS eg; -Wc++11-extensions -Wc++11-long-long . But this is only masking the problem with duct tape. devel/glibmm is no longer maintainable with the toolchains in FreeBSD. If this doesn't get updated to at least 2.6. I'm simply going to have to drop some ports I maintain. 1. https://github.com/GNOME/glibmm/tree/glibmm-2-6 --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-223538-13-JHqr3VWOg8>