similar to: [LLVMdev] LLVM 1.5 Release Plan

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

On Wed, 11 May 2005, Oleg Smolsky wrote: > 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

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.

Hello Duraid, Duraid Madina wrote on Wednesday, 11 May 2005: >> 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. Oh,

Hello Chris, Chris Lattner wrote on Wednesday, 11 May 2005: >> I've just tried building CVS/HEAD of llvm using gcc 4.0.0 that I have >> installed to /opt/gcc and got the following error quite late in the >> process: > That looks like GCC 4.0 either has a bug or is installed wrong. I think > that it's trying to link with the wrong libstdc++. Hmm... I can build

> 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

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 LLVM'ers I got this error: ------------------------------- gmake[3]: Entering directory `/usr/local/src/llvm/lib/Target/X86' Building X86.td register information header with tblgen tblgen: Assertion failed: "Buffer[Length-1] == '"'", file FileLexer.l, line 114 gmake[3]: *** [X86GenRegisterInfo.h.inc] Abort trap (core dumped) gmake[3]: Leaving directory

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, Any news on the cygwin front? What needs to be done? Can I help? Oleg.

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 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, > - llvm/make tools-only worked ok Good. > - llvm-gcc/make all failed with the following message (2nd try): > make[2]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' > make[1]: Leaving directory `/home/oleg.smolsky/llvm-gcc-build/gcc' > Checking multilib configuration... > multilib.out is unchanged > Configuring in i686-pc-cygwin/libstdc++-v3 >

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

Hi, I was wondering whether anyone has managed to compile the LLVM libraries to run on iPhone? After compiling and installing the iPhone toolchain on MacBook running Leopard (10.5.2). I run configure In the llvm2.3 directory: ./configure –host=arm-apple-darwin –target=arm-apple-darwin –enable-optimized –enable-targets=arm I run make, including an override for TBLGEN (because I obviously

On Wed, Jun 11, 2008 at 11:49 AM, Gordon Henriksen <gordonhenriksen at mac.com> wrote: > Could you please update to r52213 or later in svn and check whether > this error is resolved with your gcc? Latest trunk fixes that error. Next problem :) llvm[3]: Building ARM.td register information header with tblgen llvm[3]: Building ARM.td register names with tblgen llvm[3]: Building ARM.td

Thanks! That helps! Reid. On Thu, 2004-12-23 at 12:07, Oleg Smolsky wrote: > 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

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

Has anyone managed to get FF 18.0 to work on Centos 5.8? I've been hacking at it, placing a stack of .so files (from Centos 6) into a private directory, then using LD_LIBRARY_PATH to point the system to (in a shellscript that subsequently invokes ff 18) but so far I've not managed to find the right combination. I've moved over libstdc++, all or nearly all the .so files from glib2 and