similar to: [LLVMdev] Unable to build LLVM-GCC 2.3 (using x86_64 and gcc 4.2.3-2ubuntu7)

Am Sonntag, den 22.06.2008, 15:19 +0100 schrieb Alan Jenkins: > config.log: > > configure:2119: checking for C compiler default output file name > configure:2122: /home/alan/pkg/llvm/obj/./prev-gcc/xgcc > -B/home/alan/pkg/llvm/obj/./prev-gcc/ > -B/usr/local/x86_64-unknown-linux-gnu/bin/ -g -O2 conftest.c >&5 > configure:2125: $? = 0 > configure:2171: result:

> It seems you can't compile and run C programs at all. > > Maybe because you are using /home/alan/pkg/llvm/obj/./prev-gcc/xgcc instead of the system's gcc, which might be broken. During bootstrap stage 2 it is normal to use the just built gcc. I don't understand why he is having this problem - I bootstrap llvm-gcc from time to time on x86-64 linux. Ciao, Duncan.

Hello, Everyone > It seems you can't compile and run C programs at all. > > Maybe because you are using /home/alan/pkg/llvm/obj/./prev-gcc/xgcc instead of the system's gcc, which might be broken. It seems, that you're doing full bootstrap build. It can be broken due to some missing bits in LLVM's x86-64 ABI support. I'd suggest to try '--disable-bootstrap'

FYI: It also showed up for ARM yesterday, but only for a non-debug build. On Mar 5, 2009, at 4:32 AM, Gabor Greif wrote: > Hi Bill, > > this might be a latent bug related to PPC. I have no such > machine to access atm., but I shall be able to reproduce the > problem when back at home. (In about 4 hours). > > I keep you informed. > > Cheers, > > Gabor >

Hi Bill, this might be a latent bug related to PPC. I have no such machine to access atm., but I shall be able to reproduce the problem when back at home. (In about 4 hours). I keep you informed. Cheers, Gabor On Mar 4, 7:57 pm, Bill Wendling <wendl... at apple.com> wrote: > Something last night broke the build on Darwin PPC. Possible Gabor's   > check-in? > > -bw

Hi Warren, you can try to configure with the following export CFLAGS="-m64" export LDFLAGS="-L/usr/lib64" LLVM: ../src/configure --prefix=`pwd`../install --enable-optimized --enable-jit --enable-targets=host-only make LLVM-GCC: ../llvm-gcc4-2.0.source/configure --prefix=`pwd`../install --program-prefix=llvm- --enable-llvm=/home/warren/llvm/obj/ --enable-languages=c,c++

Something last night broke the build on Darwin PPC. Possible Gabor's check-in? -bw Begin forwarded message: > From: admin at spang.apple.com (admin) > Date: March 4, 2009 3:56:10 AM PST > To: wendling at apple.com > Subject: PPC Nightly Build Result > > /Volumes/SandBox/NightlyTest/llvmgcc42.roots/llvmgcc42~obj/obj- > powerpc-powerpc/./prev-gcc/xgcc

Hi Warren, You have the -m32 flag set, but it's still giving you this: > Warning: Generation of 64-bit code for a 32-bit processor requested. > Warning: 64-bit processors all have at least SSE2. But are you sure you want to compile the LLVM-GCC source? You should use the binaries unless absolutely necessary. -bw On May 24, 2007, at 10:34 PM, Warren Armstrong wrote: > Hi all,

On 2009-01-20 08:01, Bill Wendling wrote: > On Jan 19, 2009, at 5:34 PM, John Regehr wrote: > > >> Since yesterday I've been getting the error below when building llvm- >> gcc >> on Ubuntu Hardy on x86. For some reason, several instances of >> autoconf >> are getting confused and failing to detect a stdlib.h. >> >> John >>

I have been working successfully with llvm-gcc for some time now with support for c/c++. Today I tried going back and reconfiguring and rebuilding with support for fortran, and I am running into problems. It seems ld cannot find -lffi. I am configuring like this: /gro/pkg/src/llvm-gcc/configure --prefix=/pkg/bin/llvm-gcc --program-prefix=llvm- --enable-llvm=/pkg/build/llvm

