search for: libcrtend

...e 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?: ----------------------------- llvm[3]: Building Debug Bytecode Archive libcrtend.bca /bin/rm -f /C/projects/build/MinGW/llvm-4-1/Debug/lib/libcrtend.bca /C/projects/build/MinGW/llvm-4-1/Debug/bin/llvm-ar rcsf /C/projects/build/MinGW/llvm-4-1/Debug/lib/libcrtend.bca /C/projects/build/MinGW/llvm-4-1/runtime/GCCLibraries/crtend/Debug/comp_genericeh.bc /C/projects/build/MinGW/ll...

...eturned 1 exit status make: *** [test.opt.exe] Error 1 ------ I think the problem with main and __main is that I need to link in some LLVM runtime libraries. So, I tried to link in crtend (which defines __main). However, I get the following error: /home/testbed1/lefever/work/llvm/install/lib/libcrtend.a: could not read symbols: Archive has no index; run ranlib to add one collect2: ld returned 1 exit status make: *** [test.opt.exe] Error 1 I tried creating a copy of the libcrtend.a and running ranlib on it and I also separately tried running llvm-ranlib on it. Neither of those actions worked...

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 /usr/home/wanderer/pkg/build/llvm/night/cfe/bin/../lib/libcrtend.a install: illegal option -- D usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2...

...ile.opt.c. Now, I want to use normal gcc to > compile file.opt.c into an executable. However, I'm getting the > following errors: Please try the following: llvm-gcc -o final file.opt.bc -lcrtend llc -march=c final.bc gcc -o finalexec final.cbe.c The first line uses llvm-gcc to link libcrtend.a to your optimized bytecode file. Using llvm-gcc ensures that it picks up the version of libcrtend.a located within your llvm-gcc distribution (which should work). The second and third lines generate the C code and compile it into a final executable. If that doesn't work, please let me k...

...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?: > > ----------------------------- > llvm[3]: Building Debug Bytecode Archive libcrtend.bca > /bin/rm -f /C/projects/build/MinGW/llvm-4-1/Debug/lib/libcrtend.bca > /C/projects/build/MinGW/llvm-4-1/Debug/bin/llvm-ar rcsf > /C/projects/build/MinGW/llvm-4-1/Debug/lib/libcrtend.bca > /C/projects/build/MinGW/llvm-4-1/runtime/GCCLibraries/crtend/Debug/comp_genericeh.bc > /...

...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?: > > > > ----------------------------- > > llvm[3]: Building Debug Bytecode Archive libcrtend.bca > > /bin/rm -f /C/projects/build/MinGW/llvm-4-1/Debug/lib/libcrtend.bca > > /C/projects/build/MinGW/llvm-4-1/Debug/bin/llvm-ar rcsf > > /C/projects/build/MinGW/llvm-4-1/Debug/lib/libcrtend.bca > > >/C/projects/build/MinGW/llvm-4-1/runtime/GCCLibraries/crtend/Debug/co...

...VM 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 > /usr/home/wanderer/pkg/build/llvm/night/cfe/bin/../lib/libcrtend.a > install: illegal option -- D > usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] >...

...tecode_libdir is $(LLVMGCCDIR)/bytecode-libs The things that go into $(libdir) are built from the "runtime" directory but aren't bytecode libraries, they are .so, .a or .o files (native builds) The things that go into $(bytecode_libdir) are bytecode libraries, mostly *.bc but also libcrtend.a (which contains bytecode) This creates a certain amount of confusion. When one does an install, everything that gets installed should be under the $(prefix) variable somewhere. This is almost true today, except for the things that are installed into $(bytecode_libdir). So, to clear up the in...

...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?: > > > > > > > > ----------------------------- > > > > llvm[3]: Building Debug Bytecode Archive libcrtend.bca > > > > /bin/rm -f /C/projects/build/MinGW/llvm-4-1/Debug/lib/libcrtend.bca > > > > /C/projects/build/MinGW/llvm-4-1/Debug/bin/llvm-ar rcsf > > > > /C/projects/build/MinGW/llvm-4-1/Debug/lib/libcrtend.bca > > > > > > > >/C/projects/bu...

...l files from System/FreeBSD dir in LLVM sources. Rebuild LLVM with updated CVS sources and install without errors. Back to nighttest failures problem. > This looks like your crtend.a file did not get built correctly. Try doing > make clean/make install in llvm/runtime/ again. lib\Debug\libcrtend.a builded. But i not found it in LLVM installation dir after install. Vladimir

...subroutine in t1sub1.c and t1sub2.c. I then do the following in my makefile: llvm-gcc -c t1.c -o t1.bc llvm-gcc -c t1sub1.c -o t1sub1.bc llvm-gcc -c t1sub2.c -o t1sub2.bc llvm-ar r t1.a t1sub1.bc t1sub2.bc llvm-ar: creating t1.a llvm-ld -o t1.app t1.bc t1.a /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a llvm-ld: warning: Cannot find library 'crtend' llc t1.app.bc -o t1.app.s gcc -m32 t1.app.s -o t1 So a few minor problems, the first is really minor the llvm-ld command generates the t.app script that runs t1.app.bc, obviously no big deal, but isn't what I expected and would s...

...;> to compile file.opt.c into an executable. However, I'm getting >> the following errors: > > Please try the following: > > llvm-gcc -o final file.opt.bc -lcrtend > llc -march=c final.bc > gcc -o finalexec final.cbe.c > > The first line uses llvm-gcc to link libcrtend.a to your optimized > bytecode file. Using llvm-gcc ensures that it picks up the version > of libcrtend.a located within your llvm-gcc distribution (which > should work). > > The second and third lines generate the C code and compile it into > a final executable. > &gt...

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 ------- --- Valery A.Khamenya

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

On Thu, 11 Nov 2004, Vladimir Merzliakov wrote: > > This looks like your crtend.a file did not get built correctly. Try doing > > make clean/make install in llvm/runtime/ again. > > lib\Debug\libcrtend.a builded. > > But i not found it in LLVM installation dir after install. 'make install' should install this into the CFRONTEND/bytecodeobjs directory. -Chris -- http://llvm.org/ http://nondot.org/sabre/

...ille wrote: > I then do the following in my makefile: > > llvm-gcc -c t1.c -o t1.bc > llvm-gcc -c t1sub1.c -o t1sub1.bc > llvm-gcc -c t1sub2.c -o t1sub2.bc > llvm-ar r t1.a t1sub1.bc t1sub2.bc > llvm-ar: creating t1.a > llvm-ld -o t1.app t1.bc t1.a /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a > llvm-ld: warning: Cannot find library 'crtend' Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld. Alternatively, instead of using llvm-ld, just use gccld to link like this: llvm-gcc -o t1.app t1.bc t1.a ... which should work. > llc t1.app.bc -o t1.app....

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

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 =

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=GB2312" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Yes, I checked that envvar, and it is set.<br> The error msg when compiling a .c

...nya[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 directory `/home/vak/llvm/llvm/runtime/GCCLibraries/crtend' > ...skipped Makes sure that you have the C front-end installed correctly, and that the configure script found it (you have to provide the path to the C frontend to the configure script). -Chr...