search for: llvmgcc_lang

> LLVM tools and LLVM-GCC I've built seem to work. > Can it be due to LLVM_SRC_ROOT == LLVM_OBJ_ROOT? No. This is usually due to absence of llvm-gcc. You need reconfigure llvm once again with lvm-gcc path added and make sure it was hooked properly (look into Makefile.config for paths, etc). -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

...alled properly. From Makefile.config: LLVMGCC := /usr/local/bin/llvm-gcc.exe LLVMGXX := /usr/local/bin/llvm-g++.exe LLVMCC1 := /usr/local/libexec/gcc/i686-pc-cygwin/4.2.1/cc1.exe LLVMCC1PLUS := /usr/local/libexec/gcc/i686-pc-cygwin/4.2.1/cc1plus.exe LLVMGCC_VERSION := 4.2.1 LLVMGCC_MAJVERS := 4 LLVMGCC_LANGS := c,c++ It looks to me that this: make[4]: *** No rule to make target `Output/sse.expandfft.linked.rbc', needed by `Output/sse.expandfft.linked.bc'. Stop. means that make is trying to build this (from Makefile.programs): # Given an unoptimized bytecode file that is a simple linkage o...

...wn-linux-gnu/4.2.1/cc1plus' LLVMCC_OPTION='llvm-gcc' LLVMGCC='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCCOMMAND='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCDIR='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/..' LLVMGCC_LANGS='c,c++,fortran' LLVMGXX='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-g++' LLVMGXXCOMMAND='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-g++' LLVM_BINDIR='/home/qali/install/llvm-2.8-ori/bin' LLVM_CONFIGTIME='Wed Jan 19 10:22:57 HKT 2011'...

...- llvmgcclangs=`"$LLVMGCC" -v --help 2>&1 | grep '^Configured with:' | sed 's/^.*--enable-languages=\([^ ]*\).*/\1/'` + llvmgcclangs=`$LLVMGCC -v --help 2>&1 | grep '^Configured with:' | sed 's/^.*--enable-languages=\([^ ]*\).*/\1/'` LLVMGCC_LANGS=$llvmgcclangs LLVMGCC_DRAGONEGG=$llvm_cv_llvmgcc_dragonegg

...39;-flat-namespace' LEX='' LEXLIB='' LEX_OUTPUT_ROOT='' LIBADD_DL='' LIBOBJS='' LIBS='' LIBTOOL='' LINKALL='-Wl,-all_load' LLVMCC1='' LLVMCC1PLUS='' LLVMGCC='' LLVMGCCDIR='' LLVMGCCLIBEXEC='' LLVMGCC_LANGS='' LLVMGCC_MAJVERS='' LLVMGCC_VERSION='' LLVMGXX='' LLVM_BINDIR='' LLVM_CONFIGTIME='' LLVM_COPYRIGHT='Copyright (c) 2003-2008 University of Illinois at Urbana-Champaign.' LLVM_CROSS_COMPILING='' LLVM_DATADIR='' LLVM_DOCSDIR=...

After following all steps from http://llvm.org/docs/TestingGuide.html#testsuiterun, I've got this: make[1]: Entering directory `/cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/projects/test-suite/SingleSource' make[2]: Entering directory `/cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/projects/test-suite/SingleSource/UnitTests' make[3]: Entering directory

On 11/08/2010 03:18 PM, Duncan Sands wrote: > Hi Tobias, > >> I am very interested in using dragonegg as a fortran frontend for the >> LLVM test >> suite, as a start to improve fortran support. >> >> I believe this should be easy, but when I looked into this I had the >> impression >> the nightly tester in the llvm test-suite does not even support

...; LEX_OUTPUT_ROOT='' > LIBADD_DL='' > LIBOBJS='' > LIBS='' > LIBTOOL='' > LINKALL='-Wl,-all_load' > LLVMCC1='' > LLVMCC1PLUS='' > LLVMGCC='' > LLVMGCCDIR='' > LLVMGCCLIBEXEC='' > LLVMGCC_LANGS='' > LLVMGCC_MAJVERS='' > LLVMGCC_VERSION='' > LLVMGXX='' > LLVM_BINDIR='' > LLVM_CONFIGTIME='' > LLVM_COPYRIGHT='Copyright (c) 2003-2008 University of Illinois at > Urbana-Champaign.' > LLVM_CROSS_COMPILING=''...

...wn-linux-gnu/4.2.1/cc1plus' LLVMCC_OPTION='llvm-gcc' LLVMGCC='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCCOMMAND='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCDIR='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/..' LLVMGCC_LANGS='c,c++,fortran' LLVMGXX='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-g++' LLVMGXXCOMMAND='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-g++' LLVM_BINDIR='/home/qali/install/llvm-2.8-ori/bin' LLVM_CONFIGTIME='Wed Jan 19 10:22:57 HKT 2011'...

*1. I have searched the access/setting of LLVMCC_EMITIR_FLAG in the build directory, recursively, and all the output is what I pasted in last email (just the same to the that in source directory). Maybe the configure failed to do it. My command list for building the test suit is as followings:* *(1) cd ~/SRC_DIR/llvm/projects* *(2) svn co http://llvm.org/svn/llvm-project/test-suite/trunk