Date: Fri, 20 Apr 2018 19:07:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 227659] [PATCH] fix to build WITH_GCC=yes when using an external compiler that supports c++11 Message-ID: <bug-227659-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227659 Bug ID: 227659 Summary: [PATCH] fix to build WITH_GCC=3Dyes when using an external compiler that supports c++11 Product: Base System Version: 11.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: conf Assignee: bugs@FreeBSD.org Reporter: kennethsalerno@yahoo.com Created attachment 192687 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D192687&action= =3Dedit patch to allow user to select WITH_GCC=3Dyes when building with an external compiler that supports c++11 We should not explicitly force MK_GCC to always be set to "no" when using a modern gcc XCC (that supports c++11). Seems this should be left up to the u= ser (WITH_, WITHOUT_). I agree with always setting MK_GNUCXX to "no" because it doesn't even compi= le (missing bits/c++config.h), but there are cases where you want a system compiler installed when building with an XCC, but don't want that system compiler to be clang. One such example is the system /usr/bin/clang (LLVM 4.0.0) segfaults in powerpc64 linking ports-mgmt/pkg. So while the first and last task of /usr/bin/gcc is to just build lang/gcc6, you can't get very far if /usr/bin= /cc is clang. The system gcc 4.2.1 on powerpc64 can successfully build ports-mgmt/pkg: /usr/local/sbin/pkg: ELF 64-bit MSB executable, 64-bit PowerPC or cisco 750= 0, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, FreeBSD-style, for FreeBSD 11.1, stripped --=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>