[LLVMdev] LLVM-gcc for ARM
Misha Brukman
brukman at gmail.com
Thu Jan 28 11:53:32 PST 2010
We have had a script for a while that does this for you in
http://llvm.org/svn/llvm-project/llvm/trunk/utils/crosstool/ARM/ .
It also uses the CodeSourcery toolchain so it saves you some effort.
Does that work for you?
On Mon, Jan 18, 2010 at 2:52 PM, Viktor Kutuzov
<vkutuzov at accesssoftek.com>wrote:
> Hello Corina,
>
> I used a two-stage sequence to build the llvm and llvm-gcc with the
> codesourcery toolchain and my custom built arm toolchain. There is some
> scripted chunks for each step. I have attached them as a single file to this
> email. May be it will help you somehow.
>
> Viktor.
>
> ---
> From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] On Behalf
> Of corina s [corina_fff at yahoo.com]
> Sent: Friday, January 15, 2010 12:54 PM
> To: llvmdev at cs.uiuc.edu
> Subject: [LLVMdev] LLVM-gcc for ARM
>
>
> Hello,
>
> I am building llvm-gcc4.2-2.6 for ARM target.
> I used the next command line option:>>../configure
> --enable-languages=c,c++ --enable-checking --target=arm-eabi>> and then>>
> make target_alias=arm-eabi>>And then I obtain the following error:In file
> included from ../../gcc/config/arm/arm.c:59:./../../libcpp/internal.h: In
> function ‘ufputs’:./../../libcpp/internal.h:693: warning: implicit
> declaration of function ‘fputs_unlocked’../../gcc/config/arm/arm.c: At top
> level:../../gcc/config/arm/arm.c:514: error: ‘MASK_INTERWORK’ undeclared
> here (not in a function)../../gcc/config/arm/arm.c: In function
> ‘optimization_options’:../../gcc/config/arm/arm.c:23444: warning: unused
> parameter ‘level’What would be the problem?It is OK
> the configure line? Thanks,Corina
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100128/85b1b39e/attachment.html>
More information about the llvm-dev
mailing list