similar to: [LLVMdev] Cygwin build is still broken

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

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.

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

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

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

Hi Reid, >> I've just updated to the latest CVS version and cygwin port >> is still broken. When building full llvm: > > Any ideas? Has anybody been able to replicate this issue? > > GNU assembler 2.15.91 20040725 > > gcc (GCC) 3.4.1 (cygming special) > > Cygwin builds just fine for me. It looks like you're using > the wrong tools. Please read:

Hi LLVM, In lib/VMCare/Verifier.cpp::visitInstruction, we have such code 1287 // Check that the return value of the instruction is either void or a legal 1288 // value type. 1289 Assert1(I.getType() == Type::getVoidTy(I.getContext()) || 1290 I.getType()->isFirstClassType() 1291 || ((isa<CallInst>(I) || isa<InvokeInst>(I)) 1292 &&

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

I got the following error in 1.5 release. As far as installation is concerned, everything went fine. llc hello.bc -o hello.bs llc((anonymous namespace)::PrintStackTrace()+0x17)[0xd435f1] llc((anonymous namespace)::SignalHandler(int)+0xbd)[0xd437ff] /lib64/tls/libc.so.6[0x3ff522e410] llc(llvm::Type::isFirstClassType() const+0x13)[0x8fc38d] llc(llvm::FunctionType::FunctionType(llvm::Type const*,

Hi Jeff and others, When building the llvm runtime, I always get this error message: 'Can't destroy file: The process cannot access the file 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?:

On Sun, 28 Mar 2004, Reid Spencer wrote: > The XPL compiler produced the attached OneOfEach.bc file without error > or warning from either LLVM or XPLC. However when I llvm-dis the file, I > get: > > llvm-dis: Failed value look-up for name 'entry' I'm guessing that 'entry' is a basic block? > The Bytecode Reader prints this out when it can't find the

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;

Hello, I am testing the new cool LLVM python bindings that Mahadevan wrote over the past few weeks. I came across a problem in the python binding which directed me to use of 'cassert'[1] in LLVM itself. When LLVM users make a mistake in using the library's constructs they usually hit an assertion. This form of defensive programming is great for detecting errors as soon as they

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

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

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

The XPL compiler produced the attached OneOfEach.bc file without error or warning from either LLVM or XPLC. However when I llvm-dis the file, I get: llvm-dis: Failed value look-up for name 'entry' The Bytecode Reader prints this out when it can't find the associated value for the name. Obviously I botched something in the XPL compiler but I would have thought the verified would

On Nov 12, 2008, at 5:07 PM, David Greene wrote: > On Wednesday 12 November 2008 18:58, Chris Lattner wrote: >> On Nov 12, 2008, at 3:37 PM, David Greene wrote: >>>>> Unfortunately, calling FunctionType::refineAbstractType(opaque, >>>>> void >>>>> (...)) >>>>> doesn't work because RefineAbstractType doesn't recurse

On Wednesday 12 November 2008 19:13, Chris Lattner wrote: > You shouldn't be refining the pointer, you should use: > > t1->refineAbstractType(t2) Ok, I tried this and I get further. But the type system seems to have trouble when refining multiple types and those types resolve to the same thing. I turned on DEBUG_MERGE_TYPES to illustrate: *** First function type ***

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