similar to: [LLVMdev] $(LLVMOBJDIR)/include should be added to the serch path

Hi, I recently bootstrapped gcc4 frontend on a i686-linux-gnu too. As I notice, if the llvm "tools-only " was build with srcdir != objdir , the building of llvm-gcc4-1.7.source encountered mistakes of unable to find some header files. So I just edited llvm-gcc4-1.7.source/gcc/Makefile.in and a line like this: INCLUDES += -I$(LLVMOBJDIR)/include With this change, the building errors

Building with --enable-llvm failed latter on when compiling libojc: configure:5099: checking for exception model to use configure:5131: /home/rafael/dev/gcc/build/gcc/xgcc -B/home/rafael/dev/gcc/build/gcc/ -B/i686-pc-linux-gnu/bin/ -B/i686-pc-linux-gnu/lib/ -isystem /i686-pc-linux-gnu/include -isystem /i686-pc-linux-gnu/sys-include -c -xobjecti ve-c -fgnu-runtime -fobjc-exceptions -S conftest.c

On Fri, 21 Apr 2006, [UTF-8] Rafael Esp?ndola wrote: > To work aroud the problem I edited gcc/objc/config-lang.in and removed > the comment from the line > #target_libs=target-libobjc > > With this change it is again possible to build without objc. The > complete configure line was > > ../llvm-gcc4-1.7.source/configure --prefix=$CFEINSTALL > --enable-languages=c,c++

In http://llvm.org/svn/llvm-project/llvm-gcc-4-2/trunk/README.LLVM I can read "Below we assume the LLVM OBJDIR is $LLVMOBJDIR". But in http://llvm.org/docs/GettingStarted.html#terminology I read about OBJ_ROOT. Is this the same? Then terminology is inconsistent. But actually I don't think so, because the text says "These are not environment variables". Still it's

A clean build of revisions 12 or 13 of llvm-gcc4 produces: make[1]: *** No rule to make target `llvm-backend.c', needed by `llvm-backend.o'. Stop. While the gcc/Makefile.in has: llvm-backend.o : llvm-backend.cpp $(ALL_HEADERS) #line 2440 it also has: # APPLE LOCAL begin LLVM #line 1018 ifneq ($(LLVMOBJDIR),) OBJS-common += llvm-backend.o llvm-convert.o

> Well, it depends on the configure parameter used while building llvm- > gcc. Hmm, there are other pages on the the website that tell you how you should configure gcc, e.g. you're led from "How to build the C/C++ Frontend" at http://llvm.org/docs/CFEBuildInstrs.html to Subversion HEAD (by virtue of an "svn co"). Then you're supposed to look at README.LLVM. And

Hi, I have seen the bug http://llvm.org/bugs/show_bug.cgi?id=896 Maybe it is a non-issue but I had some trouble with this. I am running Debian sid and were no longer able to compile llvm. /home/fred/llvm/build/gcc/xgcc: /home/fred/llvm/build/gcc/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6) The installed version have this symbol. strings

I've uploaded the 2.0 pre-release to this location: http://llvm.org/prereleases/2.0/ If you have free time and would like to help test this release, please download the appropriate tarballs from the website. Here are a few ways you can help test this release: 1) Download llvm-gcc4 binary and llvm. Compile and run make check. 2) Download llvm-gcc4 binary, llvm, and llvm-test. Compile, run

Tanya, I have done make check and nightly report tests on LLVM on the GCC 4.2.0 release, on Linux x86 32 bit. On make check the bit intrinsics test is still failing but it works from the command line, strange ? What files do you want from the nightly report, as I am not familiar with it ? I will be doing Cygwin tests next. Aaron ----- Original Message ----- From: "Tanya M.

I've updated the pre-release tarballs online. I'm also extending the testing completion date to May 22nd at 5pm PDT. The new release target date is May 23rd. If you have any free time, please give the new pre-release a try. Thanks to all who have tested LLVM! -Tanya P.S. Documentation review should still be completed today! Thanks! > I've uploaded the 2.0 pre-release to this

> On make check the bit intrinsics test is still failing but it works from the > command line, strange ? Did Chris help you with this or is it still an issue? > What files do you want from the nightly report, as I am not familiar with it > ? in llvm-test, if you run the gmake TEST=nightly report command it will generated a report.nightly.txt file. Thats what I want to see. Thanks!

Aaron, On Thu, 2007-05-17 at 22:54 +0100, Aaron Gray wrote: > Tanya, > > I have done make check and nightly report tests on LLVM on the GCC 4.2.0 > release, on Linux x86 32 bit. > > On make check the bit intrinsics test is still failing but it works from the > command line, strange ? Can you be a bit more specific about which test is failing? Reid. > > What

On Tue, 2007-10-02 at 14:38 -0700, Tanya M. Lattner wrote: > > I've read and followed the README.LLVM file that comes with LLVM-GCC 4.0 > > Front End source, but got the following error when compiling: > > > > configure: error: You must specify valid path to your LLVM tree with > > --enable-llvm=DIR > > make: *** [configure-gcc] Error 1 > > > >

Hi, Op 15-mei-07, om 10:23 heeft Tanya M. Lattner het volgende geschreven: 1) Download llvm-gcc4 binary and llvm. Compile and run make check. I did a debug build on OSX 10.4.9 and everything went fine. Results of "make check" (see ppc.log): === Summary === # of expected passes 1630 # of unexpected failures 21 # of expected failures 2

Dear Anton, you can add your register allocator strait iin the "lib/CodeGen/Passes.cpp", and then 're-make' it: "makellvm llc", on the top of lib/CodeGen. It is faster than running make from LLVMOBJDIR. The problem is that it only add to llc the changes on the lib/CodeGen directory. If you change other parts, a make from LLVMOBJDIR will synchronize it. Try adding

Greetings I'm trying to build LLVM 2.6 GCC from the source files, but I am having problems during the make step. Here is the information: 1. My machine is: Linux firefly 2.6.9-89.0.9.ELsmp #1 SMP Wed Aug 19 08:06:10 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux my gcc version is 4.2.1 2. I've unpacked llvm-gcc-4.2-2.6.source.tar.gz under the llvm-gcc directory. I've also created two

On Aug 24, 2007, at 1:45 PM, Holger Schurig wrote: > In the gray block below "Example of link time optimization" there are > some source files and then a list of commands to execute: > > $ llvm-gcc4 --emit-llvm -c a.c -o a.o > $ llvm-gcc4 -c main.c -o main.o > $ llvm-gcc4 a.o main.o -o main > > 1) in current LLVM (e.g. llvm itself, cfe, llvm-gcc-4.0) no binary

> I've read and followed the README.LLVM file that comes with LLVM-GCC 4.0 > Front End source, but got the following error when compiling: > > configure: error: You must specify valid path to your LLVM tree with > --enable-llvm=DIR > make: *** [configure-gcc] Error 1 > > I've done the following in csh before hand: > $ setenv LLVMOBJDIR

On Tue, May 15, 2007 at 01:23:32AM -0700, Tanya M. Lattner wrote: > 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make > ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. > > It would also be helpful for someone to compile/test with objdir != srcdir. This is on FreeBSD 6.2-RELEASE, on i386. Both llvm and llvm-gcc were compiled with objdir

> On Tue, May 15, 2007 at 01:23:32AM -0700, Tanya M. Lattner wrote: >> 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make >> ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. >> >> It would also be helpful for someone to compile/test with objdir != srcdir. > > This is on FreeBSD 6.2-RELEASE, on i386. > Both llvm and