similar to: [LLVMdev] Errors reported in config.log on linux

I tried CC=gcc44 CXX=g++44 ../llvm/configure and got CC=gcc44: Command not found So the syntax is indeed as wriiten in the help. Sitvanit Ruah Formal Verification Group IBM Haifa Research Laboratory Tel: 972-4-828-1249 From: Duncan Sands <baldrick at free.fr> To: Sitvanit Ruah/Haifa/IBM at IBMIL, Cc: Konstantin Tokarev <annulen at yandex.ru>, llvmdev at cs.uiuc.edu,

Hi Sitvanit, On 12/07/12 22:18, Sitvanit Ruah wrote: > I ran "configure -help " and it says > > usage: configure [OPTION]..... [VAR=VALUE] > > So I assume configure CC=... is the right syntax. Isn't it? while you might think so, try it the other way round. Also, by doing make VERBOSE=1 you can see which compiler is really being used. Ciao, Duncan. > >

Ok, I got. You should install libstdc++44-devel, too. Please try to install gcc44-c++ and libstdc++44-devel. Note: gcc44-c++ depends on gcc44, but gcc44-c++ and libstdc++44-devel are independent each other, at least on my host, CentOS5. ...Takumi 2012/7/15 Sitvanit Ruah <RUAH at il.ibm.com>: > In order to isolate the problem I am now running on a machine whose only > installation

In order to isolate the problem I am now running on a machine whose only installation of gcc/g++ is gcc44, g++44 For this installation I am getting the following error: COMPILE: clang_linux/asan-i386/i386: /gpfs/haifa-p4/00/pincette/sitvanit/LLVM/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc /.../sitvanit/LLVM/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:19:10: fatal error:

Hi Sitvanit, > I tried > > CC=gcc44 CXX=g++44 ../llvm/configure > > and got > > CC=gcc44: Command not found > > So the syntax is indeed as wriiten in the help. actually, no, this just means that you are using a shell that doesn't support this syntax. What shell are you using? Try export CC=gcc44 export CXX=g++44 ../llvm/configure Ciao, Duncan. >

What is the best level to use for backend development? We do not need to generate machine code, but rather an intermediate representation that will give us the control flow graph. Is this the llvm IR? If so, how do I read into memory a file that was generated by clang++ -emit-llvm <source file>. Thanks, Sitvanit Sitvanit Ruah Formal Verification Group IBM Haifa Research Laboratory Tel:

I ran "configure -help " and it says usage: configure [OPTION]..... [VAR=VALUE] So I assume configure CC=... is the right syntax. Isn't it? Regard, Sitvanit From: Konstantin Tokarev <annulen at yandex.ru> To: Sitvanit Ruah/Haifa/IBM at IBMIL, Cc: llvmdev-bounces at cs.uiuc.edu, llvmdev at cs.uiuc.edu, Duncan Sands <baldrick at free.fr> Date:

Hello all, I am new to this mailing list so I hope this is the right place to post the following question. We are considering using Clang front end for our tool. I tried to compile LLVM (using configure followed by make from the llvm top directory) on LINUX X86 with gcc 4.1.2. I got several compilation error messages of the form /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+

It's undocumented FAQ, if you are using RHEL5 (or clone). - install gcc44-c++ - Build with CC=gcc44 CXX=g++44 - You may need "CC=clang -std=gnu89" to use clang with its glibc. Have fun! ps. AFAIK, clang can be built more easily on centos6. ...Takumi 2012/7/11 Sitvanit Ruah <RUAH at il.ibm.com>: > > Hello all, > I am new to this mailing list so I hope this is

Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. #!/bin/bash -ev export LD=`xcode-select -print-path`/usr/bin/ld xcode-select -print-path ulimit -s `ulimit -s` ulimit -s mv ../clang-2.8 ./tools/clang mkdir ../llvm_objdir cd ../llvm_objdir ../llvm-2.8/configure --prefix=/sw --prefix=/sw --mandir=/sw/share/man --infodir=/sw/share/info --with-gmp=/sw

Hi Jack, I didn't get this error. Could you try again? Is it one of the release candidates in particular that's failing? -bw On Oct 2, 2010, at 8:04 AM, Jack Howarth wrote: > Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. > > #!/bin/bash -ev > export LD=`xcode-select -print-path`/usr/bin/ld > xcode-select -print-path > ulimit -s

PS: Do you actually have gcc-4.4 installed and in your path? What do the commands gcc44 -v and g++44 -v output? On 15/07/12 10:59, Duncan Sands wrote: > Hi Sitvanit, > >> I tried >> >> CC=gcc44 CXX=g++44 ../llvm/configure >> >> and got >> >> CC=gcc44: Command not found >> >> So the syntax is indeed as wriiten in the help. >

Thanks for the information. I am running on a machine on which gcc44 is installed but whose default installation is 4.1.2. I ran ../llvm/configure CC=gcc44 CXX=g++44 make and still got the same error (I checked and CC=gcc44 and CXX=g++44 now in build/Makefile.config).. I tried also ../llvm/configure CC=gcc44 CXX=g++44 --include_dir=<gcc44 include dir> but it didn't help

Eric Christopher <echristo at apple.com> writes: >>> Or cleanup both headers from unused stuff by Eric's >>> suggestion? >> >> I'm not sure this is a good idea (not that it is bad either). Murphy's >> Law says that a function that you remove today will be used tomorrow. > > I meant literally functions that aren't used in the

> Hi all, > After reading the documentation on clang I still have the following > question: > How do I read the bitcode generated by clang from a C++ file? I need to > have all the AST information in memory. AST has nothing to do with LLVM bitcode. -- Regards, Konstantin

On Jan 5, 2011, at 6:34 AM, Óscar Fuentes wrote: > arrowdodger <6yearold at gmail.com> writes: > >>> Or to say it with other words: patches welcome. >> >> So, how should i proceed? Make CMake-generated config to be identical to >> autotools one? > > That would be a good thing. > > Please note that some checks are a bit tricky. A function that

> Yes, it is the same error referring to 4.1.2. > > /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+ > +/4.1.2/i386-redhat-linux/bits/gthr-default.h:114:1: error: weakref > declaration must have internal > linkage > __gthrw(pthread_key_delete) > > There are several such errors. Are you sure you are usin gcc44? Don't you need to run CC=gcc44 CXX=g++44

Hello: Encountered a problem installing R on CentOS release 5.2 This is a 64bit OS I need to know if this will work on this server or do I need to change OS> Thanks Bob I downloaded the source ( R-2.8.1.tar.gz ) due to no release being available for CentOS. My ./configure --with-x=no --with-readline=no R_PAPERSIZE='letter' Failed: ./configure --with-x=no --with-readline=no

I am consistently getting "libtalloc.so.1: No such file or directory" when attempting to 'make' any version of samba. I've tried all of the suggestions from the list archives on this subject. Using Solaris 9 sparc. Current versions are: gcc 3.4.6 (sunfreeware pkg) samba-3.2.11 (and any other version of samba I try) Admittedly - compiling from source is not

Here is the config.log : <p>----------------------------------------------------------- This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by configure, which was generated by GNU Autoconf 2.57. Invocation command line was $ ./configure --prefix=/home/Darkmeteor --with-ogg-prefix=/home/Darkmeteor