similar to: [LLVMdev] Building the llvm runtime: 'Can't destroy file:Theprocess cannot access the fi

Hi Reid, I don't think I've initiated a parallel build by this command: ------------------------ make TOOLLINKOPTSB+=-ldbghelp TOOLLINKOPTSB+=-lpsapi LDFLAGS+='-Wl,--no-keep-memory' -r VERBOSE=1 ------------------------ Henrik. >From: Reid Spencer Date: Wed, 26 Jan 2005 12:05:51 -0800 > >It looks like what you're getting is a sharing violation. Although, I

It looks like what you're getting is a sharing violation. Although, I don't understand why. The llvm-ar.exe when its building an archive file always builds it in a temporary. Only when that is complete does it remove the old one and rename the temporary. Perhaps this is a result of doing parallel build and the "lib3.tmp" file (that name looks wrong to me) is being accessed by

Hi Jeff and others, When building the llvm runtime, I always get this error message: 'Can't destroy file: The process cannot access the file because it is being used by another process.' The file is destoyed anyway. I think that the the real error is the path for the file (*/\file.tmp). However, I can't find the bug in the source. Do you have any clue?:

>From: Jeff Cohen Date: Wed, 26 Jan 2005 19:47:44 -0800 > >Fixed. Yes, now it isn't the path. I've recorded this trace: ------------------------- llvm[3]: Building Debug Bytecode Archive libc.bca /bin/rm -f /C/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca /C/projects/build/MinGW/llvm-4-1/Debug/bin/llvm-ar rcsf /C/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca

The mapped files weren't being closed at all; they were only being unmapped. It's now fixed. Reid Spencer wrote: >On Thu, 2005-01-27 at 13:16, Henrik Bach wrote: > > >>c:\projects\build\MinGW\llvm-4-1\Debug\bin\llvm-ar.exe: >>c:/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca-000000: Can't destroy >>file (hb:2): The process cannot access the file

On Thu, 2005-01-27 at 13:16, Henrik Bach wrote: > c:\projects\build\MinGW\llvm-4-1\Debug\bin\llvm-ar.exe: > c:/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca-000000: Can't destroy > file (hb:2): The process cannot access the file because it is being used by > another process. > make[3]: *** [/C/projects/build/MinGW/llvm-4-1/Debug/lib/libc.bca] Error 2 >

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

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 >

Hello, Henrik. You wrote Thursday, January 27, 2005, 12:17:21 AM: HB> I've attached an output. Seems to be some problems with path handling. I think the '/\' in the error line is an indicator, that something went wrong with sys::Path. Maybe, you'll add some debugging code to Win32/Path.inc to see, what's happening when calling destroyFile(), and see, how this path is

Hi all, compilation of package llvm-1.0.tar.gz under redhat 9 is failed with following output: ------- make[3]: *** No rule to make target `/home/vak/llvm/llvm/runtime/GCCLibraries/crtend/BytecodeObj/C++-Exception.bc', needed by `/home/vak/llvm/llvm/lib/BytecodeLibs/libcrtend.bc'. Stop. make[3]: Leaving directory `/home/vak/llvm/llvm/runtime/GCCLibraries/crtend' ...skipped -------

On Sun, 26 Oct 2003, [koi8-r] "Valery A.Khamenya[koi8-r] " wrote: > compilation of package llvm-1.0.tar.gz under redhat 9 is failed with > following output: > make[3]: *** No rule to make target `/home/vak/llvm/llvm/runtime/GCCLibraries/crtend/BytecodeObj/C++-Exception.bc', needed by `/home/vak/llvm/llvm/lib/BytecodeLibs/libcrtend.bc'. Stop. > make[3]: Leaving

Misha Brukman wrote: > On Sun, Feb 26, 2006 at 10:00:18PM -0800, Wink Saville wrote: > > [snip] > If you're using -c, you're telling LLVM that there are other modules you > will link into the executable. Thus, LLVM does not know whether there > will be static ctors/dtors to run or not, so there's the call to > __main() from main. > > __main() gets

Hi all. This has been bugging me for quite some time and I haven't found a solution yet. I was wondering if anyone has any experience with similar scenarios or/and can tell me how this process can be optimized. We use rsync to synchronize JAR libraries on our remote server. The catch here is, that the libraries must go in multiple locations (and not all the locations have all the

On Sun, Feb 26, 2006 at 10:00:18PM -0800, Wink Saville wrote: > Thanks for the info, you've confirmed what I was trying to do, but when > I compile: [snip] > without "-c" (llvm-gcc t1.c -o t1) the dissassembled bytecode does not > call __main: __main() is used to run static constructors and destructors, so if you're compiling without -c, LLVM knows all the files

Hi Reid, > 2. Make sure you aren't trying to link in some old/crufty crtend.bc > file. Try doing "make uninstall ; make clean" in your crtend > directory if you think this might be the case. "make install" fails - there is no such target. > If those don't clear the problem, please tell me what version > of LLVM you're trying to compile

Hi Chris, > Also note, LLVM 1.4 will be released in the next few days, so if waiting is > an option, you might choose to do so. Alright, I've got llvm and llvm-gcc from RELEASE_14 cvs and tried building it under cygwin. 1) The first problem is with llvm in SysUtils.c: int executeProgram(const char *filename, char *const argv[], char *const envp[]) { ................ execveTy

On Wed, 21 Jul 2004, Chris Lattner wrote: > > Yes, this makes a tremendous amount of sense. Do you think you could > prepare some patches to make this happen? If you have any questions, feel > free to ask :) Ok, a patch[1] is attached. I didn't care to coerce the offset, since I assume that it is an uint, but maybe I should? Hopefully I've understood the llvm source

>From: "Baptiste Lepilleur" >Date: Tue, 20 Sep 2005 09:29:07 +0200 > >Henrik Bach wrote: >>Hi, >> >>Please have a look on my private Getting started with MinGW: >> >>http://www.geocities.com/henrik_bach_llvm/ > > >Thanks Henrik.The make line was most useful. Though, in my case I also >needed to add a -L so libimagehlp.a would be

Hello, I have a question regarding bootstrap confidence intervals. Suppose we have a data set consisting of single measurements, and that the measurements are independent but the distribution is unknown. If we want a confidence interval for the population mean, when should a bootstrap confidence interval be preferred over the elementary t interval? I was hoping the answer would be

Henrik Bach wrote: >> From: "Baptiste Lepilleur" >> Date: Tue, 20 Sep 2005 09:29:07 +0200 >> >> Henrik Bach wrote: >>> Hi, >>> >>> Please have a look on my private Getting started with MinGW: >>> >>> http://www.geocities.com/henrik_bach_llvm/ >> >> >> Thanks Henrik.The make line was most useful.