Date: Thu, 06 Jul 2023 10:51:30 +0200 From: Raphael Kubo da Costa <rakuco@FreeBSD.org> To: "Hurling, Rainer" <rhurlin@FreeBSD.org>, eduardo@FreeBSD.org Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: b56d0bc41af7 - main - devel/libcutl: Explain why USE_CXXSTD=c++11 is used Message-ID: <6cf6a5eb00dfac8358dfcb1e1d5b69f293c3e85a.camel@FreeBSD.org> In-Reply-To: <e56d377d0985b86be2291b64bb3c686742283dde.camel@FreeBSD.org> References: <202307050850.3658oPOA049562@gitrepo.freebsd.org> <CAFDf7UJRc4bd3XVq%2Bb7Za2cLN7h_hkN1mpPTGQiSajV1p9A=0g@mail.gmail.com> <ebcdf01a-2b73-39c3-b6e4-25659e53b1ca@gwdg.de> <e56d377d0985b86be2291b64bb3c686742283dde.camel@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> As for a PORTREVISION bump: it _could_ be the case that the generated > files differ now, as in the past the default standard was gnu++14 > rather than c++11. For leaf ports like these two I don't think the > difference really matters, but I've been semi-abstent for so long > that > portmgr@ or someone more active may have a better guideline. By the way, one other possibility that I haven't tested myself if compatibility is an issue would be doing something like https://cgit.freebsd.org/ports/commit/?id=3D4e0c2ae319222145ab0b3f37c0ba52f= 596426d5a but passing USE_STDCXX=3Dgnu++14 instead of changing CXXFLAGS. This would guarantee that non-main with older clang releases remain untouched while also making clang 16 use the same standard that the older clang releases use.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6cf6a5eb00dfac8358dfcb1e1d5b69f293c3e85a.camel>