diff --git a/libunwind-git/Makefile b/libunwind-git/Makefile
index ac2d8166b5..7f9a2a2ec2 100644
--- a/libunwind-git/Makefile
+++ b/libunwind-git/Makefile
@@ -15,7 +15,7 @@ WRKSRC=			${WRKDIR}/${PKGBASE}
 CONFIGURE_DIRS=		${WRKDIR}/build
 
 USE_TOOLS+=		pax
-USE_LANGUAGES=		c c++
+USE_LANGUAGES=		c c++11
 USE_CMAKE=		yes
 GCC_REQD+=		4.8
 
diff --git a/lldb-git/Makefile b/lldb-git/Makefile
index 29bb247633..5321cdf768 100644
--- a/lldb-git/Makefile
+++ b/lldb-git/Makefile
@@ -17,7 +17,7 @@ WRKSRC=			${WRKDIR}/${PKGBASE}
 CONFIGURE_DIRS=		${WRKDIR}/build
 CMAKE_ARG_PATH=		${WRKSRC}
 
-USE_LANGUAGES=		c c++
+USE_LANGUAGES=		c c++11
 USE_CMAKE=		yes
 GCC_REQD+=		4.8
 PY_PATCHPLIST=		yes
diff --git a/polly-git/DESCR b/polly-git/DESCR
index 440b9fe3e9..6750ff4476 100644
--- a/polly-git/DESCR
+++ b/polly-git/DESCR
@@ -9,4 +9,4 @@ area of automatic GPU code generation.
 For many users, however, it's not the existing optimizations in Polly that are
 of most interest, but the new analyses and optimizations enabled by the Polly
 infrastructure. At polyhedral.info you can get an idea of what has already been
-done and what is possible in the context of polyhedral compilation. 
+done and what is possible in the context of polyhedral compilation.
diff --git a/polly-git/Makefile b/polly-git/Makefile
index 9f4161bade..2e55a126a2 100644
--- a/polly-git/Makefile
+++ b/polly-git/Makefile
@@ -15,7 +15,7 @@ WRKSRC=			${WRKDIR}/${PKGBASE}
 CONFIGURE_DIRS=		${WRKDIR}/build
 CMAKE_ARG_PATH=		${WRKSRC}
 
-USE_LANGUAGES=		c c++
+USE_LANGUAGES=		c c++11
 USE_CMAKE=		yes
 GCC_REQD+=		4.8