search for: cross_compile

I tend to use the same tool-chain across various hosts so I made this very simple patch that allows you to pass the cross-compiler name to make ( e.g. make CROSS_COMPILE=i686-nptl-linux-gnu-). I'm not sure if patches should be attached or just pasted inline so I did both this time. BTW, it's relative to syslinux 4 but the same changes work with syslinux 3 although the patch won't apply cleanly. don ------------- diff --git a/MCONFIG b/MCONFIG index 8...

...beulich@novell.com> Index: 2007-03-19/config/StdGNU.mk =================================================================== --- 2007-03-19.orig/config/StdGNU.mk 2007-03-08 09:37:32.000000000 +0100 +++ 2007-03-19/config/StdGNU.mk 2007-03-21 14:33:40.000000000 +0100 @@ -1,7 +1,7 @@ AS = $(CROSS_COMPILE)as LD = $(CROSS_COMPILE)ld CC = $(CROSS_COMPILE)gcc -CPP = $(CROSS_COMPILE)gcc -E +CPP = $(CC) -E AR = $(CROSS_COMPILE)ar RANLIB = $(CROSS_COMPILE)ranlib NM = $(CROSS_COMPILE)nm _______________________________________________ Xen-devel maili...

Hi, I noticed sometimes ago that my 32-bit R 2.4.1 is non-MBSC/iconv capable, whereas my 64-bit R (both built locally myself, on x86_64 linux) is. I know my system is rather beefed up on any kind of CJK-related stuff, and it shouldn't be the case. So I just looked into it, and found that the configure script basically automatically assume that the system is non-iconv/MBSC capable if it looks

...xit' usr/klibc/execl.o: In function `execl': execl.c:(.text+0x80): undefined reference to `execve' usr/klibc/execle.o: In function `execle': execle.c:(.text+0x84): undefined reference to `execve ........ I am using gcc-4.4.3 toolchain. for kernel 2.6.31. My build command is: make CROSS_COMPILE=mipsel-linux- KLIBCARCH=mips KBUILD_VERBOSE=1 Googled around and saying that it might work if i disable distcc. So i added make CROSS_COMPILE=mipsel-linux- KLIBCARCH=mips KBUILD_VERBOSE=1 FEATURES="-distcc". But no difference. Any idea what caused this? Thanks chris -------------- nex...

