Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Building the llvm runtime: 'Can't destroy file: The process cannot access the fi"
2005 Jan 26
0
[LLVMdev] Building the llvm runtime: 'Can't destroy file: The process cannot access the fi
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
2005 Jan 26
1
[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
2005 Jan 26
0
[LLVMdev] Building the llvm runtime: 'Can't destroy file:Theprocess cannot access the fi
>From: Reid Spencer Date: Wed, 26 Jan 2005 12:23:49 -0800
>
>Nope, unless "make" is an alias for "make -j 4" (like I have)
make is make for me.
>
>Could you try using TOOL_VERBOSE=1 with make to get more output ?
I've attached an output.
Henrik.
>Did you try just running the llvm-ar command by itself ?
>If not, could you and give it the V (capital
2005 Feb 17
2
[LLVMdev] LLVM CFE bootstrap problem at FreeBSD after last $(Install) changes in Makefile.rules
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
2003 Oct 26
2
[LLVMdev] redhat 9, compiling llvm-1.0.tar.gz
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
-------
2004 Aug 19
4
[LLVMdev] Can't get llvmg++ to work
I'm another new person to LLVM. I can't successfully compile and
execute a simple C++ program. The compiler seems to work, as it
produces a.out and a.out.bc files, but I get a whole bunch of warnings:
WARNING: Found global types that are not compatible:
"struct.std::messages<wchar_t>"* %_ZN9__gnu_cxx10messages_cE
[16 x sbyte]*
2004 Aug 19
0
[LLVMdev] Can't get llvmg++ to work
On Wed, 2004-08-18 at 22:14, Jeff Cohen wrote:
> I'm another new person to LLVM.
Hi Jeff. Welcome.
> I can't successfully compile and
> execute a simple C++ program. The compiler seems to work, as it
> produces a.out and a.out.bc files, but I get a whole bunch of warnings:
>
> WARNING: Found global types that are not compatible:
>
2004 Dec 10
1
[LLVMdev] Building llvm and cfrontend under cygwin
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
2005 Jan 27
2
[LLVMdev] Building the llvm runtime: 'Can't destroy file: Theprocess cannot access the fi
>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
2006 Feb 27
2
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
Robert,
Thanks for the info, you've confirmed what I was trying to do, but when
I compile:
-----------------------
#include <stdio.h>
int main(int argc, char *argv[])
{
printf("yo\n");
return 0;
}
-----------------------
without "-c" (llvm-gcc t1.c -o t1) the dissassembled bytecode does not
call __main:
-----------------------
; ModuleID =
2006 Feb 27
2
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
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
2006 Feb 27
0
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
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
2004 Dec 05
1
[LLVMdev] Building llvm and cfrontend under cygwin
Hi there,
I'm trying to build llvm under cygwin running under windows xp, and have
struck the following problem:
-- llvm: tools-only built ok
-- cfrontend: built ok
-- llvm: full build failed at the following point:
make[3]: Entering directory
`/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend'
Compiling crtend.c to bytecode
Compiling listend.ll to bytecode
Linking comp_main.bc
2003 Oct 27
2
[LLVMdev] A small doubt
Hi LLVMDev,
The GCC frontend for LLVM inserts a call to a __main() in the
main() function. Whats the purpose of this? And which LLVM
library do I need to link to satisfy the reference?
Thanks,
Rahul
2006 Apr 25
0
[LLVMdev] src to src conversion
Ryan M. Lefever wrote:
> I am trying to use LLVM as a source to source C compiler. I use
> llvm-gcc to convert file.c->file.bc. Then I use opt to run my own
> compiler passes to convert file.bc->file.opt.bc. Then I use llc to
> convert file.opt.bc->file.opt.c. Now, I want to use normal gcc to
> compile file.opt.c into an executable. However, I'm getting the
2005 Feb 17
0
[LLVMdev] LLVM CFE bootstrap problem at FreeBSD after last $(Install) changes in Makefile.rules
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
>
2005 Oct 18
3
[LLVMdev] Internalize or build broken?
Hi,
I just updated my tree, and when I do a clean rebuild, I get errors
like this:
WARNING: Internalize couldn't load file '/comp_genericeh.lst'!
WARNING: Internalize couldn't load file '/comp_main.lst'!
WARNING: Internalize couldn't load file '/comp_sjljeh.lst'!
WARNING: Internalize couldn't load file '/../gc_exported_symbols.lst'!
It looks like
2006 Apr 25
3
[LLVMdev] src to src conversion
I am trying to use LLVM as a source to source C compiler. I use
llvm-gcc to convert file.c->file.bc. Then I use opt to run my own
compiler passes to convert file.bc->file.opt.bc. Then I use llc to
convert file.opt.bc->file.opt.c. Now, I want to use normal gcc to
compile file.opt.c into an executable. However, I'm getting the
following errors:
test.opt.c:89: warning:
2004 Aug 20
2
[LLVMdev] Can't get llvmg++ to work
On Thu, 19 Aug 2004 08:45:23 -0700
Reid Spencer <reid at x10sys.com> wrote:
>
> Also, as a general note, make sure you follow precisely the steps for
> building the c front end. If you discover any BSDisms that aren't
> documented, we'd love to hear about them.
>
> Thanks,
>
> Reid.
>
OK. I've built the front end without any heartaches, but I did
2005 Oct 18
0
[LLVMdev] Internalize or build broken?
On Tue, 18 Oct 2005, Robert L. Bocchino Jr. wrote:
> I just updated my tree, and when I do a clean rebuild, I get errors like
> this:
>
> WARNING: Internalize couldn't load file '/comp_genericeh.lst'!
> WARNING: Internalize couldn't load file '/comp_main.lst'!
> WARNING: Internalize couldn't load file '/comp_sjljeh.lst'!
> WARNING: