similar to: [LLVMdev] Potential breakage in llvm-gcc's ./configure

> > ./configure in the llvm package will work on my amd64 machine > with this command line: > > ./configure --prefix=$HOME --enable-optimized \ > --build=i686-pc-linux-gnu CC=gcc-4.2 CXX=g++-4.2 > > Note that the CC and CXX flags are set on the command line, not as > environment variables - trying to submit them via the environment got me > all kinds of

(Apologies if this appears twice, it seems to not have made it into the list. I added an update for SVN trunk.) Just a quick heads-up for 2.2 and SVN trunk: ./configure in the llvm package will work on my amd64 machine with this command line: ./configure --prefix=$HOME --enable-optimized \ --build=i686-pc-linux-gnu CC=gcc-4.2 CXX=g++-4.2 Note that the CC and CXX flags are set on the command

Hello, Joachim > This assembler was configured for a target of `x86_64-linux-gnu'. Hrm, try to check, how 'as' is invoked by llvm-gcc, you need jut to run the mentioned cmdline 'by hands': ./xgcc -B./ -B/home/jo/i686-pc-linux-gnu/bin/ -isystem /home/jo/i686-pc-linux-gnu/include -isystem /home/jo/i686-pc-linux-gnu/sys-include -L/home/jo/llvm-gcc-wrk/gcc/../ld -O2 -DIN_GCC

It shoudl work fine if you set CC right and use --build --target --host == i686-pc-linux-gnu On Sun, Mar 30, 2008 at 10:40 AM, Joachim Durchholz <jo at durchholz.org> wrote: > Hi all, > > I managed to navigate around all those issues with environment variables > and such. llvm itself now builds and checks just fine, but I can't get > llvm-gcc to compile. > >

Hi all, I managed to navigate around all those issues with environment variables and such. llvm itself now builds and checks just fine, but I can't get llvm-gcc to compile. Trying to 'make' from .../gcc gives me: ./xgcc -B./ -B/home/jo/i686-pc-linux-gnu/bin/ -isystem /home/jo/i686-pc-linux-gnu/include -isystem /home/jo/i686-pc-linux-gnu/sys-include -L/home/jo/llvm-gcc-wrk/gcc/../ld

To clarify, configure --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu --target=i686-pc-linux-gnu I do this all the time on my 4 core amd64 box and it works fine. On Sun, Mar 30, 2008 at 12:22 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > It shoudl work fine if you set CC right and use --build --target > > --host == i686-pc-linux-gnu > > > > On Sun, Mar 30,

Chris Lattner wrote: > On Thu, 2 Mar 2006, Vladimir Prus wrote: >>>> The instructions seem to have one path wrong. It says to get: >>> >>> I'll put together a tarball today. That will be easier than dealing >>> with a patch, and it will include a bunch of bugfixes since the previous >>> email. >> Further into process, I get this error:

> This is close to a showstopper for integrating an llvm-gcc bootstrap > into the nightly tester. The llvm-gcc ./configure needs to be called > very differently from the llvm ./configure, and keeping two sets of > options is Not Worth The Trouble, at least IMHO. So you didn't like the suggestion of having the configure for llvm-gcc set via an environment variable? That avoids

Hi Jo, > No, that was written under the assumption that passing in CC and CXX > via env variables wouldn't work. Things work now, so that assumption > is obviously wrong. > > I still don't like environment variables. They tend to remain in > effect long after I forgot that I set them, creating all sorts of > hassle. In fact I suspect I already fell prey to this,

Am Montag, den 24.03.2008, 12:06 -0700 schrieb Tanya M. Lattner: > > This is close to a showstopper for integrating an llvm-gcc bootstrap > > into the nightly tester. The llvm-gcc ./configure needs to be called > > very differently from the llvm ./configure, and keeping two sets of > > options is Not Worth The Trouble, at least IMHO. > > So you didn't like the

Hi all, I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the (broken-for-LLVM) gcc-4.1 as a compiler. The error message that I got was this: make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore' make[1]: *** No rule to make target `/home/jo/llvm-wrk/Release/bin/tblgen', needed by `/home/jo/llvm-wrk/lib/VMCore/Release/Intrinsics.gen.tmp'. Stop.

