Date: Sat, 28 Apr 2018 22:05:42 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 227659] [PATCH] src.opts.mk: fix to build WITH_GCC=yes when using an external compiler that supports c++11 Message-ID: <bug-227659-227-8sj7UARlAP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227659-227@https.bugs.freebsd.org/bugzilla/> References: <bug-227659-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227659 --- Comment #1 from Kenneth Salerno <kennethsalerno@yahoo.com> --- On second thought, it is a real hassle to get g++ to use libc++... And I ju= st could not get out of include hell building libstdc++ with devel/powerpc64-g= cc (6.3.0) as my external compiler - the same exact parameters (isystem and sysroot etc.) would compile with no complaints with clang++ (4.0.0) but g++ (6.3.0) on the other hand would choke on __is_empty traits. I even checked = with -E (-o *.i) and diffed the results between g++ and clang++ and they were al= most identical! I reverted this patch and now trying to use devel/llvm60 (yes, I'm caving i= n) as my external compiler and see if I can get past the ports-mgmt/pkg segfau= lt with the system compiler under ppc64. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227659-227-8sj7UARlAP>