search for: libiberti

On 2008-10-01 17:36, Duncan Sands wrote: >> It builds here (Linux x86_64), I use the following configure line: >> ../llvm-gcc4.2/configure >> --prefix=/home/edwin/llvm-svn/obj42/../install --program-prefix=llvm- >> --enable-llvm=/home/edwin/llvm-svn/llvm/ --disable-multilib >> --enable-checking=release --enable-languages=c,c++ >> > > I'm using

> It builds here (Linux x86_64), I use the following configure line: > ../llvm-gcc4.2/configure > --prefix=/home/edwin/llvm-svn/obj42/../install --program-prefix=llvm- > --enable-llvm=/home/edwin/llvm-svn/llvm/ --disable-multilib > --enable-checking=release --enable-languages=c,c++ I'm using (x86-64 linux, gcc 4.3) ../gcc-4.2.llvm/configure --prefix=/usr/local/gnat-llvm

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/

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 >

Hello people. Somewhat hardheaded, and after doing so for years without problems, I started to compile wine 1.2 for my 86_64 system. Configuration went well, but compilation aborted on: make[1]: Entering directory `/home/jcoppens/wine-1.2/tools/widl' gcc -m32 -g -O2 -o widl client.o expr.o hash.o header.o proxy.o server.o typegen.o typelib.o typetree.o utils.o widl.o write_msft.o

Hello, Since 2.5 is near, I have been trying to build llvm and llvm-gcc for MingW, but hit several problem (using the current trunk). First issue is that unittests don't build for MingW, the attached patch should fix it. Second issue is that llvm-gcc fails for me with the following error: /c/cygwin/home/jlerouge/buildbot/llvm-test/gcc-build/./gcc/xgcc

So, I'm trying to build everything from source for the Debian package for LLVM, including the C/C++ front end. I'm running this build on LLVM 1.4 source (the released tarball), using Debian unstable (gcc 3.3.5, on a 2.6.8 kernel, on an x86_64 box, dual CPU). Before I get _too_ deep into it, I thought I would ask if the following compilation failure on the CFE looks the least bit familiar

Hi , I needed to apply this patch to get the GCC frontend building on an FC5 x86 box . [ramana at venglathur gcc]$ svn diff Index: libiberty/strsignal.c =================================================================== --- libiberty/strsignal.c (revision 254) +++ libiberty/strsignal.c (working copy) @@ -557,8 +557,8 @@ void psignal (signo, message) - unsigned signo; -

Anyone else seeing this? LLVM/gcc-4.2.llvm-objects/./gcc/xgcc -BLLVM/gcc-4.2.llvm-objects/./gcc/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/bin/ -B/usr/local/gnat-llvm/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/include -isystem /usr/local/gnat-llvm/x86_64-unknown-linux-gnu/sys-include -c -DHAVE_CONFIG_H -O2 -g -O2 -I.

Hi, I installed the cfrontend 1.5 and LLVM 1.5 from source in cygwin successfully using GCC3.4.3 and binutils2.15 (as in makefiles do not complain errors except some warnings). However when I do this, there are some errors like, *************************************************************** u0201201 at 9nnvf2ay /home/cfrontend/install/lib $ llvm-ranlib libiberty.a llvm-ranlib: Error opening

Thank you, I did try that and got the following error: checking for library containing strerror... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES. make[1]: *** [configure-target-libiberty] Error 1 make[1]: Leaving directory `/home/ghoang/llvm-test/llvm-gcc-2.8-build' make: *** [all] Error 2 I also tried adding --disable-libiberty but make would fail even earlier

How to solve this problem? $ make make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty' make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/tmp/llvm3/llvm/build/libiberty/testsuite' make[1]: Leaving directory `/tmp/llvm3/llvm/build/libiberty' make[1]: Entering directory

Hi, Got everything built but am now experiencing new errors on making the symbol tables and on 'make check'. Here's the errors I am experiencing :- Aaron Gray at AMD-LAPTOP-1 /usr/llvm-gcc/lib $ ls gcc libdummy.a libiberty.a libstdc++.a libsupc++.la libc.a libgcc.a libm.a libstdc++.la libtrace.a libcrtend.a libgcsemispace.a

On Sat, 23 Dec 2006, Roman wrote: > How to solve this problem? Java isn't supported. Use --enable-languages=c,c++ -Chris > $ make > make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty' > make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory

Aaron, Could you send me the libiberty.a file? Please gzip it. I would like to make sure this isn't an llvm-ranlib bug. Thanks, Reid. On Thu, 2005-05-19 at 15:36 +0100, Aaron Gray wrote: > Hi, > > Got everything built but am now experiencing new errors on making the > symbol tables and on 'make check'. > > Here's the errors I am experiencing :- > >

yes, so this happens on anything that uses a struct for va_list (like alpha). I am currently working on fixing this. if you look at the last patch to the alpha portion of llvm-gcc, you can see a quick hack to work around that (aka, get it to compile), but the resultant compiler will have issues with varargs. Alternately, build ia-32 binaries on x86_64, llvm-gcc is happy with the the abi there.

On Tue, 2006-08-01 at 15:48 +0400, Anton Vayvod wrote: > If you're building llvm-gcc4, you don't need the runtime > libraries, so > I'd just stick with the "tools-only" build and declare > success. If > you're building llvm-gcc3, I'd suggest you switch to > llvm-gcc4 :) > > I switched to

Hi, Last night's attempt to build llvmgcc4 with svn head ends in this . This is on an x86 FC5 environment. /home/ramana/llvm/llvmgccfrontend/llvmgcc4-source/build-llvmgcc/gcc/xgcc -B/home/ramana/llvm/llvmgccfrontend/llvmgcc4-source/build-llvmgcc/gcc/ -B/home/ramana/llvm/install-llvm/i686-pc-linux-gnu/bin/ -B/home/ramana/llvm/install-llvm/i686-pc-linux-gnu/lib/ -isystem

If you're building llvm-gcc4, you don't need the runtime libraries, so I'd just stick with the "tools-only" build and declare success. If you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :) However, the problem appears to be your PATH variable. In your path you have the following directory: C:/Program Files/Microsoft DirectX SDK (June

Problem 2: Configure: ../src/configure --prefix=/tmp/llvm/install --disable-threads --disable-nls --disable-shared --enable-languages=c,c++ --disable-c-mbchar --program-prefix=llvm- $ make make[1]: Entering directory `/tmp/llvm3/llvm/build/libiberty' make[2]: Entering directory `/tmp/llvm3/llvm/build/libiberty/testsuite' make[2]: Nothing to be done for `all'. make[2]: Leaving