search for: crosscompiling

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

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

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 process. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

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

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

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

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

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

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

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

I need to build libLLVM (individual static libraries are fine at the moment) using mingw-w64 cross compilers, i686-w64-mingw32-gcc and (separately) x86_64-w64-mingw32-gcc. I'd like this to work from both Linux and Cygwin build environments. With autotools, this worked fine: ../configure --host=i686-w64-mingw32 and that's it (with mingw32-gcc-c++ installed on Fedora 23, also works fine on

You need to configure with --enable-llvm. (It would still be nice if V1DI_pointer_node was defined; I'll take a look at that.) On May 20, 2010, at 1:04 PM, Anatoly Yakovenko wrote: > i am getting this compilation error: > > > gcc -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall > -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic >

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