Anatoly Yakovenko
2010-May-25 18:12 UTC
[LLVMdev] linker errors when trying to link llvm-gcc
I am trying to build a cross compiler for arm on linux, here is how i have configured it cd llvm-gcc-4.2-2.7.source-objtree ../llvm-gcc-4.2-2.7.source/configure --enable-llvm=/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-2.7 --enable-multilib --enable-target-optspace --enable-interwork --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --target=arm-elf --prefix=/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/arm-elf i've been able to build vanila gcc 4.2 to 4.5 using this configuration for arm, but not llvm. So i deleted my tree and tried again and i got these errors now: ../../llvm-gcc-4.2-2.7.source/gcc/config/arm/lib1funcs.asm: Assembler messages: ../../llvm-gcc-4.2-2.7.source/gcc/config/arm/lib1funcs.asm:1004: Error: backward ref to unknown label "8:" Thanks, Anatoly On Mon, May 24, 2010 at 12:52 PM, Duncan Sands <baldrick at free.fr> wrote:> Hi Anatoly, > >> any ideas what library has these symbols >> >> lang_eh_catch_all >> get_pointer_alignment >> validate_arglist > > it sounds like you are trying to build a version of llvm-gcc without LLVM > enabled. Did you specify --enable-llvm=path_to_llvm_build_directory when > configuring llvm-gcc? These symbols are all defined in llvm-gcc itself, > but only when ENABLE_LLVM is defined. This suggests to me that you somehow > configured llvm-gcc wrong. > > Ciao, > > Duncan. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Anton Korobeynikov
2010-May-25 19:46 UTC
[LLVMdev] linker errors when trying to link llvm-gcc
> ../llvm-gcc-4.2-2.7.source/configure > --enable-llvm=/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-2.7 > --enable-multilib --enable-target-optspace --enable-interwork > --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++ > --target=arm-elfThis means that the compiler is built for ARMv4 which is not pretty good supported. Try to switch to ARMv7, e.g. adding --with-cpu=cortex-a8. Also, LLVM might not support interworking yet, so it's worth to remove this option as well. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
Anatoly Yakovenko
2010-May-25 20:25 UTC
[LLVMdev] linker errors when trying to link llvm-gcc
thanks, that worked, also interworking built without problems. i haven't tested an elf with it yet though. On Tue, May 25, 2010 at 12:46 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote:>> ../llvm-gcc-4.2-2.7.source/configure >> --enable-llvm=/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-2.7 >> --enable-multilib --enable-target-optspace --enable-interwork >> --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++ >> --target=arm-elf > This means that the compiler is built for ARMv4 which is not pretty > good supported. > Try to switch to ARMv7, e.g. adding --with-cpu=cortex-a8. Also, LLVM > might not support interworking yet, so it's worth to remove this > option as well. > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Saint Petersburg State University >
Apparently Analagous Threads
- [LLVMdev] linker errors when trying to link llvm-gcc
- [LLVMdev] trying to build llvm-gcc for arm, error: 'V1DI_pointer_node' undeclared (first use in this function)
- [LLVMdev] trying to build llvm-gcc for arm, error: 'V1DI_pointer_node' undeclared (first use in this function)
- [LLVMdev] linker errors when trying to link llvm-gcc
- [LLVMdev] linker errors when trying to link llvm-gcc