search for: build_llvm

On Sat, 3 Jun 2017 16:04:57 -0700 Tim Northover <t.p.northover at gmail.com> wrote: [snip] > I think you should be able to fix it by changing the > compiler-rt/lib/xray/test/CMakeLists.txt. If you find the > "add_compiler_rt_test" call and move "-lstdc++" to the end, just after > "-lrt" it should work. Thanks, Tim. I don't see "-lrt":

...t/openmp/tags/RELEASE_400/final/ openmp svn co http://llvm.org/svn/llvm-project/libcxx/tags/RELEASE_400/final/ libcxx svn co http://llvm.org/svn/llvm-project/libcxxabi/tags/RELEASE_400/final/ libcxxabi svn co http://llvm.org/svn/llvm-project/test-suite/tags/RELEASE_400/final/ test-suite mkdir $BASE/build_llvm cd $BASE/build_llvm cmake3 -G Ninja -DCMAKE_INSTALL_PREFIX=$HOME/.local/llvm \ -DCMAKE_BUILD_TYPE=Release $BASE/llvm_Rel400 ninja-build ninja-build check-all 2>&1 | tee check.log ----- The last few lines of the log file look like this: [112/475] cd /home/hanzer/build/build_llvm/projects...

...VE_CONFIG_H -Wno-unused -DTARGET_NAME=\"i686-pc-linux-gnu\" -I. -I. -I../../../llvm-gcc/gcc -I../../../llvm-gcc/gcc/. -I../../../llvm-gcc/gcc/../include -I../../../llvm-gcc/gcc/../libcpp/include -I../../../llvm-gcc/gcc/../libdecnumber -I../libdecnumber -I/home/mcuelenaere/llvm_build/build_llvm-gcc/obj/../../build_llvm//include -I//include -DENABLE_LLVM -I/home/mcuelenaere/llvm_build/build_llvm/include -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -I. -I. -I../../../llvm-gcc/gcc -I../../../llvm-gcc/gcc/. -I../../../llvm-gcc/gcc/../include -I../../../llvm-gcc/gcc/....

...etc. instead of a fully qualified name with the triple as prefix) or there's something broken in the host tools installation. -Jim On Jul 11, 2011, at 9:03 PM, Whee Cheng Ong wrote: > Hi Jim > > Thanks for your suggestion of building llvm in a dedicated directory. > However, it (build_llvm) does not work, and for some reasons, it > appear to re-run configure when make is called, using different host > and target configurations: > fusion at fusion-desktop:~/Desktop/Samsung/OpenCL/src/build_llvm$ make > checking build system type... i686-pc-linux-gnu > checking host syst...

Hello I am new to LLVM and would like to cross-compile LLVM 2.9 on x86 (Ubuntu) to ARM using Code Sourcery LIte toolchain for ARM EABI (2011.03-41). This is the command I used to configure: ./configure --build=i686-pc-linux-gnu --host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi followed by: make -C llvm.2.9 ENABLE_OPTIMIZED=0 I encountered the following errors: configure:error:

Currently, to get LLVM to build "Apple-style," it's necessary to copy two files (utils/buildit/GNUmakefile and utils/buildit/build_llvm) into the top-level directory. This is generally a PITA inside of Apple. (I'll spare you the gory details. :-) I'd like to fix this for Apple, and I want to avoid compromising anybody else's build system. I've never used CMAKE, so I would be very grateful if a Windows/C...

On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: > Currently, to get LLVM to build "Apple-style," it's necessary to > copy two files (utils/buildit/GNUmakefile and utils/buildit/ > build_llvm) into the top-level directory. Why not: $ RC_ARCHS="x86" make echo Apple Build. Apple Build. $ make echo Standard Build Standard Build $ cat Makefile ifneq ($(RC_ARCHS),) include Makefile.apple else all: echo Standard Build endif mrs $ cat Makefile.apple all: echo Apple Build. It lea...

...e: > >> checking for armv7-apple-darwin-clang... no >> checking for armv7-apple-darwin-llvm-gcc... no >> checking for armv7-apple-darwin-gcc... no > > It's because you don't have a compiler around that targets arm by default. Exactly right. You can look in the build_llvm script for an ugly-but-effective way to work around that on Darwin. -Jim

On Oct 8, 2009, at 5:18 PM, Mike Stump wrote: > On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: >> Currently, to get LLVM to build "Apple-style," it's necessary to >> copy two files (utils/buildit/GNUmakefile and utils/buildit/ >> build_llvm) into the top-level directory. > > Why not: > > $ RC_ARCHS="x86" make > echo Apple Build. > Apple Build. > $ make > echo Standard Build > Standard Build > $ cat Makefile > ifneq ($(RC_ARCHS),) > include Makefile.apple > else > all: > echo Stan...

