Date: Wed, 27 May 2015 09:30:15 +0000 From: bugzilla-noreply@freebsd.org To: office@FreeBSD.org Subject: [Bug 200236] [maintainer][patch] games/wesnoth: fix for some FreeBSD 10.1 builds Message-ID: <bug-200236-25061-23o1F1xVkA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200236-25061@https.bugs.freebsd.org/bugzilla/> References: <bug-200236-25061@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=200236 Don Lewis <truckman@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |truckman@FreeBSD.org --- Comment #30 from Don Lewis <truckman@FreeBSD.org> --- (In reply to John Marino from comment #18) There is no guarantee that clang is present on 9, 10, and 11. This is true by default on some of the tier 2 platforms according to src.conf(5), and on i386 or amd64 the end user might have added WITHOUT_CLANG to his /etc/src.conf. If using the base version of clang if present is OK then the cleanest solution might be to add USES=compiler:cwhatever to the Makefile. Since boost is used by this port, and boost is built with the default c++ compiler from base, it gets tricky. On FreeBSD 9, many of the USES=compiler options will use clang as the compiler and result in fatal libstdc++ vs. libc++ conflicts. USES=compiler:c++11-lib will generally do the right thing here because it will use the ports version of gcc if COMPILER_TYPE != clang. BTW, the COMPILER_VERSION check in ".if ${COMPILER_TYPE} == gcc && ${COMPILER_VERSION} <= 42" is pretty useless because it is always true when COMPILER_TYPE is gcc. -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200236-25061-23o1F1xVkA>