similar to: [LLVMdev] clang build fails if done in the separate object directory

can you tell what commands exactly did you use? What I usually do is: svn co llvm... mkdir llvm/tools/clang svn co llvm/tools/clang mkdir cmake-build cd cmake-build cmake ../ make Try something similar by running "../configure", it should work. On Thu, Jun 10, 2010 at 11:23 AM, Yuri <yuri at rawbw.com> wrote: > I did these steps: > * checked out llvm trunk, and clang

I've built clang+llvm in an object directory successfully, and I'm sure others have. I'd guess the problem is the symlink, so I'd give it a shot without it. Reid On Thu, Jun 10, 2010 at 7:43 AM, Diego Iastrubni <diegoiast at gmail.com> wrote: > can you tell what commands exactly did you use? > > What I usually do is: > > svn co llvm... > mkdir

On 06/10/2010 07:43, Diego Iastrubni wrote: > can you tell what commands exactly did you use? > > What I usually do is: > > svn co llvm... > mkdir llvm/tools/clang > svn co llvm/tools/clang > > mkdir cmake-build > cd cmake-build > cmake ../ > make > I did something like this: svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm svn co

Command from LLVM CFE bootstrap sequence at FreeBSD: gmake -C runtime install-bytecode terminated with error (verbose mode): --8X------------------------------------------------------- llvm[2]: Installing Debug Bytecode Archive /usr/home/wanderer/pkg/build/llvm/night/cfe/bin/../lib/libcrtend.a /usr/bin/install -c -D /usr/home/wanderer/pkg/build/llvm/obj/Debug/lib/libcrtend.bca

Current CVS version LLVM install failed for me with error: gmake[2]: Entering directory `/usr/home/wanderer/pkg/build/llvm/obj/tools/llvmc' llvm[2]: Installing Configuration Files To /home/wanderer/pkg/llvm/etc/llvm llvm[2]: Installing Debug /home/wanderer/pkg/llvm/bin/llvmc llvm[2]: Installing additional C++ configuration clones install: /cc: Permission denied gmake[2]: *** [install] Error

On 06/10/2010 08:35, Reid Kleckner wrote: > I've built clang+llvm in an object directory successfully, and I'm > sure others have. I'd guess the problem is the symlink, so I'd give > it a shot without it. > > Reid No, clang isn't built in the object directory, even without symlink Do I need to run 'mkdir llvm-objects/tools/clang' and configure there

I checked recent revisions 138624 and 138620 and both produce this log with gcc-4.6.0 on FreeBSD-8.2-STABLE amd64: gmake[2]: Entering directory `/usr/home/yuri/llvm-svn/llvm-objects/lib/CodeGen' llvm[2]: Compiling LLVMTargetMachine.cpp for Release build /usr/home/yuri/llvm-svn/llvm/lib/CodeGen/LLVMTargetMachine.cpp:253:3: error: ‘AsmStreamer’ does not name a type

Vladimir, Thanks for the note. Unfortunately, the install approach that we're using in the makefiles is a bit broken, based on Linux install program. We'll get this cleaned up soon so that it works on multiple unixes. Reid. On Thu, 2005-02-17 at 14:48, Vladimir Merzliakov wrote: > Command from LLVM CFE bootstrap sequence at FreeBSD: > gmake -C runtime install-bytecode >

In r134967 it still worked, and in r137742 it now doesn't. I used such flags: --enable-assertions --enable-shared --enable-libffi --enable-debug-runtime --enable-debug-symbols --disable-optimized Before build would create directory tools/llvm-shlib under the build tree. Now it is missing. Yuri

On 10/02/2012 13:01, Duncan Sands wrote: > > I think Chris is the right person to look at this, hopefully he will. Now 5 months passed. I updated the patch for this current revision. Can anybody review this and check in please? http://llvm.org/bugs/show_bug.cgi?id=13163 Yuri

AFAICT these are valid errors. Getting an error on the 'make install' for LLVM :- make[2]: Entering directory `/usr/build/llvm/tools/llvm-ar' llvm[2]: Installing Debug /usr/llvm/bin/llvm-ar /usr/bin/install: target `/usr/llvm/bin/llvm-ar' is not a directory make[2]: *** [/usr/llvm/bin/llvm-ar] Error 1 make[2]: Leaving directory `/usr/build/llvm/tools/llvm-ar' make[1]: ***

This function (understandably) takes quite a long time, because it has to go through each function in module and write its binary. But it probably can be parallelized if different threads would write binaries separately, and then merge them together. Is this implemented or planned? Yuri

On 02/02/2014 01:48, David Chisnall wrote: > In most calling conventions, this is a callee-save register. After its last use, the register allocator may reuse that register. On x86 and ARM, the register that contains this is also (usually) the register used for But the rule "after the last use, the register allocator may reuse it" is also introduced by llvm, since register

I have a couple of questions regarding openssh.spec and the rpm that gets generated from it. I am using 2.3.0p1 1. Why is openssl a prereq? openssh statically links to openssl during build by default (rightfully so, you don't want your security library a shared object if possible) 2. I don't understand the following line in the spec file during the install step (it makes it not build for

How can I copy the value from another BB? PHI instruction with one argument would fit, but it requires that all arguments are in immediately preceding BBs. Yuri

Jeffrey Yasskin wrote: >> Would you try the patch at >> http://codereview.appspot.com/download/issue968046_1.diff? It should >> make the BSDs fall into the same path as Linux, and since you use gnu >> ld, that should work for you. >> > > Ping? > Sorry for the delay. Here is what I am getting after applying the patch: gmake[2]: Leaving directory

I can't reproduce these on GNU-Linux/x86. What platform are you on? Reid. On Sat, 2005-05-14 at 16:50 +0100, Aaron Gray wrote: > AFAICT these are valid errors. > > Getting an error on the 'make install' for LLVM :- > > > make[2]: Entering directory `/usr/build/llvm/tools/llvm-ar' > llvm[2]: Installing Debug /usr/llvm/bin/llvm-ar > /usr/bin/install:

Yuri, on which host? 2011/8/17 Yuri <yuri at rawbw.com>: > In r134967 it still worked, and in r137742 it now doesn't. > I used such flags: --enable-assertions --enable-shared --enable-libffi > --enable-debug-runtime --enable-debug-symbols --disable-optimized > > Before build would create directory tools/llvm-shlib under the build > tree. Now it is missing. In my

On Apr 17, 2013, at 7:26 PM, Yuri <yuri at rawbw.com> wrote: > On 10/02/2012 13:01, Duncan Sands wrote: >> >> I think Chris is the right person to look at this, hopefully he will. > > Now 5 months passed. I updated the patch for this current revision. > Can anybody review this and check in please? > > http://llvm.org/bugs/show_bug.cgi?id=13163 >

I think my patch fell through the cracks: http://llvm.org/bugs/show_bug.cgi?id=13163 Could anybody please check it in? Thanks, Yuri