similar to: [LLVMdev] [Cygwin] llvm-ranlib and 'make check' errors

Does not look like the demangle test worked anyway :( And 'make check' :- $ make check make[1]: Entering directory `/usr/build/llvm-gcc/gcc' (rootme=`${PWDCMD-pwd}`; export rootme; \ srcdir=`cd /usr/cfrontend/src/gcc; ${PWDCMD-pwd}` ; export srcdir ; \ cd testsuite; \ EXPECT=expect ; export EXPECT ; \ if [ -f ${rootme}/../expect/expect ] ; then \ TCL_LIBRARY=`cd

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 :- > >

Okay, this I have no clue about. I've never done "make check" on llvm- gcc. I thought you meant "make check" on LLVM. You're into "new territory". Reid. On Thu, 2005-05-19 at 16:07 +0100, Aaron Gray wrote: > Does not look like the demangle test worked anyway :( > And 'make check' :- > > $ make check >

Hello, Everyone. This is just brief description on building llvm-gcc4 with mingw32. It's definitely non error-free and contains many "hacks", which should be eliminated in the future. 1. Prerequisites We're building in the folowing configuration: 1.1 GCC 3.4.5: gcc -v Reading specs from f:/research/mingw/bin/../lib/gcc/mingw32/3.4.5/specs Configured with:

> 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 >

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 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

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

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

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.

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

Hi! I'm trying to build LLVM under cygwin. I have the latest version of cygwin and CVS versions of llvm, llvm-test and llvm-gcc. make of tools only succeeded. make of frontend succeeded too but full make of llvm failed on crtend in llvm/runtime/GCCLibraries with the following message: llvm[0]: Compiling crtend.c for Debug build (bytecode) /bin/sh: -c: line 0: syntax error near unexpected

>which version of makeinfo are you running? 4.8 Hi Henrik, The new release 1.5 has fixed that now. I am getting through to step 9 of the CFEBuildInst instructions. But 'llvm-ranlib libiberty.a' is failing so is 'make check' :( Aaron

Hi all, We know that 'ItaniumDemangle' has been added into llvm lib to resolve demangling related issues. And if we dump mangled function name '_Z3duti' into 'char *llvm::itaniumDemangle(const char *mangled_name, char *buf, size_t *n, int *status)', we will get 'dut(int)'. So my question is: How can I just get the function name 'dut' without parameters,

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.

Hi, I am trying to build the front end llvm-gcc 2.8 on 32-bit Ubuntu 10.04, using gcc 4.2.4. I was able to configure and build llvm-2.8 in the directory llvm-2.8-build. Here is the command I used to configure llvm-gcc build: ../llvm-gcc-4.2-2.8.source/configure --enable-checking --disable-bootstrap --disable-multilib --enable-llvm=/home/ghoang/llvm-test/llvm-2.8-build/ --enable-languages=c

try --disable-libmudflap when you config llvm-gcc FE:) On Mon, Jan 16, 2012 at 9:44 AM, Giang Hoang <ghoang84 at gmail.com> wrote: > Hi, > > I am trying to build the front end llvm-gcc 2.8 on 32-bit Ubuntu 10.04, > using gcc 4.2.4.  I was able to configure and build llvm-2.8 in the > directory llvm-2.8-build.  Here is the command I used to configure llvm-gcc > build: >

Hello! We want to implement in-process symbolizer for {Address,Thread}Sanitizer testing tools that would be based on LLVM libraries. I've noticed that llvm-nm (as well as other tools) doesn't demangle C++ names. Is it true, that LLVM doesn't have the code that is capable of that, and if yes, are there any plans to add it? Depending on something like libiberty.a doesn't seem like a