Thanks Dan. Actually, I added the llvm-gcc to the path: export
PATH=$PATH:${LLVM_GCC}/bin/llvmcI downloaded LLVM-GCC from http://llvm.org/releases/2.9/llvm-gcc4.2-2.9-x86_64-linux.tar.bz2 and extracted. The strange thing is the binary nameis llvmc, not llvm-gcc. Is it right? --Haihao On Fri, Aug 17, 2012 at 6:59 PM, Delcypher <[email protected]> wrote: > Hi, > > You have not followed the build instructions correctly. "*Forgetting to > add llvm-gcc to your PATH at this point is by far the most common source of > build errors reported by new users."* > > Your problem comes from the fact that when you built LLVM-2.9 the program > "llvm-gcc" was not in your PATH variable. > > If you look at the file "Rules.mak" in your uclibc-klee build directory > you will see the line... > > CC = $(LLVMGCC) --emit-llvm $(KLEE_CFLAGS) > > In your case $(LLVMGCC) is empty because it is set to nothing in > "Makefile.config" file in the your LLVM build directory. > > Make sure llvm-gcc is in your PATH and then rebuild LLVM-2.9 and then > uclibc-klee should compile correctly. > > Regards, > Dan. > > > > > On 16 August 2012 19:03, haihao shen <[email protected]> wrote: > >> Hi, >> >> When I build uClibc and got the following errors: >> >> extra/scripts/gen_bits_syscall_h.sh: line 30: --emit-llvm: command not >> found >> extra/scripts/gen_bits_syscall_h.sh: line 26: --emit-llvm: command not >> found >> CC libcrypt/crypt.os >> /bin/sh: --emit-llvm: command not found >> make: *** [libcrypt/crypt.os] Error 127 >> >> Actually, I can successfully compile LLVM-2.9. Does anyone know how to >> solve it? >> >> Thanks, >> Haihao >> >> >> >> _______________________________________________ >> klee-dev mailing list >> [email protected] >> http://keeda.Stanford.EDU/mailman/listinfo/klee-dev<http://keeda.stanford.edu/mailman/listinfo/klee-dev> >> >> >
_______________________________________________ klee-dev mailing list [email protected] http://keeda.Stanford.EDU/mailman/listinfo/klee-dev
