On 04/13/17 17:51, Joerg Sonnenberger wrote:
On Thu, Apr 13, 2017 at 04:05:53PM +0100, Sevan Janiyan wrote:We're starting to see applications which specifically need a compiler with C++ 11 support in order to build correctly e.g. textproc/icu & net/powerdns-recursor. The patch below adds a minimal set of changes similar to the c99 option which results in GCC_REQD being set to 4.8 & -std=c++11 being handled by the wrapppers. http://www.netbsd.org/~sevan/patch-pkgsrc-cplusplus11.txt Any comments?As I said the last time this was brought up -- I don't think this actually solves the problem and in many cases will make it much worse. I.e. it is much easier with this change to end up with a mix of different C++ compilers and all the associated major problems. Joerg
Does it necessarily have to allow mixing tool chains? In my view, it could mean that a CentOS installation would use GCC4X for all c++11 code now, and at some future date, we could switch to GCC5 or clang for everything, requiring packages to be recompiled, but not modified. I Think NetBSD6 could probably use a similar approach.
Systems with their own proprietary compilers may have to go a different route, of course, due to ABI differences.
We regularly mix clang and GCC object code in FreeBSD ports, with
very few issues. I don't know how much effort, if any, is
required to maintain ABI compatibility, though.
-- Earth is a beta site.