...-r-- 1 wearefam wearefam 14295 Feb 24 15:53 logs/configure-log_llvm-toolchain-3.8.0rc3.txt $ cat disc-usage_llvm-toolchain-3.8.0rc3.txt 315 llvm 1464 llvm-build 864 /opt/llvm-toolchain-3.8.0rc3 - EOT - -------------- next part -------------- A non-text attachment was scrubbed... Name: build_llvm-toolchain_clang-cmake-ninja.sh Type: application/x-sh Size: 3058 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160226/44a815cc/attachment.sh> -------------- next part -------------- A non-text attachment was scrubbed... Name: build_llvm-toolchain_gcc-m...

...; > On Oct 8, 2009, at 5:18 PM, Mike Stump wrote: > >> On Oct 8, 2009, at 4:52 PM, Stuart Hastings wrote: >>> Currently, to get LLVM to build "Apple-style," it's necessary to >>> copy two files (utils/buildit/GNUmakefile and utils/buildit/ >>> build_llvm) into the top-level directory. >> >> Why not: >> >> $ RC_ARCHS="x86" make >> echo Apple Build. >> Apple Build. >> $ make >> echo Standard Build >> Standard Build >> $ cat Makefile >> ifneq ($(RC_ARCHS),) >> include Ma...

...(incidentally, I really wish it was!), I had to modify the definition of the classes and functions that I need in order to have something like: class LLVM_EXPORT Compilation { . }; rather than class Compilation { . }; with LLVM_EXPORT being defined as: #ifdef _WIN32 #ifdef BUILD_LLVM #define LLVM_EXPORT __declspec(dllexport) #else #define LLVM_EXPORT __declspec(dllimport) #endif #else #define LLVM_EXPORT #endif Now, as I mentioned before, that approach works fine up to LLVM+Clang 3.5.1, but it fails with LLVM+Clang 3.6. Not for all the cla...

...I was playing with LLVM pass. I changed the lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make install the pass and use an example test1.c to see whether it works or not. When I run example using the following command: clang -emit-llvm test1.c -c -o test1.bc opt -load ../build_llvm/Debug+Asserts/lib/LLVMHello.so -hello < test1.bc > /dev/null It shows the following error: Unknown instruction type encountered! UNREACHABLE executed at include/llvm/InstVisitor.h:120! 0 opt 0x00000000014190b6 llvm::sys::PrintStackTrace(_IO_FILE*) + 38 1 opt 0x0000...

...> ( For testing RCs I tend to use slow build - one single (c)make job. ) > > My build-script and configure-log are attached. > > Thanks. > > Regards, > - Sedat - > > > [1] http://llvm.org/docs/CMake.html > <configure-log_llvm-toolchain-3.8.0rc3.txt><build_llvm-toolchain.sh>_______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

...L=OFF # #### TRYOUT #4: TABLEGEN # LLVM_OPTIMIZED_TABLEGEN:BOOL=OFF # ##### END *** SECTION WILL BE DELETED *** Thanks for any help and ideas. Regards, - Sedat - [1] http://llvm.org/releases/3.8.0/docs/CMake.html -------------- next part -------------- A non-text attachment was scrubbed... Name: build_llvm-toolchain_clang-cmake-ninja.sh Type: application/x-sh Size: 4638 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160312/6249bc5d/attachment.sh>

...pass. I changed the > lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make > install the pass and use an example test1.c to see whether it works or > not. When I run example using the following command: > clang -emit-llvm test1.c -c -o test1.bc > opt -load ../build_llvm/Debug+Asserts/lib/LLVMHello.so -hello < test1.bc > > /dev/null > > It shows the following error: > > Unknown instruction type encountered! > UNREACHABLE executed at include/llvm/InstVisitor.h:120! The error message here means that the type of instruction -- alloca, add, s...

...;> >>> My build-script and configure-log are attached. >>> >>> Thanks. >>> >>> Regards, >>> - Sedat - >>> >>> >>> [1] http://llvm.org/docs/CMake.html >>> <configure-log_llvm-toolchain-3.8.0rc3.txt><build_llvm-toolchain.sh>_______________________________________________ >>> LLVM Developers mailing list >>> llvm-dev at lists.llvm.org >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > _______________________________________________ > LLVM Developers m...

...ow build - one single (c)make job. ) >> >> My build-script and configure-log are attached. >> >> Thanks. >> >> Regards, >> - Sedat - >> >> >> [1] http://llvm.org/docs/CMake.html >> <configure-log_llvm-toolchain-3.8.0rc3.txt><build_llvm-toolchain.sh>_______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >

...> > > > Not having to manually track down a bunch of dependencies before building > is a feature. Not having to have an internet connection at build time (if > we were to script the getting of the custom CMake) is a feature. Being able > to just call cmake instead of using some build_llvm.sh that (probably > poorly) wraps cmake and downloads the correct version is a feature. Being > able to use CMake that is distributed with visual studio so that invoking > cmake from the developer powershell just works without fiddling with PATHs > is a feature. Not having to install ms...

...S_NO_NESTED_ANON_TYPES_FLAG -- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG - Failed -- Configuring done -- Generating done -- Build files have been written to: /home/wearefam/src/llvm-toolchain/llvm-build -------------- next part -------------- A non-text attachment was scrubbed... Name: build_llvm-toolchain.sh Type: application/x-sh Size: 3786 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160225/0393e162/attachment.sh>