Date: Sun, 12 Apr 2015 13:24:01 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: danfe@FreeBSD.org Cc: svn-ports-head@FreeBSD.org, marino@FreeBSD.org, svn-ports-all@FreeBSD.org, amdmi3@amdmi3.ru, ports-committers@FreeBSD.org Subject: Re: svn commit: r383466 - in head/x11-toolkits/wxgtk30: . files Message-ID: <201504122024.t3CKO1Af001846@gw.catspoiler.org> In-Reply-To: <20150412121509.GA99970@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 Apr, Alexey Dokuchaev wrote:
> 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.
Our copy of gcc42 in base doesn't claim to support anything newer than
c++98. This is what I get when I print ${COMPILER_FEATURES}:
libstdc++ c89 c99 gnu89 gnu99 c++98 gnu++98
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201504122024.t3CKO1Af001846>