similar to: [LLVMdev] mingw build problems

Hi, I'm trying to build clang under MingW, but I'm getting a number of errors. Could anyone provide some hints as to what you had to do? I got some tips from http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx, but using the newer packages, as it's a bit old. The ./configure seems to run without errors. The first run of make aborts with errors like:

The next problem I have is: llvm[2]: Linking Debug executable opt /home/foad/llvm/objdir-mingw/Debug/lib/libLLVMSystem.a(DynamicLibrary.o):/home/foad/svn/llvm-project/llvm/trunk/lib/System/Win32/DynamicLibrary.inc:179: undefined reference to `___eprintf' collect2: ld returned 1 exit status I can work around this by removing the two references to __eprintf from

Another observation: GettingStarted.html still gives these instructions for cross-compiling LLVM: 1. Configure and build LLVM as a native compiler. You will need just TableGen from that build. * If you have $LLVM_OBJ_ROOT=$LLVM_SRC_ROOT just execute make -C utils/TableGen after configuring. * Otherwise you will need to monitor building process and terminate it just after

On Mon, Apr 20, 2009 at 3:32 AM, Jay Foad <jay.foad at gmail.com> wrote: >> The attached patch makes GenLibDeps.pl notice that nm has failed, so >> that the build fails immediately rather than giving more obscure >> errors later on. > > Would you mind applying the patch? > Sure. But could you add a message to the "die" commands? Something like: close

On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> To test clang: >> 1) Compile llvm and clang from source. > > LLVM fails to build for me on Cygwin. I get: > Does TOT build? If not, please file a bug. Unfortunately Cygwin is not in our release criteria. I'd like to have a buildbot running (if there is not one already) and then get someone to qualify it for the

> To test clang: > 1) Compile llvm and clang from source. LLVM fails to build for me on Cygwin. I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]:

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: > >>> To test clang: >>> 1) Compile llvm and clang from source. >> >> LLVM fails to build for me on Cygwin. I get: >> > > Does TOT build? If not, please file a bug. No. Theres the runtime install bug (below), and llvm-gcc has a bug that I

On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > 2009/10/20 Tanya Lattner <lattner at apple.com>: >> >> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> >>>> To test clang: >>>> 1) Compile llvm and clang from source. >>> >>> LLVM fails to build for me on Cygwin. I get: >>> >> >> Does TOT build? If not,

Hi, I'm trying to build llvm on a Solaris/Sparc machine. I get many undefined symbols during the link phase of opt. The link command being run is below. It is identical to the link command that gets run and works on an x86 host. Thanks, Tarun g++ -I/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/include -I/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > >> 2009/10/20 Tanya Lattner <lattner at apple.com>: >>> >>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >>> >>>>> To test clang: >>>>> 1) Compile llvm and clang from source. >>>> >>>> LLVM

I'm trying to run some of the test suite using the instructions here: http://llvm.org/docs/TestingGuide.html#quicktestsuite I've built llvm myself, but I'm using pre-built binaries of llvm-gcc (from http://llvm.org/prereleases/2.5/llvm-gcc4.2-2.5-x86-linux-RHEL4.tar.gz). Here's what happens: foad at debian:~/svn/llvm-project/test-suite/trunk$ ./configure

I configured with options: --enable-debug-runtime --prefix=/usr/local/llvm/2.7 --enable-optimized --enable-assertions --enable-shared Build fails with the errors: llvm[2]: Linking Release executable opt (without symbols) /tmp/llvm-build/2.7/llvm-objects/tools/opt/Release/AnalysisWrappers.o(.text+0xb0): In function `(anonymous

> The attached patch makes GenLibDeps.pl notice that nm has failed, so > that the build fails immediately rather than giving more obscure > errors later on. Would you mind applying the patch? Thanks, Jay. -------------- next part -------------- A non-text attachment was scrubbed... Name: patch.die Type: application/octet-stream Size: 892 bytes Desc: not available URL:

Hi, If I configure llvm-gcc 2.6 with --target=mips or --target=mips-elf, I get: c++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -pedantic -Wno-long-long -Wno-variadic-macros -Wmissing-format-attribute -fno-common -DHAVE_CONFIG_H -Wno-unused -DTARGET_NAME=\"mips-elf\" -frandom-seed=0 -I. -I. -I/home/foad/toolchain/llvm/llvm-gcc/gcc

On Linux, when I run "make TEST=ipodbgopt" in MultiSource/Applications/sqlite3 I get: make[4]: Entering directory `/home/foad/llvm/poo/build/test-suite/MultiSource/Applications/sqlite3' Compiling shell.c to Output/shell.bc /home/foad/svn/llvm-project/test-suite/trunk/MultiSource/Applications/sqlite3/speedtest.tcl make[4]: execvp:

> I don't know anything about Solaris, but your paste doesn't actually > contain any errors, just warnings (unless I'm reading "ld: warning: > relocation error:" wrong). It might help to run make without -j until > it fails, and then use `make VERBOSE=1` to print the exact commands > it's running. Sorry. There was so much output I wasn't sure how much

Hi Kees, You added some support for Minix to LLVM's copy of googletest: http://llvm.org/viewvc/llvm-project?view=rev&revision=100895 Is it still being used? If so, would you mind pushing these patches upstream to the googletest project: http://code.google.com/p/googletest/ Otherwise we may drop them, because it makes it harder to import new releases of googletest into the LLVM

Hi Jay, they all seem to work with dragonegg, so I closed them. Ciao, Duncan. On 04/05/12 13:37, Jay Foad wrote: > On 1 May 2012 12:34, Jay Foad<jay.foad at gmail.com> wrote: >> The following bugs look like they only relate to llvm-gcc. Can they be >> closed, as llvm-gcc is no longer supported? > > Also: > > http://llvm.org/bugs/show_bug.cgi?id=1375 >

On 18 July 2011 15:23, David Blaikie <dblaikie at gmail.com> wrote: > Looks like that break came > from http://llvm.org/viewvc/llvm-project?view=rev&revision=135154 > Judging by this ArrayRef ctor you should be able to simplify those calls by > changing the last two arguments from "&foo, 1" to, simply, "foo". I've done this in r135472. Jay.

When I build LLVM with ENABLE_EXPENSIVE_CHECKS=1, make check fails: Running /home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/dg.exp ... FAIL: /home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/2007-05-14-InlineAsmCstCrash.ll Failed with signal(SIGABRT) at line 1 while running: llvm-as < /home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/2007-05-14-InlineAsmCstCrash.ll | llc