Date: Sat, 8 Jul 2023 00:18:09 +0100 From: Nuno Teixeira <eduardo@freebsd.org> To: "Hurling, Rainer" <rhurlin@freebsd.org> Cc: Raphael Kubo da Costa <rakuco@freebsd.org>, 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: <CAFDf7ULKhd%2BZMEi3920sntmy1UPygsRWkqyQ%2B1j9BWPGsNOJKQ@mail.gmail.com> In-Reply-To: <34ea7315-6e9b-ebe4-6be8-5e0518cf969c@gwdg.de> References: <202307050850.3658oPOA049562@gitrepo.freebsd.org> <CAFDf7UJRc4bd3XVq%2Bb7Za2cLN7h_hkN1mpPTGQiSajV1p9A=0g@mail.gmail.com> <ebcdf01a-2b73-39c3-b6e4-25659e53b1ca@gwdg.de> <e56d377d0985b86be2291b64bb3c686742283dde.camel@FreeBSD.org> <6cf6a5eb00dfac8358dfcb1e1d5b69f293c3e85a.camel@FreeBSD.org> <4701f862-7a0b-afab-48fd-a62b6f5ec308@gwdg.de> <CAFDf7UKJh%2BscZ-zkmwWUNeQbVB%2B42TQSN8-m102iChi8wg0WoA@mail.gmail.com> <4cc5665f-a4ef-a4ef-226a-a9a59b29f3a0@gwdg.de> <CAFDf7ULoQfRo4S45Fpwm9Ve4h0E%2Bd82z5SYrFopmcKFLOShrdw@mail.gmail.com> <45470f65-48c3-9a18-b7bd-26ce17160afd@gwdg.de> <CAFDf7UJ90-hVX3WePtD--tHb0HEeUrq6Y0mRezZ8kYYoDQL69g@mail.gmail.com> <34ea7315-6e9b-ebe4-6be8-5e0518cf969c@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000003c642a05ffedd96e Content-Type: text/plain; charset="UTF-8" > Which version, gnu++14 or c++14, should we use here in terms of being as > universal as possible? Probably gnu++14, since clang treats both the > same ... > After some googling: C++14 (ISO standard) - Language standard released in 2014 with various improvements over C++11. GNU++14 (GCC extension) - Extension of the GCC compiler that implements C++14 with additional features specific to GCC. But it seems that upstream will know whats best. Anyway, this is a good topic to discuss because it must be a lot of failing builds because of c++17 being default on clang 16. I have another case in hands about a dependency 'graphics/libemf' (3 years old release) blocking a port of "mine", 'graphics/pstoedit'. It was easy to just use std c++14 to fix it. I'm afraid of being so easy method to fix things :) Tomorrow I will open an PR at upstream to check their opinion. Cheers, --0000000000003c642a05ffedd96e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote"><blo= ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left= :1px solid rgb(204,204,204);padding-left:1ex"> Which version, gnu++14 or c++14, should we use here in terms of being as <b= r> universal as possible? Probably gnu++14, since clang treats both the <br> same ...<br></blockquote><div><br></div><div>After some googling:<br></div>= <div><br></div><div>C++14 (ISO standard) - Language standard released in 20= 14 with various improvements over C++11.<br>GNU++14 (GCC extension) - Exten= sion of the GCC compiler that implements C++14 with additional features spe= cific to GCC.</div></div><div class=3D"gmail_quote"><br><div>But it seems t= hat upstream will know whats best.<br><br></div><div>Anyway, this is a good= topic to discuss because it must be a lot of failing builds because of c++= 17 being default on clang 16.<br><br></div><div>I have another case in hand= s about a dependency 'graphics/libemf' (3 years old release) blocki= ng a port of "mine", 'graphics/pstoedit'.<br></div><div>I= t was easy to just use std c++14 to fix it.</div><div><br></div><div>I'= m afraid of being so easy method to fix things :)<br></div><div><br></div><= div>Tomorrow I will open an PR at upstream to check their opinion.</div><di= v><br></div><div>Cheers,<br></div></div></div> --0000000000003c642a05ffedd96e--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7ULKhd%2BZMEi3920sntmy1UPygsRWkqyQ%2B1j9BWPGsNOJKQ>