similar to: [LLVMdev] JIT: LibDeps.txt does not include all dependencies

SevenThunders wrote: > > > Someone reported this earlier but the situation remains unchanged. > > -Matt > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > Thanks for getting it back up so quickly. Now if I

Hello everyone, I've run across a problem building LLVM 2.7 with Mingw on Win7. When I try make VERBOSE=1, it churns away happily for a while and then produces: /c/Perl/bin/perl /c/Programs32/llvm-2.7/utils/GenLibDeps.pl -flat /c/Programs 32/llvm-2.7/obj/Release/lib "/mingw/bin/nm" > /c/Programs32/llvm-2.7/obj/tools/ llvm-config/LibDeps.txt.tmp 'c:' is not recognized as

My 7 zip file manager says that the mingw binary is corrupt for llvm 1.9. I suppose that means that those of us running windows have no hope of getting llvm right now? Someone reported this earlier but the situation remains unchanged. -Matt

Hi, I'm trying to build clang under MingW, but I'm getting a number of errors. Could anyone provide some hints as to what you had to do? I got some tips from http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx, but using the newer packages, as it's a bit old. The ./configure seems to run without errors. The first run of make aborts with errors like:

Kenneth Boyd <zaimoni at zaimoni.com> writes: [snip] >> That does not really surprise me about CMake, but then mingw is not a >> primary compiler on Windows, more so is VC++ or Intel, either way a >> bug should be submitted to the CMake devs. > I do not want to troll the CMake devteam, so I will not submit the bug > report without a full-blown patch. The CMake

Óscar Fuentes wrote: > The CMake devteam is very responsive about bug reports. They will > certainly appreciate your bug report, no patch required. > I still don't think I have enough detail to file a bug report (not sure exactly what they need to know about my system configuration to make it testable). I did go ahead (just now) and ask the main CMake mailing list which files I

$ make update ...snip... Updated to revision 69967. $ ENABLE_OPTIMIZED=1 make ...snip... llvm[1]: Regenerating LibDeps.txt.tmp llvm[1]: Checking for cyclic dependencies between LLVM libraries. find-cycles.pl: Circular dependency between *.a files: find-cycles.pl: libLLVMAsmPrinter.a libLLVMCodeGen.a libLLVMSelectionDAG.a llvm[1]: Building llvm-config script. cat:

Reid added some nice inter-library dependency data to utils/llvm- config/LibDeps.txt. There are three sets of circular dependencies between LLVM libraries. If you use any library from one of these sets, you may need to pull in the rest: LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a LLVMSparcV9.o LLVMSparcV9InstrSched.o

[ 73%] Regenerating /Users/samuraicrow/Documents/workspace/llvm-trunk-build/tools/llvm-config/LibDeps.txt.tmp [ 73%] Updating /Users/samuraicrow/Documents/workspace/llvm-trunk-build/tools/llvm-config/LibDeps.txt if necessary... [ 73%] Checking for cyclic dependencies between LLVM libraries. find-cycles.pl: Circular dependency between *.a files: find-cycles.pl: libLLVMAsmPrinter.a

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > > ..... >> From the existence of the dependency-tracker scripts, it obviously was >> a problem for autoconf as well. >> > > This seems a different issue, but are those dependency-tracker scripts > for tracking dependencies among cpp files and its headers? CMake gives >

Forgot to hit "Reply All." -- John T. -------------- next part -------------- An embedded message was scrubbed... From: John Criswell <criswell at cs.uiuc.edu> Subject: Re: using dsa Date: Tue, 06 Mar 2007 09:53:43 -0600 Size: 3103 URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070306/ef7c2f29/attachment.mht>

Hi Eric, Its definitely amusing :) About the only thing I can suggest are: 1. Combine LLVMSparc*.o into one LLVMSparc.a. That work is already happening with the new Sparc backend that is being developed. Should be out in 1.7 (Chris?) 2. Combine the JIT/Interpreter/ExecutionEngine into one .a I don't know enough about the codegen/target/analysis/ipa stuff to be able to make any

Samuel Crow <samuraileumas at yahoo.com> writes: > [ 73%] Regenerating > /Users/samuraicrow/Documents/workspace/llvm-trunk-build/tools/llvm-config/LibDeps.txt.tmp > > [ 73%] Updating > /Users/samuraicrow/Documents/workspace/llvm-trunk-build/tools/llvm-config/LibDeps.txt > if necessary... > [ 73%] Checking for cyclic dependencies between LLVM libraries. >

What versions of llvm and llvm-poolalloc should I check out of cvs, in order to use DSA? In a previous post John Criswell suggested checking llvm and llvm-poolalloc out of cvs using the -r release_19 flag. However, there were several post later that said that changes should not be made to the release_19 branch. At any rate, I've not seen any update on which versions of llvm and

I am using LLVM as back end for my compiler, and until now I have used my own CMake build system for LLVM. But now LLVM has a CMake build system of its own, so when upgrading my LLVM version I decided to move to the 'official' one. It's not an easy transition, the build fails. I already found one bug: in some files the variable CMAKE_SOURCE_DIR is used for the LLVM top-level source

I am unable to install gems on my dreamhost server since it''s just shared hosting. I tried unpacking the ferret gem into vendor/ferret, but to no avail. Also how would I recompile the C extensions for the new platform? Any ideas would be greatly appreciated. Cheers, Simon -- Posted via http://www.ruby-forum.com/.

I updated dsa to mainline cvs. Poolalloc is broken, however. On Mar 6, 2007, at 3:39 AM, Ryan M. Lefever wrote: > What versions of llvm and llvm-poolalloc should I check out of cvs, in > order to use DSA? In a previous post John Criswell suggested checking > llvm and llvm-poolalloc out of cvs using the -r release_19 flag. > However, there were several post later that said that

Kenneth Boyd <zaimoni at zaimoni.com> writes: >> 1) either CMake becomes the de facto standard for LLVM, deprecating >> autoconf&&gmake and thus requiring the developers to update the >> CMakeLists.txt files to compile their sources... >> > Sorry, but this is a noticeable obstacle for CMake becoming the de-facto > standard for LLVM. Writing a new

make[1]: Entering directory `/home/hkultala26/src/llvm-trunk/llvm/tools/llvm-config' llvm[1]: Regenerating LibDeps.txt.tmp llvm[1]: Checking for cyclic dependencies between LLVM libraries. find-cycles.pl: Circular dependency between *.a files: find-cycles.pl: libLLVMPTXAsmPrinter.a libLLVMPTXCodeGen.a libLLVMPTXDesc.a llvm[1]: Building llvm-config script. cat:

Hello Anton Thu, 3 Aug 2006 15:06:56 +0400 you wrote: > here it is in the attachment :) Ok. Could you also send LibDeps.txt file? It should be in /obj/tools/llvm-config directory -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.