similar to: [LLVMdev] Cygwin build is still broken

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

Hello Aaron, Aaron Gray wrote on 14/10/2005 at 5:50 a.m.: >> Also, it would be really nice if an official cygwin build (the >> binary) was published too. I spent quite a bit of time screwing >> with it a few months ago, and it was quite a bastard to get >> going... > I had quite a time with it too, could only get the debug version to > build as there seemed to be an

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

On Wed, Dec 08, 2004 at 11:23:39AM +1300, Oleg Smolsky wrote: > > 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 >

> Also, it would be really nice if an official > cygwin build (the binary) was published too. I spent quite a bit of > time screwing with it a few months ago, and it was quite a bastard to > get going... I had quite a time with it too, could only get the debug version to build as there seemed to be an internal problem with ld. I would very interested in how you got it running and

OK I've got GNU ld version 2.15.94 20041229 as and ar are the same version number etc. I think the latest release is 2.16. I guess you guys like to stay on the bleeding edge! I'll give it a try with the cfrontend included as suggested, but I'm actually writing a pattern matching compiler for a non-C scripting language and I'm looking for an optimizing back-end such as llvm. I

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

Hi all, After successfully building llvm tools-only and cfontend, I went back to llvm directory and ran configure --with-llvmgccdir=$CFEINSTALL Unfortunately, at the end of the process I got the following configure: WARNING: ***** llvm C/C++ front end was not found, or does not configure: WARNING: ***** appear to be working. And I do have CFEINSTALL environment variable.... BTW, I have noticed

Hi all, Any news on the cygwin front? What needs to be done? Can I help? Oleg.

Hi Reid, > I've been doing a Cygwin build today too. All these problems > have been updated in the current CVS. Please update your tree > and give it another try. Alright, this time everything works quite a bit better. However: tools\llvm-ld\llvm-ld.cpp needs the CopyFile() invocation fix identical to gccld.cpp Also, it turns out gcc 3.3.3 in cygwin is buggy and it's unable

Hey all, is anyone gonna make a debian package for stable or testing? It's just that building llvm/cfrontend drives me crazy :) Best regards, Oleg.

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

Oleg Smolsky wrote: > Hey all, > > is anyone gonna make a debian package for stable or testing? It's just > that building llvm/cfrontend drives me crazy :) We don't have Debian packages for LLVM 1.5, but we do have a pre-compiled GCC frontend for i386/Linux. Does that not work on Debian? > > Best regards, > Oleg. > >

On Tue, Dec 21, 2004 at 10:24:29AM +1300, Oleg Smolsky wrote: > Any news on the cygwin front? What needs to be done? Can I help? At some point, LLVM built and ran on Cygwin, however, the only user at the time (Chris) no longer uses Cygwin, so it may or may not currently build on Cygwin. Please try it out, if it doesn't work, please tell us what's wrong, or, better yet, submit a patch.

Hi all, > Please try it out, if it doesn't work, please tell us what's > wrong, or, better yet, submit a patch. :) Alright, here are the results of building the latest llvm from CVS under cygwin: lib\Debugger\SourceFile.cpp needs #include <assert.h> when building with gcc 3.3.3 tools\gccld\gccld.cpp line 128 tools\llvm-ld\llvm-ld line 318 need

If you use Microsoft's VC++ compiler to build LLVM, you don't need to build the C front end (indeed, you can't even if you wanted to). Matthew Bromberg wrote: > OK I've got > GNU ld version 2.15.94 20041229 > as and ar are the same version number etc. I think the latest release > is 2.16. > I guess you guys like to stay on the bleeding edge! > > I'll

Hello all, John Criswell wrote on Wednesday, 11 May 2005: > If other developers (especially those for platforms which we don't have > here at UIUC) could test the release branch, we would be most > appreciative. I will send out another email detailing when the release > branch is finished and how to get it out of CVS. I've just tried building CVS/HEAD of llvm using gcc 4.0.0

Dear LLVMers, Here is the current, tentative schedule for LLVM 1.5: 1. We are hoping to have all relevant features and bug fixes into mainline CVS by Friday of this week. For those of you with commit access, please plan to have all of your changes for LLVM 1.5 committed by 9 am (CST) this Friday. If you need more time, please email the list. 2. On Friday, I will be making the 1.5 release

Hi Reid, > Jeff, can you provide a test case that we can use to > reproduce this problem? Looks like I'm finally going to > force myself into a windows build (i.e. cough up the money > for VC++ 7.1). You can also download MS Visual C++ Toolkit 2003 - contains the VC++ 7.1 compiler/linker as well as all the standard libraries and headers. No gui, no debugger though:

Oleg Smolsky wrote: > I've just tried building CVS/HEAD of llvm using gcc 4.0.0 that I have > installed to /opt/gcc ... then you should either add /opt/gcc/lib to /etc/ld.so.conf and rerun ldconfig, or add /opt/gcc/lib to your LD_LIBRARY_PATH . However, GCC 4.x definitely has issues building LLVM, at least on ia64. If you want to use LLVM in anger, I'd stick with 3.4 for now.