search for: xianai

...) contains inline asm so cannot be compiled by gcc-3.4 frontend. So I decided to firstly link together the llvm objects and libcrtend and compile it to native .o file and then link it with sysdeputil.o . The Makefile is sth like this: vsftpd: $(OBJS) gccld -r -native -o vsftpd.o $(OBJS) -L/home/xianai/my_projects/llvm/cfrontend/x86/llvm-gcc/lib/ -lcrtend gcc -o vsftpd vsftpd.o sysdeputil.o `./vsf_findlibs.sh` But the gcc/ld still cannot find the reference to __main. Do I have to compile crtend to native to solve this problem? -- Regards, Nai

On Fri, 2 Jun 2006, Nai Xia wrote: > The Makefile is sth like this: > > vsftpd: $(OBJS) > gccld -r -native -o vsftpd.o $(OBJS) -L/home/xianai/my_projects/llvm/cfrontend/x86/llvm-gcc/lib/ -lcrtend > gcc -o vsftpd vsftpd.o sysdeputil.o `./vsf_findlibs.sh` > > > But the gcc/ld still cannot find the reference to __main. > Do I have to compile crtend to native to solve this problem? gccld -r doesn't work with -nativ...

...her users, maybe it deserves its place in FAQ or in man page for LLVM. On Friday 02 June 2006 13:13, Chris Lattner wrote: > On Fri, 2 Jun 2006, Nai Xia wrote: > > The Makefile is sth like this: > > > > vsftpd: $(OBJS) > > gccld -r -native -o vsftpd.o $(OBJS) -L/home/xianai/my_projects/llvm/cfrontend/x86/llvm-gcc/lib/ -lcrtend > > gcc -o vsftpd vsftpd.o sysdeputil.o `./vsf_findlibs.sh` > > > > > > But the gcc/ld still cannot find the reference to __main. > > Do I have to compile crtend to native to solve this problem? > > gc...

I run "./configure" with CC=llvm-gcc and got no errors. When compiling, the llvm-gcc complained about "-lcposix" not found and unrecognized option `-rdynamic'. So I eliminated -lcposix from "LIBS" and replaced -rdynamic with --export-dynamic and got a bash.bc with no errors. However, after I run "lli bash.bc" it terminated with error message below:

On Friday 14 April 2006 13:26, you wrote: > On Fri, 14 Apr 2006, xia_nai at yahoo.com.cn wrote: > >> Have you tried compiling bash with a native GCC then running it through > >> valgrind? > > > > The native compiled bash can run properly, but valgrind detect memory errors with the error summary > > below: > > This is probably a bug in bash or

Hi, I recently bootstrapped gcc4 frontend on a i686-linux-gnu too. As I notice, if the llvm "tools-only " was build with srcdir != objdir , the building of llvm-gcc4-1.7.source encountered mistakes of unable to find some header files. So I just edited llvm-gcc4-1.7.source/gcc/Makefile.in and a line like this: INCLUDES += -I$(LLVMOBJDIR)/include With this change, the building errors