similar to: [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

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

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

Chris Lattner wrote: >On Sun, 15 Aug 2004, Robert Feldt wrote: > > > >>However, I wonder if someone supplies pre-built cfrontend binaries for >>cygwin? >> >> > >Nope, we don't have one yet, sorry. > > > >>I followed the instructions and tried to build them myself but get >>when building the cfrontend. Any ideas? >>

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

On Thu, 19 Aug 2004 08:45:23 -0700 Reid Spencer <reid at x10sys.com> wrote: > > I'm running FreeBSD 5.2.1 with gcc 3.3.3. I had some problem starting > > the build as I had to get linux binary emulation to work. (The problem > > here is that FreeBSD can be made compatible with 5 different distros, > > and not all of them work with LLVM. I used linux_base-8;

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]*

Privet, > > Unfortunately, at the end of the process I got the following > > configure: WARNING: ***** llvm C/C++ front end was not > > found, or does not appear to be working. > Yes, Reid changed the CFE build instructions to add > "--program-prefix=llvm" to the end of the configure line, but > autoconf and Makefiles are not yet updated with that change.

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

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

Hi Jeff, On Fri, 2004-08-20 at 08:07, Jeff Cohen wrote: > OK. I've built the front end without any heartaches, but I did > encountered the following glitches: > > The documentation of --with-llvmgccdir is a bit ambiguous. I had to try > several paths before I got the right one. It should state that the > directory is <path>/cfrontend/<platform>/llvm-gcc.

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 [snip] > I don't understand the error message since I see no reference to > Files/ATI. Any clues? Can

Ok, here's the new patch. (Please tell me if I shouldn't mail patches directly on the mailing list.) While I was editing LowerGC.cpp I made a little test (not part of this patch, but the diff with LowerGC.cpp in cvs is attached). I've added a new intrinsic called llvm.gcroot_value(sbyte*, sbyte*), which takes a pointer directly instead and transforms it into an alloca. The idea is the

Hi! I'm trying to build LLVM under cygwin. I have the latest version of cygwin and CVS versions of llvm, llvm-test and llvm-gcc. make of tools only succeeded. make of frontend succeeded too but full make of llvm failed on crtend in llvm/runtime/GCCLibraries with the following message: llvm[0]: Compiling crtend.c for Debug build (bytecode) /bin/sh: -c: line 0: syntax error near unexpected

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

Happy New Year all, I've just updated to the latest CVS version and cygwin port is still broken. When building full llvm: llvm[3]: Compiling crtend.c for Debug build (bytecode) llvm[3]: Compiling listend.ll for Debug build llvm[3]: Linking comp_main.bc component... assertion "(Result->isFirstClassType() || Result == Type::VoidTy || isa<OpaqueType>(Result)) && "LLVM

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

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

> 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

Hi Reid, > 1. Make sure your path now includes <builddir>/Debug/bin instead of > <builddir>/tools/Debug. This changed a little while back. Interesting. I don't have llvm/Debug/ after building "tools-only". Is that a symlink? Do symlinks work under cygwin? (I run xp and both of my partitions are ntfs) > If those don't clear the problem, please tell me