similar to: [LLVMdev] Using LLVM as a crosscompiler

On Sun, 2007-04-01 at 21:26 +0200, Koen Kooi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > After hearing Chris' talk at bossaconference I wanted to see if I could use LLVM (and/or > llvm-gcc) as a crosscompiler for ARM. The documentation beautifully outlines how to build > it for your host and how to crosscompile it, but not how to build it as a

Hello, Koen. > So my question is: How should I build llvm and llvm-gcc4 to have it cross-compile from x86 > to ARM/EABI? Well, just supply appropriate --host/--target options to configure. I haven't tried ARM, but this definitely works for crosscompiling from linux to mingw32. Please also note, that you'll need native (=arm) tools (binutils, libcheaders, etc) during gcc build

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anton Korobeynikov schreef: > Hello, Koen. > >> So my question is: How should I build llvm and llvm-gcc4 to have it cross-compile from x86 >> to ARM/EABI? > Well, just supply appropriate --host/--target options to configure. To llvm or llvm-gcc4? > I haven't tried ARM, but this definitely works for crosscompiling from

Hi Koen, The process to build llvm-gcc as a crosscompiler is basically the same as build a normal gcc as crosscompiler. The differences: you need a LLVM installed (compiled for the host). You must configure llvm-gcc with --enable-llvm. Problems: - Today LLVM supports ARM/EABI, but llvm-gcc don't. You must apply the patch:

All, There's been much email traffic and discussion about the repository layout, top level stuff, etc. Additionally, Tanya, Chris, Gordon and I had an IRC discussion last evening and worked through some of the issues and confusion. As a result, I've prepared a web page that contains the proposals and decisions we made. Hopefully this will reduce the confusion surrounding this topic.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Reid Spencer schreef: > All, > > There's been much email traffic and discussion about the repository > layout, top level stuff, etc. Additionally, Tanya, Chris, Gordon and I > had an IRC discussion last evening and worked through some of the issues > and confusion. As a result, I've prepared a web page that contains the >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lauro Ramos Venancio schreef: > Hi Koen, > > The process to build llvm-gcc as a crosscompiler is basically the same > as build a normal gcc as crosscompiler. The differences: you need a > LLVM installed (compiled for the host). You must configure llvm-gcc > with --enable-llvm. > > Problems: > - Today LLVM supports

Hi, well, I downloaded the head revision of llvm and llvm-gcc. As you said it hangs at: Formal argument #0 has unhandled type f32 /home/julio/trunk/llvm-gcc/gcc/libgcc2.c:1765: internal compiler error: Abortado Please submit a full bug report, with preprocessed source if appropriate. Actually, I don't need fp, there is any way to disable? By the way, I'm working with a MIPS coprocessor

Hi, I was trying to crosscompile dovecot, but I got some error: --with-notify=inotify don't work, as it try to run a test program to verify if inotify is supported in the building platform. Solved with --with-notify=dnotify. Ihmo, is more a hack than a solution. | checking whether posix_fallocate() works... configure: error: cannot run test program while cross compiling I can't

> > - Today LLVM supports ARM/EABI, but llvm-gcc don't. You must apply the > > patch: > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070319/046070.html > > That doesn't apply anymore :( You must use the llvm-gcc4 from the svn. It has some bug fixes that are important to ARM EABI and the patch should apply cleanly. Lauro

Hello > grep llvm configure* doesn't return anything in trunk/, did I > checkout[1] the wrong svn? No. It's ok :) It's just complicated nature of gcc's build system. In fact, try "grep llvm gcc/configure" :) -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hello > But I got the followings errors: > > /var/folders/7f/7fiRIEm-FruFfT7mGbk3uk+++TI/-Tmp-//ccDFjySd.s: > Assembler messages: > /var/folders/7f/7fiRIEm-FruFfT7mGbk3uk+++TI/-Tmp-//ccDFjySd.s:96: Correct. You haven't specified any ARM specific stuff during llvm-gcc conffigure (cpu type, fpu type, floating point abi, etc). This means that default will be used. LLVM defaults to

Hello, Pazzo > Any clue? Yes. Sorry, my fault - next time I should check ARM docs before replying. ARM7TDMI is ARMv4T and this is not supported by LLVM (LLVM does v5+ codegen). -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello, Pazzo > I had a look to llvm (2.6) configure options but I couldn't find any > way to specify cpu type, fpu ecc.. These are not llvm configure options, but gcc's one. Basically, you should configure llvm-gcc in the same way you do for gcc for your platform. > Could you please give me any > indication and/or example? I want to try llvm with Atmel's > AT91SAM7X256

Dear ML, I'm trying to understand how to build a llvm (2.6) cross compiler for arm-elf target using the gcc frontend with newlib. Could you please indicate, if possible steps I should follow? I try to configure and build llvm with ../llvm-2.6/configure --prefix=/usr/local/cross-llvm-gcc-arm-elf-4.2-2.6 --enable-optimized --disable-threads --enable-targets=cbe,cpp,arm and LLVM-GCC frontend

Dear ML, Anton, Thank you for your answer and your help. I had a look at ARM.td of LLVM 2.6 (in lib/Target/ARM..) where I found following definitions: // V4T Processors. def : ProcNoItin<"arm7tdmi", [ArchV4T]>; def : ProcNoItin<"arm7tdmi-s", [ArchV4T]>; def : ProcNoItin<"arm710t", [ArchV4T]>; def :

i am getting this compilation error: gcc -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../llvm-gcc-4.2-2.7.source/gcc -I../../llvm-gcc-4.2-2.7.source/gcc/.

Dear Anton, Thank you again for your help! I tried with the following options (adding --with-cpu=arm7tdmi and using binutils from cvs snapshot): ../llvm-gcc4.2-2.6.source/configure --prefix=/usr/local/cross-llvm-gcc-arm-elf-4.2-2.6 --program-prefix=llvm- --enable-llvm=/Users/dummy/Develop/llvm/llvm-build --enable-languages=c,c++ --host=i686-apple-darwin9 --build=i686-apple-darwin9

Hi,    I use the crosstool build script to build a crosscompiler for ARM. I get the following error when compilng "helloworld" program:   llvm-gcc hello.c -o hello   as: unrecognized option `-meabi=4'   I know that the reason is not to get proper cross assembler. It tries to use the native assembler but I am unable to fix the problem. I use llvm-gcc -### hello.c -o hello and see

Dear Anton, Thanks for your help! I had a look to llvm (2.6) configure options but I couldn't find any way to specify cpu type, fpu ecc..Could you please give me any indication and/or example? I want to try llvm with Atmel's AT91SAM7X256 (core is ARM7TDMI ) Thank you again, pz 2010/1/9 Anton Korobeynikov <anton at korobeynikov.info>: > Hello > >> But I got the