similar to: [LLVMdev] No crt2.o file found

Hello, Matthew. > Not with the recent build. In times past I failed miserably at this using cygwin. Maybe I should try again? Well, actually I mean: whether llvm-gcc binary under consideration was built by yourself or you're using pre-built binaries from downloads section? If you're using llvm-gcc4 binary from downloads section, mingw binary is included into tarball, you might find

Hello, Matthew > I managed to get the llvm tool chain compiled on my windows machine > using mingw a couple of weeks ago. Have you tried to build llvm-gcc by yourself? > $ llvm-gcc hello.c -o hello.exe > ld: crt2.o: No such file: No such file or directory Normally crt*.o files are built during normal gcc build process (llvm-gcc as well). However, mingw32 runtime has its own crt*.o

Hello, Matthew. > > I figured that just copying the mingw crt*.o files would not > > be a good idea. > /Why not? Mingw32 crt does not depend on LLVM. /I rashly copied all the *.o files from my mingw\lib directory to the llvm\lib directory. This does enable the hello world binary to compile and to function correctly. However the byte code file does not work correctly giving:

Hello, Matthew. > My file size matches the patched file. I haven't figured out how to get 7-zip to give me checksum information on windows. Use md5sum utility. It can be successfully found via google. > I rashly copied all the *.o files from my mingw\lib directory to the llvm\lib directory. > This does enable the hello world binary to compile and to function correctly. Strange.

Hello, Matthew. > Hmm there is no llvm-gcc directory in either the patch file or what made it > on to my system. Furthermore there are no crt*.o files after my build until > I put them in the lib directory, which where they are in the patch file. > Again the clean must have removed them. Well. Actually you should have 2 trees: 1. One you're building LLVM in. There is directory

Hello, Matthew. > I figured as much. It would be great to get the mingw branch on > windows working, since it avoids the cygwin dll and some restrictive > licensing issues. Mingw32 branch is quite ok as the time of writing this lines :) I was able to compile Qt with llvm-gcc4 1.9 and everything was fine. So, I suppose something went wrong during unpacking tarball or something like

I managed to get the llvm tool chain compiled on my windows machine using mingw a couple of weeks ago. When I tried to run the simple test case provided in the documentation I ran into a problem of missing object files. I attempted to compile the simple hello.c hello world application. Unfortunately I get the following $ llvm-gcc hello.c -o hello.exe ld: crt2.o: No such file: No such file

Hi all, After being able to build llvm and llvm-gcc on windows/mingw, I am running into problems with linking. It seems llvm-gcc isn't able to find crt2.o. Ronald

On Thu, 16 Nov 2006, Tanya M. Lattner wrote: >> * I don't think this is ready for release. In particular the llvm-gcc4 >> binary >> seg faults on FC 5 for most of llvm-test programs. >> * I'm going to re-try without using the binaries and building >> everything from scratch. > > Does llvm-gcc4 seg fault for make check? I've done extensive

> On Thu, 20 Apr 2006, [UTF-8] Rafael Esp?ndola wrote: > > > I am trying to bootstrap the just released gcc 4.0.1 and the cvs head llvm. > > > > I was able to build the llvm tools without a problem. > > gcc has a small problem (from the apple branch IIRC): libojc is built > > unconditionally, so objc must be in the --enable-languages option for > > the

On Thu, 20 Apr 2006, [UTF-8] Rafael Esp?ndola wrote: > I am trying to bootstrap the just released gcc 4.0.1 and the cvs head llvm. > > I was able to build the llvm tools without a problem. > gcc has a small problem (from the apple branch IIRC): libojc is built > unconditionally, so objc must be in the --enable-languages option for > the build to be successful. > > Building

Thank you, Reid, I tried llvm-gcc -lcrtend ary3.c -o ary3, but I get gccld: warning: Cannot find library 'crtend' gccld: warning: Cannot find library 'c' I have the libraries in my llvm directory: llvm/runtime/GCCLibraries/crtend Well, how do I link this to the LLVM runtime stuff? Before building from the source, I had copied all the .h from my old gcc 4.0 to

If you're building llvm-gcc4, you don't need the runtime libraries, so I'd just stick with the "tools-only" build and declare success. If you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :) However, the problem appears to be your PATH variable. In your path you have the following directory: C:/Program Files/Microsoft DirectX SDK (June

First, thanks for testing this! > Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5) > > HIGH LEVEL COMMENTS > * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't > that be llvm-1.9? We have always labeled the dir just llvm which is fine. If you build llvm it will know its version 1.9. > * LLVM was built in Release mode

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

dear community, sorry for posting again a beginner's question but i can't find a solution on my own. i installed all llvm and llvm-gcc4 in a directory called "~/programs/llvm/install" in my home folder. i can build a test c - file as follows: ~/programs/llvm/install/bin/gcc -v -o test test.c Using built-in specifications. Target: i686-pc-linux-gnu Configured with:

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 01 Sep 2006, at 10:05, Kenneth Hoste wrote: > >> >>> Also, it is possible to tell make only to compile benchmark X? How >>> can I >>> enforce this? >> >> Go into the directory for that benchmark, then run 'make' or >> whatever. > I tried tom compile each of the SPEC CPU2000 benchmarks using the make command is each respective

Misha Brukman wrote: >On Mon, Aug 16, 2004 at 01:07:39PM +0200, Robert Feldt wrote: > > >>However, when I go back to rebuild llvm, reconfigure, setting the >>CFEINSTALL dir, then make it can build the tools ok but not the >>runtime: >> >> >[snip] > > >>Compiling crtend.c to bytecode >>Files/ATI: not found >> >>

On Fri, 1 Sep 2006, Kenneth Hoste wrote: > Some problems were solved, new ones arised... Getting closer though... > The fixes for the previous problems are at the bottom of this email, > bug reports will be submitted when all problems are solved. Kenneth, In general, I am more than happy to help people on this list. It is good for the community and I enjoy helping people be successful