You're right, thanks. However, now I ran into the next problem. This seems to be related to the fact that I have a 64-bit machine? $ ../../src/llvm-gcc/configure --prefix=/home/johan/llvm --program-prefix=llvm- --enable-llvm=/home/johan/llvm/obj/llvm --enable-languages=c,c++ ... $ gmake ... /home/johan/llvm/obj/llvm-gcc/./gcc/xgcc -B/home/johan/llvm/obj/llvm-gcc/./gcc/

On Mar 20, 2008, at 3:00 PM, Joachim Durchholz wrote: > Hi all, > > I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the > (broken-for-LLVM) gcc-4.1 as a compiler. > The error message that I got was this: > make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore' > make[1]: *** No rule to make target > `/home/jo/llvm-wrk/Release/bin/tblgen',

>> I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the >> (broken-for-LLVM) gcc-4.1 as a compiler. >> The error message that I got was this: >> make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore' >> make[1]: *** No rule to make target >> `/home/jo/llvm-wrk/Release/bin/tblgen', needed by >>

llvm's ./configure already does that for gcc < 3. What are valid versions? Exactly 4.0 and 4.2? 4.0 and >=4.2? dnl Verify that GCC is version 3.0 or higher if test "$GCC" = "yes" then AC_COMPILE_IFELSE([[#if !defined(__GNUC__) || __GNUC__ < 3 #error Unsupported GCC version #endif ]], [], [AC_MSG_ERROR([gcc 3.x required, but you have a lower version])]) fi

gcc 3.4.x builds LLVM incorrectly on x86_64. gcc 4.0 will get you much farther, but the llvm-test regression tests still have massive problems. Zhongxing Xu wrote: > The machine is a Dell workstation with xeon processors. The OS is RHEL > 4 AS x86_64 > gcc version is 3.4.6 > > I checked out the llvm-gcc from svn, configured with > ../llvm-gcc/configure

The machine is a Dell workstation with xeon processors. The OS is RHEL 4 AS x86_64 gcc version is 3.4.6 I checked out the llvm-gcc from svn, configured with ../llvm-gcc/configure --prefix=$HOME/llvm-gcc-install --enable-llvm=$HOME/llvmobj/ --enable-languages=c,c++ --enable-checking --disable-shared --disable-multilib and get the following error message: make

Already have concerning gcc 3.4: http://llvm.org/bugs/show_bug.cgi?id=1056 As for llvm-test issues, quite frankly I don't know how well they're expected to work on x86_64. No one has jumped in and said they run fine on their x86_64 system. Maybe they're code generator bugs, or maybe they're portability issues for FreeBSD (though I never saw such massive problems with 32-bit

I get the output below on Ubuntu Hardy on ia32 from svn 56984. John make[2]: Entering directory `/home/regehr/llvm-gcc/build/gcc' /home/regehr/llvm-gcc/build/./gcc/xgcc -B/home/regehr/llvm-gcc/build/./gcc/ -B/home/regehr/i686-pc-linux-gnu/bin/ -B/home/regehr/i686-pc-linux-gnu/lib/ -isystem /home/regehr/i686-pc-linux-gnu/include -isystem /home/regehr/i686-pc-linux-gnu/sys-include -O2 -O2

I think this error is due to these changes: Doing diffs in .: --- ./gsyslimits.h.~1~ 2006-11-26 12:31:50.000000000 -0800 +++ ./gsyslimits.h 2007-04-02 12:37:38.000000000 -0700 @@ -4,5 +4,3 @@ instead of this text. */ #define _GCC_NEXT_LIMITS_H /* tell gcc's limits.h to recurse */ -#include_next <limits.h> -#undef _GCC_NEXT_LIMITS_H --- ./limitx.h.~1~ 2006-11-26