Date: Wed, 5 Jul 2023 12:08:02 +0000 From: Alexey Dokuchaev <danfe@freebsd.org> To: Nuno Teixeira <eduardo@freebsd.org> Cc: John Baldwin <jhb@freebsd.org>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 348c10112de6 - main - devel/freebsd-gcc9: Build with -std=c++11. Message-ID: <ZKVdIh4jSge1sDsx@FreeBSD.org> In-Reply-To: <CAFDf7UJz-PVu00D5ubhUN-Qw72549t6Fy0P3jaorefsN6YH4iQ@mail.gmail.com> References: <202307041714.364HEbPI098704@gitrepo.freebsd.org> <ZKTjj84P5XCzuGzG@FreeBSD.org> <CAFDf7UJz-PVu00D5ubhUN-Qw72549t6Fy0P3jaorefsN6YH4iQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 05, 2023 at 09:39:06AM +0100, Nuno Teixeira wrote: > Hello, > > This fix inspired me to try it on net-p2p/amule that is failing on > clang16. This port already have USES=compiler:c++11-lang This is no-op these days: at least on most arches system compiler already is C++11-capable and defaults to C++11 on stable branches. Now default was bumped to C++17 on -CURRENT with recent Clang update. > and I added USE_CXXSTD=c++11 and it fixes build. > > My question is, isn't a PORTREVISION bump reccomended since build have > changed with -std=c++11? I wouldn't bump it: where C++ is the default (12/13) adding USE_CXXSTD won't change anything, and on -CURRENT it allows the package to appear, as previously it didn't build. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZKVdIh4jSge1sDsx>