lldb-git: polly-git: libunwind-git: Reduce diff with upstream

This commit is contained in:
Kamil Rytarowski 2017-05-06 03:32:52 +02:00
parent 791668b49f
commit addb002fb9
4 changed files with 4 additions and 4 deletions

View file

@ -15,7 +15,7 @@ WRKSRC= ${WRKDIR}/${PKGBASE}
CONFIGURE_DIRS= ${WRKDIR}/build CONFIGURE_DIRS= ${WRKDIR}/build
USE_TOOLS+= pax USE_TOOLS+= pax
USE_LANGUAGES= c c++ USE_LANGUAGES= c c++11
USE_CMAKE= yes USE_CMAKE= yes
GCC_REQD+= 4.8 GCC_REQD+= 4.8

View file

@ -17,7 +17,7 @@ WRKSRC= ${WRKDIR}/${PKGBASE}
CONFIGURE_DIRS= ${WRKDIR}/build CONFIGURE_DIRS= ${WRKDIR}/build
CMAKE_ARG_PATH= ${WRKSRC} CMAKE_ARG_PATH= ${WRKSRC}
USE_LANGUAGES= c c++ USE_LANGUAGES= c c++11
USE_CMAKE= yes USE_CMAKE= yes
GCC_REQD+= 4.8 GCC_REQD+= 4.8
PY_PATCHPLIST= yes PY_PATCHPLIST= yes

View file

@ -9,4 +9,4 @@ area of automatic GPU code generation.
For many users, however, it's not the existing optimizations in Polly that are 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 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 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.

View file

@ -15,7 +15,7 @@ WRKSRC= ${WRKDIR}/${PKGBASE}
CONFIGURE_DIRS= ${WRKDIR}/build CONFIGURE_DIRS= ${WRKDIR}/build
CMAKE_ARG_PATH= ${WRKSRC} CMAKE_ARG_PATH= ${WRKSRC}
USE_LANGUAGES= c c++ USE_LANGUAGES= c c++11
USE_CMAKE= yes USE_CMAKE= yes
GCC_REQD+= 4.8 GCC_REQD+= 4.8