> Hi chenwj, > If it use system pthread library, then it should find it in the stand search path. I also added the option "-L/usr/lib -L/usr/lib64" but it still failed.Don't know if the link below helps or not, http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-November/027274.html Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667
> According to the link, I found that during the compiling process, the option "-emit-llvm" must be added to generate immediate object *.o. > [hanfeng at os-wstation02 fft]llvm-gcc -c fft.c -emit-llvm"-emit-llvm" emits object file which contains LLVM bitcode (IR). Default file name suffix is .o, but you might want to use "-o fft.bc" to make the suffix self-explained.> Then using llvm-ld will generate two files - a shell excutable and a llvm bytecode data both of which would run perfect. > [hanfeng at os-wstation02 fft]llvm-ld -o FFT fft.o^^^ Is it not a native excutable? Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667