...portage/x11-drivers/nvidia-drivers-270.41.06/ > work ... > >>> Source configured. > >>> Compiling source in > /var/tmp/portage/x11-drivers/nvidia-drivers-270.41.06/wo > rk ... > ^[[32;01m*^[[0m Preparing nvidia module > make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- > LDFLA > GS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux > SYSOUT=/lib/modules/2.6.34- > xen-r4/build HOST_CC=x86_64-pc-linux-gnu-gcc clean module > The kernel you are installing for is a Xen kernel! > > The NVIDIA driver does not currently work on Xe...

Hi I want to recompile some RPMs (my own) for x86_64 arch from my i386 compatible build host (because of hardware restriction/funds).Is anyone ever done this ? After a google search, it seems not so easy... i just found this: http://www.speedblue.org/cross_compilation/ but haven't tried it yet (i would have to convert these to RPM first). How is it done for Centos SRPMS rebuilds ? is it a

...eaders_install > > > >B) cd ~/src/klibc > > make KLIBCKERNELSRC=`pwd`/../linux/usr/ > > > > > Sorry, but without my patchs, 'make install' fails with the > following message (complete messages file attached) > > # make install V=1 KLIBCARCH=ppc CROSS_COMPILE=ppc-linux- > KLIBCKERNELSRC=/root/gen/trunk/knl/linux/usr/ > prefix=/tmp/klibc-install have you done step A previously? It seems you are not compiling against the preconfigured linux headers otherwise the headers_install wouldn't fail. -- maks

...ns on how to compile with these patches on the wiki: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling Thanks are due to Wookey who gave lots of good advice in the hackrooms at LinaroConnect last week. I consider it an outstanding bug that you need to essentially pass CROSS_COMPILE and XEN_TARGET_ARCH to both configure and make. This is hardly the only remaining annoyance in our build system though... Ian.

...king run-init. belows makes use of the exported CC var. Signed-off-by: maximilian attems <maks@sternwelten.at> diff --git a/scripts/Kbuild.klibc b/scripts/Kbuild.klibc index 66e16e7..70e4071 100644 --- a/scripts/Kbuild.klibc +++ b/scripts/Kbuild.klibc @@ -72,7 +72,7 @@ KLIBCROSS := $(CROSS_COMPILE) # binutils KLIBCLD := $(KLIBCROSS)ld -KLIBCCC := $(KLIBCROSS)gcc +KLIBCCC := $(KLIBCROSS)$(CC) KLIBCAR := $(KLIBCROSS)ar KLIBCRANLIB := $(KLIBCROSS)ranlib KLIBCSTRIP := $(KLIBCROSS)strip

Hi, I'm trying to compile linux-2.6.23.16 with llvm-2.3. Is it at all possible? I get "Not an ELF" error. I pass "-emit-llvm" option to spit LLVM IR, which can be JITed at runtime $ make CROSS_COMPILE=llvm- CFLAGS="-O2 -emit-llvm" Error: not ELF make[2]: *** [scripts/mod/elfconfig.h] Error 1 make[1]: *** [scripts/mod] Error 2 make: *** [scripts] Error 2 using the verbose option - $ make V=1 CROSS_COMPILE=llvm- CFLAGS="-O2 -emit-llvm" /bin/bash scripts/checksyscalls.sh llvm-...

...gt;>>> make KLIBCKERNELSRC=`pwd`/../linux/usr/ >>>> >>>> >>> Sorry, but without my patchs, 'make install' fails with the >>> following message (complete messages file attached) >>> >>> # make install V=1 KLIBCARCH=ppc CROSS_COMPILE=ppc-linux- >>> KLIBCKERNELSRC=/root/gen/trunk/knl/linux/usr/ >>> prefix=/tmp/klibc-install >> have you done step A previously? >> It seems you are not compiling against the preconfigured linux headers >> otherwise the headers_install wouldn't fail. >> &...

traps.i has been attached. I used 'make CROSS_COMPILE=llvm-arm-' to compile the kernel with default configurations provided by kernel package If you need more information, please let me know. Thanks, Won On Wed, Jul 8, 2009 at 3:00 PM, Bob Wilson <bob.wilson at apple.com> wrote: > Thanks for the bug report. The attached file isn't...

http://bugzilla.mindrot.org/show_bug.cgi?id=321 ------- Additional Comments From astrand at lysator.liu.se 2004-06-22 20:45 ------- Created an attachment (id=655) --> (http://bugzilla.mindrot.org/attachment.cgi?id=655&action=view) Patch to configure.ac (3.7p1) This new patch is for 3.7p1. It only modifies configure.ac; no C source. Can someone *please* apply? ------- You are

...le to install the kernel headers elsewhere and +point to them there. - It is also possible to install the kernel headers elsewhere and - point to them there. +Cross-compiling +--------------- +If you're cross-compiling, you need to set KLIBCARCH to the +appropriate architecture, and set CROSS_COMPILE to your toolchain +prefix. -b) If you're cross-compiling, you need to set KLIBCARCH to the - appropriate architecture, and set CROSS_COMPILE to your toolchain - prefix. +IMPORTANT: if you're on a 64-bit machine with a 32-bit userland +(ia64, mips64, ppc64 sparc64, s390x or x86_64), an...

Hi Ian, I try compile the bootwrapper for cubieboard2 like this: joshzhao@joshzhao-ThinkCentre-M58p:~/project/Xen/A20/boot-wrapper$ make cubieboard2_defconfig CROSS_COMPILE=arm-linux-gnueabihf- # # configuration written to .config # joshzhao@joshzhao-ThinkCentre-M58p:~/project/Xen/A20/boot-wrapper$ make CROSS_COMPILE=arm-linux-gnueabihf- make -C scripts/kconfig -f Makefile.bootwrapper silentoldconfig cd ../../ && scripts/kconfig/conf --silentoldconfig /home/jo...

...ned in the above link, which I feel is due to version difference. I am using Xen 4.3.3 version. My understanding is that due to this version difference I am not able to compile xen tools. I have produced the output below. Also I have attached my mkheader.py file for reference. ... make dist-tools CROSS_COMPILE=arm-linux-gnueabihf- XEN_TARGET_ARCH=arm32 make -C tools install make[1]: Entering directory `/Virt/xen1/xen-unstable.git-xen-arm-4.3-3-e2cb352/tools'' make[2]: Entering directory `/Virt/xen1/xen-unstable.git-xen-arm-4.3-3-e2cb352/tools'' make -C include install make[3]: Entering di...

Full_Name: Krassimir Sedmakov Version: R-1.4.1 OS: Solaris 8 Submission from: (NULL) (134.114.165.52) ******** Problem: ******** When running make for R-1.4.1 on Solaris 8, SPARC 64 bit the following error message is generated: arithmetic.c:672: #error code requires that int have 32 bits gmake[3]: *** [arithmetic.o] Error 1 gmake[3]: Leaving directory `/opt/R/R-1.4.1/src/main' gmake[2]:

...inux system "chooses" the linker, but that makes deployment and validation quite cumbersome on GNU systems. I'd like to suggest a change in behaviour: // Some flag like --linker=<full path / bin on path> if (LinkerFlag) { linker = Flag (linker); // triple != host } else if (CROSS_COMPILE) { if (LLDSupports(triple)) linker = Find (LLD); if (!linker) linker = Find (triple-ld); if (!linker) ERROR; // *NOT* the system linker! // triple = host } else { linker = Find (LLD); if (!linker) linker = Find (SYSLD); // OS-specific if (!linker) ERROR; // We tried...

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

...embly. I'm using LLVM-2.3 code snippet from "arch/x86_64/kernel/asm-offsets.c" .... #define DEFINE(sym, val) \ asm volatile("\n->" #sym " %0 " #val : : "i" (val)) .... DEFINE(__NR_syscall_max, sizeof(syscalls) - 1); return 0; # make CROSS_COMPILE=llvm- V=1 llvm-gcc -Wp,-MD,arch/x86_64/kernel/.syscall.o.d -nostdinc -isystem /home/ashish/llvm/llvm-gcc4.2-2.3.source/obj/../install/lib/gcc/x86_64-unknown-linux-gnu/4.2.1/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -emit-llvm -Wall -Wundef -Wstrict-prototypes -Wno-trigra...