From owner-svn-ports-all@FreeBSD.ORG  Sun Apr 12 12:15:09 2015
Return-Path: <owner-svn-ports-all@FreeBSD.ORG>
Delivered-To: svn-ports-all@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1033)
 id 617579C1; Sun, 12 Apr 2015 12:15:09 +0000 (UTC)
Date: Sun, 12 Apr 2015 12:15:09 +0000
From: Alexey Dokuchaev <danfe@FreeBSD.org>
To: Dmitry Marakasov <amdmi3@amdmi3.ru>
Subject: Re: svn commit: r383466 - in head/x11-toolkits/wxgtk30: . files
Message-ID: <20150412121509.GA99970@FreeBSD.org>
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>
 <20150412120900.GH21982@hades.panopticon>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150412120900.GH21982@hades.panopticon>
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, marino@freebsd.org,
 ports-committers@freebsd.org
X-BeenThere: svn-ports-all@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the ports tree <svn-ports-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-ports-all>,
 <mailto:svn-ports-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-ports-all/>
List-Post: <mailto:svn-ports-all@freebsd.org>
List-Help: <mailto:svn-ports-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-ports-all>,
 <mailto:svn-ports-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Apr 2015 12:15:09 -0000

On Sun, Apr 12, 2015 at 03:09:00PM +0300, Dmitry Marakasov wrote:
> * 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.

Of course it sucks.  Do you know another comparably prominent example
when things breaking so spectacularly all over the place? :-)

If one must use C++ to develop e.g. a library intended to be used in
open-source projects, they really should stick to c++03 (and make sure
their code is fine by gcc42) for at least couple of years from now.

./danfe