search for: crosscompile

any ideas what library has these symbols lang_eh_catch_all get_pointer_alignment validate_arglist i get these linker errors when trying to link llvm-gcc: make[1]: Entering directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree' make[2]: Entering directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree/build-x86_64-unknown-linux-gnu/libiberty' make[2]: Entering directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/pro...

...llvm or llvm-gcc4? > 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) You mean binutils-cross, right? > during gcc build process. Building gcc as a crosscompiler is fully automized in OpenEmbedded, I'm trying to add llvm-gcc4 into that framework. regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGEBMwMkyGM64RGpERAnL+AKC4gtxNAPJetf0kOPJC2NAqF31tDwCfWmAu WiNlCu36rf5JQ+AwGs7VSMs= =LLY2 -----END PGP SIGNATURE-----

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

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: http://lists.cs.uiuc.edu/pi...

Hi folks, here're some quick+dirty fixes to allow sysroot'ed crosscompiling. probably not yet very clean, but seems to work. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: contact at metux.de

-----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 cross-compiler. So my question is: How should I build llvm and llvm-gcc4 to have it cross-compile from x86 to ARM/EABI? regards, Koen -----BEGIN PGP SIGNATURE--...

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 cross-compiler. > > So my question is: How should I build llvm and llvm-gcc4 to have it cross-compile from x86 > to ARM/EABI? For the LLVM build, j...

...e/gcc/config/arm/arm.c:17355: error: (Each undeclared identifier is reported only once ../../llvm-gcc-4.2-2.7.source/gcc/config/arm/arm.c:17355: error: for each function it appears in.) make[3]: *** [arm.o] Error 1 make[3]: Leaving directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree/gcc' make[2]: *** [all-gcc] Error 2 make[2]: Leaving directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/anatolyy/qctp406/pakman/depot...

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: err...

-----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 ARM/EABI, but llvm-gcc don't. You must apply the >...

...ot;No rule to make target 'LLVMSupport'. Stop." Full build log is at http://sprunge.us/bCUU I'd like to go with the default behavior of building a native version of TableGen, but the way that's currently set up in cmake isn't working here. I'm looking at cmake/modules/CrossCompile.cmake (and I think "toochain" on the first line is a typo?) and trying to figure out how to make its call to execute_process(COMMAND ${CMAKE_COMMAND} ...) not inherit the top-level settings for CMAKE_C_COMPILER etc from the cross build. Any ideas? I've tried moving my mingw settings f...

...error: (Each > undeclared identifier is reported only once > ../../llvm-gcc-4.2-2.7.source/gcc/config/arm/arm.c:17355: error: for > each function it appears in.) > make[3]: *** [arm.o] Error 1 > make[3]: Leaving directory > `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree/gcc' > make[2]: *** [all-gcc] Error 2 > make[2]: Leaving directory > `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree' > make[1]: *** [all] Error 2 > make[1]: Leaving directory > `/home...

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

-------------- next part -------------- A non-text attachment was scrubbed... Name: speex.mingw.patch__charset_ISO-8859-15 Type: text/x-patch Size: 1490 bytes Desc: speex.mingw.patch__charset_ISO-8859-15 Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20040212/51b4c2a9/speex.mingw-0001.bin

according to my little knowledge about automake, its not possible to put variables in _SOURCES. so something like speexdec_SOURCES = speexdec.c wav_io.c $(WIN32_OBJ) is not possible. but than i looked into wave_out.c and the entire source is surrounded by #if defined WIN32 || defined _WIN32 so it will just disappear than build on linux. j On Fri, 2004-02-13 at 07:59, Jean-Marc Valin wrote: >

Hello, I see that in 6.04-pre3 there is some support for host and target gcc. However, build always fails when using a cross-compiler: [ 89s] + make CC=x86_64-suse-linux-gcc CC_FOR_BUILD=gcc ... [ 401s] objcopy --strip-debug --strip-unneeded libutil.elf libutil.c32 [ 401s] x86_64-suse-linux-gcc -I/home/abuild/rpmbuild/BUILD/syslinux-6.04~pre3+git3.05ac953c/com32/libutil/include -W -Wall -O

> > - 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.

Hi, I am trying to use LLVM on x86 with some code intended for another architecture (IBM Cell). The plan is: 1. foreach $c_files llvm-gcc -emit-llvm -c -o $bc_file $c_file 2. link $bc_files 3. run my passes with 'opt' 4. llc -march=c 5. cell_cc The original code is for the Cell, and uses altivec intrinsics. However, llvm-gcc complains about not recognizing them. I read that