search for: llvm_cflags

.... > When we build Icedtea shark JIT we use the llvm-config version to make the icedtea code compatible with api changes in llvm. I belive you are trying to do something similarwith LDC. This can be done without changing the llvm codebase. I suggest the following: add to the LDC configure. LLVM_CFLAGS="$LLVM_CFLAGS -DLLVM_VERSION=`$LLVM_CONFIG --version | sed 's/\.//;s/svn.*//'`" this will take the llvm-config --version output and truncates the versionnumber from 2.6svn to 26 now the LLVM_VERSION can be used in your source code like this: #if LLVM_VERSION >= 26 /*llvm 2....

...T we use the llvm-config version to make > the icedtea code compatible with api changes in llvm. > I belive you are trying to do something similarwith LDC. This can be > done without changing the llvm codebase. > > I suggest the following: > add to the LDC configure. > > LLVM_CFLAGS="$LLVM_CFLAGS -DLLVM_VERSION=`$LLVM_CONFIG --version | sed 's/\.//;s/svn.*//'`" > > this will take the llvm-config --version output and truncates the versionnumber from > > 2.6svn to 26 > > now the LLVM_VERSION can be used in your source code like this: >...

Benjamin Kramer wrote: > At the moment llvm-config outputs "2.6svn" if llvm is build from trunk > > $ llvm-config --version > 2.6svn > > Some external projects (built out-of-tree) need to know which revision > of llvm is installed. LDC currently asks llvm-config --src-root for the > source directory and then parses svn info's output to get the revision

...on to make >> the icedtea code compatible with api changes in llvm. >> I belive you are trying to do something similarwith LDC. This can be >> done without changing the llvm codebase. >> >> I suggest the following: >> add to the LDC configure. >> >> LLVM_CFLAGS="$LLVM_CFLAGS -DLLVM_VERSION=`$LLVM_CONFIG --version | sed 's/\.//;s/svn.*//'`" >> >> this will take the llvm-config --version output and truncates the versionnumber from >> >> 2.6svn to 26 >> >> now the LLVM_VERSION can be used in your source c...

At the moment llvm-config outputs "2.6svn" if llvm is build from trunk $ llvm-config --version 2.6svn Some external projects (built out-of-tree) need to know which revision of llvm is installed. LDC currently asks llvm-config --src-root for the source directory and then parses svn info's output to get the revision number. This requires the user to keep the llvm source tree

...tools/llvm-config/CMakeLists.txt llvm-project/llvm/tools/llvm-config/CMakeLists.txt --- llvm-project-10.0.1rc1/llvm/tools/llvm-config/CMakeLists.txt 2020-05-19 21:16:37.000000000 +0200 +++ llvm-project/llvm/tools/llvm-config/CMakeLists.txt 2020-05-20 18:28:03.793999462 +0200 @@ -49,7 +49,7 @@ set(LLVM_CFLAGS "${LLVM_C_STD_FLAG} ${LL set(LLVM_CXXFLAGS "${CMAKE_CXX${CMAKE_CXX_STANDARD}_STANDARD_COMPILE_OPTION} ${LLVM_CXX_STDLIB_FLAG} ${COMPILE_FLAGS} ${LLVM_DEFINITIONS}") set(LLVM_BUILD_SYSTEM cmake) set(LLVM_HAS_RTTI ${LLVM_CONFIG_HAS_RTTI}) -set(LLVM_DYLIB_VERSION "${LLVM_VERSION...

.../tools/llvm-config/CMakeLists.txt > > --- llvm-project-10.0.1rc1/llvm/tools/llvm-config/CMakeLists.txt > > 2020-05-19 21:16:37.000000000 +0200 > > +++ llvm-project/llvm/tools/llvm-config/CMakeLists.txt 2020-05-20 > > 18:28:03.793999462 +0200 > > @@ -49,7 +49,7 @@ set(LLVM_CFLAGS "${LLVM_C_STD_FLAG} ${LL > > set(LLVM_CXXFLAGS > > "${CMAKE_CXX${CMAKE_CXX_STANDARD}_STANDARD_COMPILE_OPTION} > > ${LLVM_CXX_STDLIB_FLAG} ${COMPILE_FLAGS} ${LLVM_DEFINITIONS}") > > set(LLVM_BUILD_SYSTEM cmake) > > set(LLVM_HAS_RTTI ${LLVM_CONFIG_HAS_R...

Try make VERBOSE=1 first. Perhaps it'll tell us something. Evan On Feb 19, 2008, at 4:19 PM, Tobias Oberstein wrote: > Hello, > > I'd like to do some initial experiments with LLVM on embedded ARM > (Nokia N800), but ran into a build issue. Could s.o. give me a tip? > > Thx alot, > Tobias > > P.S.: just as sidenote, LLVM 2.2 builds cleanly on GCC 4.2.3 / Linux.

Hi Tom, thanks and congrats for LLVM 10.0.1-rc1 release. [1] shows 2 assets. 10.0.0 RCs had a lot of more assets. I am missing the llvm-project-10.0.1rc1.tar.xz tarball. Will you provide them later or is there a new development/workflow decision I do not know of? BTW, the source zip and tar.gz tarballs show no sizes. I am using Mobile LTE/UMTS to download stuff from the Internet. For now I

Hello, I'd like to do some initial experiments with LLVM on embedded ARM (Nokia N800), but ran into a build issue. Could s.o. give me a tip? Thx alot, Tobias P.S.: just as sidenote, LLVM 2.2 builds cleanly on GCC 4.2.3 / Linux. === I'm building on Ubuntu/Scratchbox/ARMEL using GCC 3.4.4 (CodeSourcery ARM 2005q3-2) using ./configure --prefix=$HOME/local/llvm-2.2 --enable-jit

..._GNU_SOURCE -DUSE_SSE41 -DDEBUG -DUSE_X86_64_ASM -DHAVE_XLOCALE_H -DHAVE_STRTOF -DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DLLVM_VERSION_PATCH=0 LLVM_CFLAGS: -I/opt/llvm-toolchain-3.6.0rc2/include -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS LLVM_CXXFLAGS: -I/opt/llvm-toolchain-3.6.0rc2/include -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -std=c++11 -fno-rtti...