I did follow the README.LLVM. I configure like: ../llvm-gcc4.2-2.4.source/configure --program-prefix=llvm- --enable-llvm=/home/wangtielei/TOOLS/llvm/llvm-obj/ --enable-language=c,c++ --disable-jit --disable-multilib The error information is /home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/xgcc -B/home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/

On Jan 19, 2009, at 5:34 PM, John Regehr wrote: > Since yesterday I've been getting the error below when building llvm- > gcc > on Ubuntu Hardy on x86. For some reason, several instances of > autoconf > are getting confused and failing to detect a stdlib.h. > > John > > > /home/regehr/z/tmp/llvm-gcc-r62547-src/build/./prev-gcc/xgcc >

I just tried to compile llvm-gcc against the top of llvm and I ran into this error: /.../llvm/llvm-gcc-build/./prev-gcc/xgcc -B/.../llvm/llvm-gcc-build/./prev-gcc/ -B/.../llvm/llvm-gcc-install/x86_64-unknown-linux-gnu/bin/ -c -DHAVE_CONFIG_H -g -O2 -I. -I/.../llvm/llvm-gcc-4.2/libiberty/../include  -W -Wall -pedantic -Wwrite-strings -Wstrict-prototypes -Wc++-compat

Since yesterday I've been getting the error below when building llvm-gcc on Ubuntu Hardy on x86. For some reason, several instances of autoconf are getting confused and failing to detect a stdlib.h. John /home/regehr/z/tmp/llvm-gcc-r62547-src/build/./prev-gcc/xgcc -B/home/regehr/z/tmp/llvm-gcc-r62547-src/build/./prev-gcc/

Hi, every body, I get stuck when trying to build llvm-gcc4.2-2.4 on x86_64 Linux with GCC-4.3.3. I meet this error: make[3]: Entering directory `/home/wangtielei/TOOLS/llvm/llvm-gcc-obj/gcc' /home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/xgcc -B/home/wangtielei/TOOLS/llvm/llvm-gcc-obj/./prev-gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings

2010/1/10 Aaron Gray <aaronngray.lists at googlemail.com> > 2010/1/10 Duncan Sands <baldrick at free.fr> > > Hi Aaron, >> >> >> Thanks, okay heres the results :- >>> >>> LLVM type size doesn't match GCC type size! >>> >>> <real_type 0x7ff80b40 long double sizes-gimplified XF size <integer_cst >>>

>> Dear All, I have been trying for days but still cannot break this barrier. May I get your help? I have compiled llvm-2.1 successfully and make install. When I proceed with llvm-gcc-4.2-2.1, however, I keep getting linking error as attached. Some functions with totally different content conflict with each other in linking process. That is a Linux box (Debian, with 2.6.23-1

Here's a working testcase: ; ModuleID = '/tmp/crtbegin.bc' target datalayout = "E-p:32:32:128-i1:8:128-i8:8:128-i16:16:128-i32:32:128-i64:32:128-f32:32:128-f64:64:128-v64:64:64-v128:128:128-a0:0:128-s0:128:128" target triple = "spu" @__dso_handle = hidden global i8* null, align 16 ; <i8**> [#uses=0] @__CTOR_LIST__ = internal global [1 x void

On Aug 15, 2009, at 5:05 PM, Erick Tryzelaar wrote: > I just tried to compile llvm-gcc against the top of llvm and I ran > into this error: > > /.../llvm/llvm-gcc-build/./prev-gcc/xgcc > -B/.../llvm/llvm-gcc-build/./prev-gcc/ > -B/.../llvm/llvm-gcc-install/x86_64-unknown-linux-gnu/bin/ -c > -DHAVE_CONFIG_H -g -O2 -I. > -I/.../llvm/llvm-gcc-4.2/libiberty/../include -W

Hi Jack, > The curent llvm svn (r54623) is unable to link the gfortran > compiler in llvm-gcc-4.2 svn. I am getting the error... ... > Undefined symbols: > "_create_init_utf16_var", referenced from: > _darwin_build_constant_cfstring in libbackend.a(darwin.o) this is probably due to recent Apple changes. Fortran builds on linux. > Why is c++ being used