search for: librarydepend

...<module> import llvmbuild File "/home/vk/opt/llvm/utils/llvm-build/llvmbuild/__init__.py", line 1, in <module> from main import main ImportError: No module named main llvm[1]: Compiling llvm-config.cpp for Debug+Asserts build llvm-config.cpp:46:10: fatal error: 'LibraryDependencies.inc' file not found #include "LibraryDependencies.inc" ^ 1 error generated. make[1]: *** [/home/vk/opt/llvm/tools/llvm-config-2/Debug+Asserts/llvm-config.o] Error 1 make[1]: Leaving directory `/home/vk/opt/llvm/tools/llvm-config-2' make: *** [all] Error 1 It looks...

...; This is an error I get when compiling Clang from SVN: > >  gmake[1]: Entering directory `/home/johann/build/llvm/tools/llvm-config' >  llvm[1]: Compiling llvm-config.cpp for Debug+Asserts build >  /opt/myrkraverk/src/llvm/tools/llvm-config/llvm-config.cpp:45:35: fatal >  error: LibraryDependencies.inc: No such file or directory >  compilation terminated. >  rm: >  /home/johann/build/llvm/tools/llvm-config/Debug+Asserts/llvm-config.d.tmp: >  No such file or directory > > I'm going by the directions here: > >  http://clang.llvm.org/get_started.html > > I...

I am getting the same problem as described here: http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-November/045769.html I've applied the patch but it doesn't help. Any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120113/2a2e2518/attachment.html>

...Mailing List > Objet : Re: [LLVMdev] RE : svn trunk comilation error > > Hi Rinaldini, > > You probably need to illustrate what your enviroment is, what revision you > checkout and how you build LLVM. I have no problem build LLVM svn here. Have > you checked tools/llvm-config/LibraryDependencies.inc is exist? > > Regards, > chenwj > > -- > Wei-Ren Chen (陳韋任) > Computer Systems Lab, Institute of Information Science, > Academia Sinica, Taiwan (R.O.C.) > Tel:886-2-2788-3799 #1667 > Homepage: http://people.cs.nctu.edu.tw/~chenwj Ok, I'll check that tomo...

...Mailing List > Objet : Re: [LLVMdev] RE : svn trunk comilation error > > Hi Rinaldini, > > You probably need to illustrate what your enviroment is, what revision you > checkout and how you build LLVM. I have no problem build LLVM svn here. Have > you checked tools/llvm-config/LibraryDependencies.inc is exist? > > Regards, > chenwj > > -- > Wei-Ren Chen (陳韋任) > Computer Systems Lab, Institute of Information Science, > Academia Sinica, Taiwan (R.O.C.) > Tel:886-2-2788-3799 #1667 > Homepage: http://people.cs.nctu.edu.tw/~chenwj Hi, I made an svn update t...

Hi Rinaldini, You probably need to illustrate what your enviroment is, what revision you checkout and how you build LLVM. I have no problem build LLVM svn here. Have you checked tools/llvm-config/LibraryDependencies.inc is exist? Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: http://people.cs.nctu.edu.tw/~chenwj

...defines, I had to solve this problem by adding a new --enable-llvm-link-llvm-dylib option in utils/llvm-build/llvmbuild/main.py to allow the LLVM_LINK_LLVM_DYLIB build to prune 'Support' from the the required library dependencies of the gtest library before the creation of tools/llvm-config/LibraryDependencies.inc. Now the LLVM_LINK_LLVM_DYLIB build contains... { "gtest", "libgtest.a", false, { } }, rather than { "gtest", "libgtest.a", false, { "support" } }, in that file. If there are specific maintainers for the llvm-build code, please add th...

Hi, Sorry I did not precise that, but I'm already doing that... I have, as you say, two different director, one for source and one for build (where I run my configure)... Cheers ________________________________________ De : 陳韋任 [chenwj at iis.sinica.edu.tw] Date d'envoi : mardi 8 mai 2012 05:21 À : Rinaldini Julien Cc: LLVM Developers Mailing List Objet : Re: [LLVMdev] svn trunk

...he backend to the configure script, so it compiles (on Linux) with LLVM 3.1. However, llvm-build fails with: llvm[0]: Constructing LLVMBuild project information. Usage: llvm-build [options] llvm-build: error: invalid target to enable: 'Foo' (not in project) and since the to be generated LibraryDependencies.inc is missing llvm-config doesn't build. Am I missing something? Regards, Mario -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJP9t/EAAoJEDv0fP6GapNteooH/A/9z/hkTzS7p3bUx6JM3j+9 xhq6owto2w0...

Hi folks, Python2 has reached end of support[0], and many core Python packages are dropping pthon 2 support[1]. This is a subject that raises periodically on this mlist, with a rather strong no in 2018 [-1] and a slow move in 2019 [-2, -3]. Even if Python is not a core build requirement, it's used during some configurations steps (e.g. in the cmake export_executable_symbols function), for

...g LLVMBuild project information. > /usr/bin/env: python: No such file or directory > llvm[1]: Building llvm-config BuildVariables.inc file. > llvm[1]: Compiling llvm-config.cpp for Debug+Asserts build > /media/data/dev/llvm/llvm/tools/llvm-config/llvm-config.cpp:45:35: fatal > error: LibraryDependencies.inc: No such file or directory > compilation terminated. > /bin/rm: cannot remove > '/media/data/dev/llvm/bin/tools/llvm-config/Debug+Asserts/llvm-config.d.tmp': > No such file or directory > make[1]: *** > [/media/data/dev/llvm/bin/tools/llvm-config/Debug+Asserts/ll...

Hello to everyone! I've configured LLVM by "../llvm/configure". But when I run "gmake", I receive compilation error: llvm[2]: Linking Debug+Asserts executable llvm-tblgen /home/poiuj/dev/llvm/build/Debug+Asserts/lib/libLLVMSupport.a(FormattedStream.o):(.debug_loc+0x2a8): undefined reference to `.LCfI21' collect2: error: ld returned 1 exit status gmake[2]: ***

