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

/Have you tried to build llvm-gcc by yourself? /Not with the recent build. In times past I failed miserably at this using cygwin. Maybe I should try again? /Normally crt*.o files are built during normal gcc build process (llvm-gcc as well). However, mingw32 runtime has its own crt*.o files, which are included with binary distribution of llvm-gcc4 (mingw32 variant). /I thought that would be

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. > 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. > 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

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

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

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

Hi Thanks for the info, it led to the source of the error I was having. I was using llvm-gcc binaries (built with mingw I guess) to compile a .c file that is my language runtime, llvm-link'ing that with my frontend's .ll, and using an vcpp-built lli to run the resulting bytecode. This caused the special case in X86RegisterInfo::emitPrologue for "main" to try to align the stack

The alloca hook is in lib\System\Win32\DynamicLibrary.inc all the way at the bottom. You'll see a __MING32__ #ifdef around the definition. You just have to implement those methods and it'll work just fine. Jake On 6/24/07, Scott Graham <scott.llvm at h4ck3r.net> wrote: > > Hi > > Thanks for the info, it led to the source of the error I was having. > > I was using

I'm having some trouble getting llvm-gcc4 to compile. It's unable to compile darwin-crt3.c. It's mentioning "Complex expression. Absolute segment assumed." but I'm not sure if that's a real error message. Has anyone run into this before? I'm running on a G4 apple 10.4.8, kernel version 8.6.0. I googled around and found a bug with the same error message:

Hello, Scott. > Checking the assembly from llc, the first alloca call is to allocate > local vars in _main. Is this just the state of the code at 2.0 when > built with vs.net, or is there something that I've managed to > mis-build locally? _alloca is used to probe the stack, if you asks for locals of size more that 4k. This is pretty ugly, but the names of this functions differs

I'm looking forward to your patches and bug reports. I really want to get this going myself. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Anton Korobeynikov Sent: Wednesday, May 10, 2006 1:22 PM To: LLVM Developers Mailing List Subject: [LLVMdev] Successfulyl bootsrapped llvm-gcc4 on mingw32 Hello, Everyone. Today

Hello, Greg. You wrote Saturday, May 6, 2006, 10:24:16 PM: GP> If anyone has any insight I'd love to hear it. GP> Meanwhile, I'll continue to investigate... Currently I'm working on bootstrapping llvm-gcc4 on mingw32 platform. There are some serious miscompartibilities preventing build. I'll let know the results. Anyway, it's common knowledge, that msys itself have

Hello, Aaron. > /usr/src/llvm-gcc4/gcc/libgcc2.c: In function '__eprintf': > /usr/src/llvm-gcc4/gcc/libgcc2.c:1832: internal compiler error: > Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://llvm.org/bugs> for instructions. You should: 1. Try to emit bytecode with --emit-llvm compiler switch. 1.1

Reid & Aaron > > This is the same error that appears alot of times on the 'make check' > > of the debug build. > > > > What is going on here please ? > > Sounds to me like the llvm-gcc being used wasn't configured using > --with-llvm=. That message occurs when llvm-gcc is built > "normally" (without using llvm). Yes. llvm-gcc4

Hello, Everyone. Today I've finished digging into llvm-gcc4 in order to build in under mingw32. The most trickiest was to make libstdc++ build, since its configure & makefiles are not so perfect as main gcc ones. There are several problems with inline assemler (in two places at least), but both of them are easily seen. Also, there are some compiler crashes while compiling libiberty (with

Hello Philipp. > Why does it need target libraries and binutils? gcc building process (and llvm-gcc4 as well) includes building of target-specific stuff including: 1. Building crt-support code on several platforms 2. Building libgcc.a[.so] 3. Building libstdc++.a[.so] If you don't want them to be built you should, probably you should consult gcc documentation to find right options or

Hello, Everyone. I'm currently trying to bootstrap llvm-gcc4 on mingw32 platform. Everything (except some small fixes) seems to be fine: stage1 finished successfully. I'm linking with debug variant of LLVM, since linker bug prevents release builds. Unfortunately, stage2 failes immediately with this cryptic message: $/f/tmp/llvm/gccbuild/gcc/xgcc -B/f/tmp/llvm/gccbuild/gcc/

Hello, Everyone. All blackmagic (playing with pwd, etc) in my build description has gone with patched bash (pwd builtin was just hardly disabled). It's not good, I myself prefer modifying libstdc++ configure script to use PWD_CMD environmental variable as main gcc ones. I'm working on this feature. -- With best regards, Anton mailto:asl at math.spbu.ru