search for: cross_compiling

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

Since CPP is being used with CFLAGS, it should be in lock-step with CC, to avoid having to specify both CC and CPP for the build. Signed-off-by: Jan Beulich <jbeulich@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

...quot; >&5 echo $ECHO_N "checking whether iconv() accepts \"UTF-8\", \"latin1\" and \"UCS-*\"... $ECHO_C" >&6 if test "${r_cv_iconv_latin1+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else if test "$cross_compiling" = yes; then r_cv_iconv_latin1=no else cat >conftest.$ac_ext <<_ACEOF ..... _ACEOF ============= FWIW, I am doing my "cross-compile" with a slightly more complicated version of this: LDFLAGS=-m32 CFLAGS=-m32 CPPFLAGS=-m32 CXXFLAGS=-m32 FFLAGS=-m32 \ ./configure --bu...

Hi: I downloaded klibc-1.5.17 and try to cross-compiled it for MIPS. Got following errors: usr/klibc/exit.o: In function `exit': exit.c:(.text+0x40): undefined reference to `_exit' 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

Hi, I tried to Update the Nvidia driver. But the result is a failed because it''s not for Xen Kernel. This the log > [ebuild U ] x11-drivers/nvidia-drivers-270.41.06 [260.19.36] > USE="(multilib) > -acpi -custom-cflags -gtk" 0 kB > > >>> Source > prepared. > >>> Configuring source in >

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

On Wed, Aug 21, 2013 at 01:39:50PM +0200, leroy christophe wrote: > > Le 21/08/2013 12:20, maximilian attems a ?crit : > >On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > >>Find attached two patches I have in order to build klibc 2.0.2 > >>against kernel 3.8.13 > >>We had to introduce those patches when going from kernel 3.6 to kernel 3.7

The following patches shave some rough edges off the tools build system to allow cross compiling for at least arm32 and arm64 based on the Debian/Ubuntu multiarch infrastructure. They also add the necessary fixes to build for arm64 (which I have only tried cross, not native). I have posted some instructions on how to compile with these patches on the wiki:

sparc still needs gcc-3.3 for a working 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

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

Le 21/08/2013 17:36, leroy christophe a ?crit : > > Le 21/08/2013 17:15, maximilian attems a ?crit : >> On Wed, Aug 21, 2013 at 01:39:50PM +0200, leroy christophe wrote: >>> Le 21/08/2013 12:20, maximilian attems a ?crit : >>>> On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: >>>>> Find attached two patches I have in order to build

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 helpful for > reproducing the problem.

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

Commit-ID: 72fea69b91bdc8981d958984bc78401a08f8aff5 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=72fea69b91bdc8981d958984bc78401a08f8aff5 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 1 Feb 2019 16:00:20 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 2 Feb 2019 00:09:23 +0100 [klibc] README.klibc: Replace list

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

Hi All, I am adding the patch mentioned here http://lists.xen.org/archives/html/xen-changelog/2013-02/msg00235.html I am getting errors on compiling Xen tools. My /tools/include/xen-foreign/mkheader.py looks different from the one that is mentioned 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

...arrior 6) chokes on it. 678 So for now just assume it is true. 679 */ ***Related code in configure file: 10871 if test "${ac_cv_sizeof_int}" = 4; then 10872 cat >> confdefs.h <<\EOF 10873 #define INT_32_BITS 1 10874 EOF 10875 10876 fi 10877 if test "${cross_compiling}" = yes; then 10878 warn_xcompile_sizeof_long="assuming C longs are 4 byte on ${host}" 10879 echo "configure: warning: ${warn_xcompile_sizeof_long}" 1>&2 10880 fi ********* Solution: ********* Run ./configure Ignore warnings in R-1.4.1/ directory create a fil...

Folks, I'm creating a bootstrap buildbot on AArch64 with LLD and I just realised the "accepted" way to make clang call lld is to "symlink lld -> ld". I understand that's how every Linux 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

...; ], - [ ac_cv_have_control_in_msghdr="no" ] + [ ac_cv_have_control_in_msghdr="no" ], + [ ac_cv_have_control_in_msghdr="yes" ] ) ]) if test "x$ac_cv_have_control_in_msghdr" = "xyes" ; then @@ -2115,13 +2153,14 @@ ) fi fi +if test "$cross_compiling" != yes; then AC_CHECK_FILE("/dev/ptc", [ AC_DEFINE_UNQUOTED(HAVE_DEV_PTS_AND_PTC) have_dev_ptc=1 ] ) - +fi # Options from here on. Some of these are preset by platform above AC_ARG_WITH(mantype, [ --with-mantype=man|cat|doc Set man page type], @@ -2215,15 +2254,18...

Thanks for the help. I've a couple of questions though: How does LLVM deal with inline assembly? I'm trying to compile kernel and I get this error probably because LLVM is not able to handle inline assembly. 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 "