Hi, I got the following error output: llvm[1]: Compiling llvm-config.cpp for Debug+Asserts build llvm-config.cpp:46:35: LibraryDependencies.inc: No such file or directory llvm-config.cpp:56: error: `AvailableComponent' was not declared in this scope llvm-config.cpp:56: error: template argument 1 is invalid llvm-config.cpp:57: error: `AvailableComponent' was not declared in this scope llvm-config.cpp:57: error: template ar...

.... I configured it with: CC=gcc CXX=g++ ./configure --enable-optimisation=yes --enable-assertions=no But I have this error: llvm[1]: Building llvm-config BuildVariables.inc file. llvm[1]: Compiling llvm-config.cpp for Release build 3.1_svn/llvm/tools/llvm-config/llvm-config.cpp:45:35: fatal error: LibraryDependencies.inc: No such file or directory compilation terminated. /bin/rm: cannot remove ‘3.1_svn/build/tools/llvm-config/Release/llvm-config.d.tmp’: No such file or directory make[1]: *** [3.1_svn/build/tools/llvm-config/Release/llvm-config.o] Error 1 make[1]: Leaving directory `3.1_svn/build/tools/llv...

...t/LLVMBuild.txt is not read it for LLVM_LINK_LLVM_DYLIB. The new patch modifies llvm_add_library() in cmake/modules/AddLLVM.cmake to manually set the LLVMBUILD_LIB_DEPS_gtest property to LLVM when LLVM_LINK_LLVM_DYLIB is set and the library name is gtest rather than read from the tools/llvm-config/LibraryDependencies.inc generated by llvm-build. Jack ps As soon as this patch lands, I'll look at trying to rework the unittests handling of the LLVMSupport dependency and see if setting that explicitly can be dropped (as it should be pulled in from the LLVMBUILD_LIB_DEPS_gtest property...

...-native-target "x86" \ --enable-targets "X86 Sparc PowerPC ARM Mips CellSPU XCore MSP430 CppBackend MBlaze NVPTX Hexagon" \ --enable-optional-components "" \ --write-library-table /home/pacifist/research_documents/LLVM_Play/using_directions/llvm/tools/llvm-config/LibraryDependencies.inc \ --write-make-fragment /home/pacifist/research_documents/LLVM_Play/using_directions/llvm/Makefile.llvmbuild Traceback (most recent call last): File "/home/pacifist/research_documents/LLVM_Play/using_directions/llvm/utils/llvm-build/llvm-build", line 3, in <module>...

The raspberry Pi2 is an armv7a chip (Cortex-A7), the first stage builds fine with the native g++ (if not a little slowly at 10+ hours), but it crashes at some point with this command line: Program arguments: /home/ben/development/llvm/3.6.0/rc2/Phase2/Release/llvmCore-3.6.0-rc2.install/bin/clang -cc1 -triple armv7-unknown-linux-gnueabihf -emit-obj -disable-free -disable-llvm-verifier

...86" \ > --enable-targets "X86 Sparc PowerPC ARM Mips CellSPU XCore MSP430 > CppBackend MBlaze NVPTX Hexagon" \ > --enable-optional-components "" \ > --write-library-table > /home/pacifist/research_documents/LLVM_Play/using_directions/llvm/tools/llvm-config/LibraryDependencies.inc > \ > --write-make-fragment > /home/pacifist/research_documents/LLVM_Play/using_directions/llvm/Makefile.llvmbuild > Traceback (most recent call last): > File > "/home/pacifist/research_documents/LLVM_Play/using_directions/llvm/utils/llvm-build/llvm-build", &...

...ull +++ b/projects/sample/.gitignore @@ -0,0 +1,4 @@ +Makefile.common +Makefile.llvm.config +config.log +config.status diff --git a/tools/llvm-config/.gitignore b/tools/llvm-config/.gitignore new file mode 100644 index 0000000..6e2f8b4 --- /dev/null +++ b/tools/llvm-config/.gitignore @@ -0,0 +1 @@ +LibraryDependencies.inc diff --git a/unittests/ExecutionEngine/JIT/.gitignore b/unittests/ExecutionEngine/JIT/.gitignore new file mode 100644 index 0000000..0f84574 --- /dev/null +++ b/unittests/ExecutionEngine/JIT/.gitignore @@ -0,0 +1,2 @@ +.dir +JITTests.exports -- 1.7.8.1.362.g5d6df.dirty