Date: Sun, 12 Apr 2015 15:09:00 +0300 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: marino@freebsd.org Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r383466 - in head/x11-toolkits/wxgtk30: . files Message-ID: <20150412120900.GH21982@hades.panopticon> In-Reply-To: <552A30CF.6060204@marino.st> References: <201504061849.t36InrtY095320@svn.freebsd.org> <20150410174533.GB77333@hades.panopticon> <55281352.6060904@marino.st> <20150412002519.GG21982@hades.panopticon> <552A0F83.10704@marino.st> <552A30CF.6060204@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
* John Marino (freebsd.contact@marino.st) wrote: > > I got a report py-wxPython30 broke too. > > So for those ports that break on 10 but build on < 10, it seems that > > gcc4.8+ is happy enough with the c++ code but clang isn't. > > > > since these are using compiler:c++11-lib, it seems to me the only > > solution is to actually fix the c++ code. > > > > Either that, or remove "compiler:c++11-lib" and set "USE_GCC" for > > freeBSD < 10. > > > > Thoughts? > > > > A prime example of why c++ sucks by the way. Nothing like that. It's just that crappy incompatible code sucks, instead we could just use c++11 by default everywhere, which would automatically get us some performance gains. > I got three of them fixed, but I can't fix gambit. For some reason, > gcc48 doesn't build it on F10 while it will on F8. I have concluded the > only way forward on this port is either mark it broken for F9+ or patch > the c++ errors. I am not a c++ guy though. I'll look into this. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150412120900.GH21982>