Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Xen>
  3. ARM
[help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git
chysun2000 at 163
Jan 30, 2012, 10:01 PM
Post #1 of 10 (4384 views)
Permalink
Hi experts,

I am interested in XEN for ARM. I am trying to compile the unstable source which I cloned from this repository, sstabellini/xen-unstable.git and the branch is arm-v6.

The environment is ubuntu-10.04 LTS. The cross-compiler for arm is downloaded from codesourcery, the version : arm-2011.09.

My steps:
1) export XEN_COMPILE_ARCH=arm
2) CROSS_COMPILE=arm-none-eabi- make xen
The error message is the following:
---
make[4]: Entering directory `/home/frank/workspace/xen/src/xen-arm-v6/xen/common'
arm-none-eabi-gcc -O1 -fno-omit-frame-pointer -marm -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/frank/workspace/xen/src/xen-arm-v6/xen/include -msoft-float -fno-stack-protector -fno-exceptions -Wnested-externs -DGCC_HAS_VISIBILITY_ATTRIBUTE -march=armv7-a -mcpu=cortex-a15 -fno-optimize-sibling-calls -g -D__XEN__ -include /home/frank/workspace/xen/src/xen-arm-v6/xen/include/xen/config.h -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD -MF .version.o.d -c version.c -o version.o
make -f /home/frank/workspace/xen/src/xen-arm-v6/xen/Rules.mk -C libelf built_in.o
make[5]: Entering directory `/home/frank/workspace/xen/src/xen-arm-v6/xen/common/libelf'
arm-none-eabi-ld -marmelf_linux_eabi -r -o libelf-temp.o libelf-tools.o libelf-loader.o libelf-dominfo.o
arm-none-eabi-ld: unrecognised emulation mode: armelf_linux_eabi
Supported emulations: armelf
make[5]: *** [libelf-temp.o] Error 1
make[5]: Leaving directory `/home/frank/workspace/xen/src/xen-arm-v6/xen/common/libelf'
make[4]: *** [libelf/built_in.o] Error 2
---
When I change CROSS_COMPILE from arm-none-eabi- to arm-linux-gnueabi-, then rebuild, the error message is changed as the following:
---
[ -e include/asm ] || ln -sf asm-arm include/asm
make -f /home/frank/workspace/xen/src/xen-arm-v6/xen/Rules.mk -C include
make[3]: Entering directory `/home/frank/workspace/xen/src/xen-arm-v6/xen/include'
for i in public/callback.h public/dom0_ops.h public/elfnote.h public/event_channel.h public/features.h public/grant_table.h public/kexec.h public/mem_event.h public/memory.h public/nmi.h public/physdev.h public/platform.h public/sched.h public/tmem.h public/trace.h public/vcpu.h public/version.h public/xen-compat.h public/xen.h public/xencomm.h public/xenoprof.h public/hvm/e820.h public/hvm/hvm_info_table.h public/hvm/hvm_op.h public/hvm/ioreq.h public/hvm/params.h public/io/blkif.h public/io/console.h public/io/fbif.h public/io/fsif.h public/io/kbdif.h public/io/libxenvchan.h public/io/netif.h public/io/pciif.h public/io/protocols.h public/io/ring.h public/io/tpmif.h public/io/usbif.h public/io/vscsiif.h public/io/xenbus.h public/io/xs_wire.h; do arm-linux-gnueabi-gcc -ansi -include stdint.h -Wall -W -Werror -S -o /dev/null -xc $i || exit 1; echo $i; done >headers.chk.new
public/callback.h:87:5: error: unknown type name 'xen_callback_t'
make[3]: *** [headers.chk] Error 1
---
Could anyone tell me how to compile it?

Thanks in advance.

Best Regards,
Frank
--
Re: [help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git [ In reply to ]
post4pavan at gmail
Jan 30, 2012, 10:14 PM
Post #2 of 10 (4203 views)
Permalink
Hi Xen-ARM,

You have to go to the place in your filesystem, where the exact binaries of
the Cross_Compiler are placed.

You have to export them later on with the name they have in that particular
location.

For example my path arm_based_CC is

/opt/....../usr/local/gcc-4.3.3-glibc-2.8-cs2009q1-203/arm-none-linux-gnueabi/bin/
*arm-none-linux-gnueabi-*

Make sure that the path is exported properly for the ARM-Cross_Compiler.
echo $PATH should give you the check to it.

Sometimes, it may not result proper, when you export a path, then you can
include the path directly in a makefile.

*Regards :: Krishna Pavan*
Re: [help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git [ In reply to ]
Ian.Campbell at citrix
Jan 31, 2012, 1:36 AM
Post #3 of 10 (4210 views)
Permalink
On Tue, 2012-01-31 at 06:01 +0000, Frank, Chen wrote:
> Hi experts,
>
> I am interested in XEN for ARM. I am trying to compile the unstable
> source which I cloned from this repository,
> sstabellini/xen-unstable.git and the branch is arm-v6.
>
> The environment is ubuntu-10.04 LTS. The cross-compiler for arm is
> downloaded from codesourcery, the version : arm-2011.09.
>
> My steps:
> 1) export XEN_COMPILE_ARCH=arm
> 2) CROSS_COMPILE=arm-none-eabi- make xen

This is approximately what I do, except I use XEN_TARGET_ARCH rather
than XEN_COMPILE_ARCH and I pass both XEN_TARGET_ARCH and CROSS_COMPILE
as make variables rather than setting then in my environment, e.g. I do:

make -C xen XEN_TARGET_ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnueabi- xen

I'm not sure if XEN_COMPILE_ARCH and XEN_TARGET_ARCH are the same thing
(I think they are just synonyms) but the placement of the variable (env
vs. command line) can have effects on what actually ends up getting set
so it might be worth trying.

> The error message is the following:
> ---
> make[4]: Entering directory
> `/home/frank/workspace/xen/src/xen-arm-v6/xen/common'
> arm-none-eabi-gcc -O1 -fno-omit-frame-pointer -marm -g
> -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
> -Wdeclaration-after-statement -Wno-unused-but-set-variable
> -fno-builtin -fno-common -Wredundant-decls -iwithprefix include
> -Werror -Wno-pointer-arith -pipe
> -I/home/frank/workspace/xen/src/xen-arm-v6/xen/include -msoft-float
> -fno-stack-protector -fno-exceptions -Wnested-externs
> -DGCC_HAS_VISIBILITY_ATTRIBUTE -march=armv7-a -mcpu=cortex-a15
> -fno-optimize-sibling-calls -g -D__XEN__
> -include /home/frank/workspace/xen/src/xen-arm-v6/xen/include/xen/config.h -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD -MF .version.o.d -c version.c -o version.o
> make -f /home/frank/workspace/xen/src/xen-arm-v6/xen/Rules.mk -C
> libelf built_in.o
> make[5]: Entering directory
> `/home/frank/workspace/xen/src/xen-arm-v6/xen/common/libelf'
> arm-none-eabi-ld -marmelf_linux_eabi -r -o libelf-temp.o
> libelf-tools.o libelf-loader.o libelf-dominfo.o
> arm-none-eabi-ld: unrecognised emulation mode: armelf_linux_eabi
> Supported emulations: armelf

It's not clear whether our use of armelf_linux_eabi here is correct but
both the cross compiler/ld I use and the native Debian armhf compiler
support exactly armelf_linux_eabi and armelfb_linux_eabi but not armelf.

This might be something we need to figure out going forward but for now
it seems you also have arm-linux-gnueabi so I recommend using that.

> make[5]: *** [libelf-temp.o] Error 1
> make[5]: Leaving directory
> `/home/frank/workspace/xen/src/xen-arm-v6/xen/common/libelf'
> make[4]: *** [libelf/built_in.o] Error 2
> ---
> When I change CROSS_COMPILE from arm-none-eabi- to arm-linux-gnueabi-,
> then rebuild, the error message is changed as the following:
> ---
> [ -e include/asm ] || ln -sf asm-arm include/asm
> make -f /home/frank/workspace/xen/src/xen-arm-v6/xen/Rules.mk -C
> include
> make[3]: Entering directory
> `/home/frank/workspace/xen/src/xen-arm-v6/xen/include'
> for i in public/callback.h public/dom0_ops.h public/elfnote.h
> public/event_channel.h public/features.h public/grant_table.h
> public/kexec.h public/mem_event.h public/memory.h public/nmi.h
> public/physdev.h public/platform.h public/sched.h public/tmem.h
> public/trace.h public/vcpu.h public/version.h public/xen-compat.h
> public/xen.h public/xencomm.h public/xenoprof.h public/hvm/e820.h
> public/hvm/hvm_info_table.h public/hvm/hvm_op.h public/hvm/ioreq.h
> public/hvm/params.h public/io/blkif.h public/io/console.h
> public/io/fbif.h public/io/fsif.h public/io/kbdif.h
> public/io/libxenvchan.h public/io/netif.h public/io/pciif.h
> public/io/protocols.h public/io/ring.h public/io/tpmif.h
> public/io/usbif.h public/io/vscsiif.h public/io/xenbus.h
> public/io/xs_wire.h; do arm-linux-gnueabi-gcc -ansi -include stdint.h
> -Wall -W -Werror -S -o /dev/null -xc $i || exit 1; echo $i; done
> >headers.chk.new
> public/callback.h:87:5: error: unknown type name 'xen_callback_t'

At this point I get:
[ -e include/asm ] || ln -sf asm-arm include/asm
make -f /local/scratch/ianc/devel/arm/xen-unstable/xen/Rules.mk -C include
make[3]: Entering directory `/local/scratch/ianc/devel/arm/xen-unstable/xen/include'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/local/scratch/ianc/devel/arm/xen-unstable/xen/include'

Aha -- the difference is down to XEN_TARGET_ARCH vs. XEN_COMPILE_ARCH,
see towards the end of xen/include/Makefile:
ifeq ($(XEN_TARGET_ARCH),$(XEN_COMPILE_ARCH))
...
all: headers.chk
...

I'm inferring from the Makefile that:
XEN_COMPILE_ARCH == the host architecture -- e.g. the machine you are
compiling on
XEN_TARGET_ARCH == the target architecture -- e.g. the machine you want
to run the resulting Xen on.

And indeed if I do a native build on an arm system I see the same error
as you do. We'll look at fixing this but in the meantime I suggest you
use XEN_TARGET_ARCH and not XEN_COMPILE_ARCH.

Ian.




_______________________________________________
Xen-arm mailing list
Xen-arm@lists.xensource.com
http://lists.xensource.com/mailman/listinfo/xen-arm
Re: [help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git [ In reply to ]
stefano.stabellini at eu
Jan 31, 2012, 6:53 AM
Post #4 of 10 (4200 views)
Permalink
On Tue, 31 Jan 2012, Ian Campbell wrote:
> > make[3]: Entering directory
> > `/home/frank/workspace/xen/src/xen-arm-v6/xen/include'
> > for i in public/callback.h public/dom0_ops.h public/elfnote.h
> > public/event_channel.h public/features.h public/grant_table.h
> > public/kexec.h public/mem_event.h public/memory.h public/nmi.h
> > public/physdev.h public/platform.h public/sched.h public/tmem.h
> > public/trace.h public/vcpu.h public/version.h public/xen-compat.h
> > public/xen.h public/xencomm.h public/xenoprof.h public/hvm/e820.h
> > public/hvm/hvm_info_table.h public/hvm/hvm_op.h public/hvm/ioreq.h
> > public/hvm/params.h public/io/blkif.h public/io/console.h
> > public/io/fbif.h public/io/fsif.h public/io/kbdif.h
> > public/io/libxenvchan.h public/io/netif.h public/io/pciif.h
> > public/io/protocols.h public/io/ring.h public/io/tpmif.h
> > public/io/usbif.h public/io/vscsiif.h public/io/xenbus.h
> > public/io/xs_wire.h; do arm-linux-gnueabi-gcc -ansi -include stdint.h
> > -Wall -W -Werror -S -o /dev/null -xc $i || exit 1; echo $i; done
> > >headers.chk.new
> > public/callback.h:87:5: error: unknown type name 'xen_callback_t'
>
> At this point I get:
> [ -e include/asm ] || ln -sf asm-arm include/asm
> make -f /local/scratch/ianc/devel/arm/xen-unstable/xen/Rules.mk -C include
> make[3]: Entering directory `/local/scratch/ianc/devel/arm/xen-unstable/xen/include'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/local/scratch/ianc/devel/arm/xen-unstable/xen/include'
>
> Aha -- the difference is down to XEN_TARGET_ARCH vs. XEN_COMPILE_ARCH,
> see towards the end of xen/include/Makefile:
> ifeq ($(XEN_TARGET_ARCH),$(XEN_COMPILE_ARCH))
> ...
> all: headers.chk
> ...
>
> I'm inferring from the Makefile that:
> XEN_COMPILE_ARCH == the host architecture -- e.g. the machine you are
> compiling on
> XEN_TARGET_ARCH == the target architecture -- e.g. the machine you want
> to run the resulting Xen on.
>
> And indeed if I do a native build on an arm system I see the same error
> as you do. We'll look at fixing this but in the meantime I suggest you
> use XEN_TARGET_ARCH and not XEN_COMPILE_ARCH.

The following patch fixes the compile issue (that indeed is due to the
header files check you pointed out).

---

arm: few missing #define

Few missing #define are the cause of a compile failure with
XEN_TARGET_ARM=arm and XEN_COMPILE_ARM=arm (for example in the case of a
native compilation). This patch fill the gaps.

Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>

diff --git a/xen/include/public/arch-arm.h b/xen/include/public/arch-arm.h
index c430cf3..e04c4fd 100644
--- a/xen/include/public/arch-arm.h
+++ b/xen/include/public/arch-arm.h
@@ -110,6 +110,8 @@ typedef struct arch_vcpu_info arch_vcpu_info_t;

struct arch_shared_info { };
typedef struct arch_shared_info arch_shared_info_t;
+typedef unsigned long xen_callback_t;
+
#endif

#endif /* __XEN_PUBLIC_ARCH_ARM_H__ */
diff --git a/xen/include/public/io/protocols.h b/xen/include/public/io/protocols.h
index 77bd1bd..0b7a2ea 100644
--- a/xen/include/public/io/protocols.h
+++ b/xen/include/public/io/protocols.h
@@ -26,6 +26,7 @@
#define XEN_IO_PROTO_ABI_X86_32 "x86_32-abi"
#define XEN_IO_PROTO_ABI_X86_64 "x86_64-abi"
#define XEN_IO_PROTO_ABI_IA64 "ia64-abi"
+#define XEN_IO_PROTO_ABI_ARM "arm-abi"

#if defined(__i386__)
# define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_X86_32
@@ -33,6 +34,8 @@
# define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_X86_64
#elif defined(__ia64__)
# define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_IA64
+#elif defined(__arm__)
+# define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_ARM
#else
# error arch fixup needed here
#endif

_______________________________________________
Xen-arm mailing list
Xen-arm@lists.xensource.com
http://lists.xensource.com/mailman/listinfo/xen-arm
Re: [help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git [ In reply to ]
chysun2000 at 163
Feb 5, 2012, 5:00 PM
Post #5 of 10 (4199 views)
Permalink
Hi Xen-ARMs,

I applied this patch, "error: unknown type name 'xen_callback_t' is fixed. But I still meet the problem. The problem is where to download the cross compiler "arm-none-linux-gnueabi-gcc" which supports march=arm-V7a and mcpu=cortex-a15.

Would someone give me one avaiable URL to download the right compiler?

Best Regards,
Frank
--




At 2012-01-31 22:51:29,"Stefano Stabellini" <stefano.stabellini@eu.citrix.com> wrote:
>On Tue, 31 Jan 2012, Ian Campbell wrote:
>> > make[3]: Entering directory
>> > `/home/frank/workspace/xen/src/xen-arm-v6/xen/include'
>> > for i in public/callback.h public/dom0_ops.h public/elfnote.h
>> > public/event_channel.h public/features.h public/grant_table.h
>> > public/kexec.h public/mem_event.h public/memory.h public/nmi.h
>> > public/physdev.h public/platform.h public/sched.h public/tmem.h
>> > public/trace.h public/vcpu.h public/version.h public/xen-compat.h
>> > public/xen.h public/xencomm.h public/xenoprof.h public/hvm/e820.h
>> > public/hvm/hvm_info_table.h public/hvm/hvm_op.h public/hvm/ioreq.h
>> > public/hvm/params.h public/io/blkif.h public/io/console.h
>> > public/io/fbif.h public/io/fsif.h public/io/kbdif.h
>> > public/io/libxenvchan.h public/io/netif.h public/io/pciif.h
>> > public/io/protocols.h public/io/ring.h public/io/tpmif.h
>> > public/io/usbif.h public/io/vscsiif.h public/io/xenbus.h
>> > public/io/xs_wire.h; do arm-linux-gnueabi-gcc -ansi -include stdint.h
>> > -Wall -W -Werror -S -o /dev/null -xc $i || exit 1; echo $i; done
>> > >headers.chk.new
>> > public/callback.h:87:5: error: unknown type name 'xen_callback_t'
>>
>> At this point I get:
>> [ -e include/asm ] || ln -sf asm-arm include/asm
>> make -f /local/scratch/ianc/devel/arm/xen-unstable/xen/Rules.mk -C include
>> make[3]: Entering directory `/local/scratch/ianc/devel/arm/xen-unstable/xen/include'
>> make[3]: Nothing to be done for `all'.
>> make[3]: Leaving directory `/local/scratch/ianc/devel/arm/xen-unstable/xen/include'
>>
>> Aha -- the difference is down to XEN_TARGET_ARCH vs. XEN_COMPILE_ARCH,
>> see towards the end of xen/include/Makefile:
>> ifeq ($(XEN_TARGET_ARCH),$(XEN_COMPILE_ARCH))
>> ...
>> all: headers.chk
>> ...
>>
>> I'm inferring from the Makefile that:
>> XEN_COMPILE_ARCH == the host architecture -- e.g. the machine you are
>> compiling on
>> XEN_TARGET_ARCH == the target architecture -- e.g. the machine you want
>> to run the resulting Xen on.
>>
>> And indeed if I do a native build on an arm system I see the same error
>> as you do. We'll look at fixing this but in the meantime I suggest you
>> use XEN_TARGET_ARCH and not XEN_COMPILE_ARCH.
>
>The following patch fixes the compile issue (that indeed is due to the
>header files check you pointed out).
>
>---
>
>arm: few missing #define
>
>Few missing #define are the cause of a compile failure with
>XEN_TARGET_ARM=arm and XEN_COMPILE_ARM=arm (for example in the case of a
>native compilation). This patch fill the gaps.
>
>Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
>diff --git a/xen/include/public/arch-arm.h b/xen/include/public/arch-arm.h
>index c430cf3..e04c4fd 100644
>--- a/xen/include/public/arch-arm.h
>+++ b/xen/include/public/arch-arm.h
>@@ -110,6 +110,8 @@ typedef struct arch_vcpu_info arch_vcpu_info_t;
>
> struct arch_shared_info { };
> typedef struct arch_shared_info arch_shared_info_t;
>+typedef unsigned long xen_callback_t;
>+
> #endif
>
> #endif /* __XEN_PUBLIC_ARCH_ARM_H__ */
>diff --git a/xen/include/public/io/protocols.h b/xen/include/public/io/protocols.h
>index 77bd1bd..0b7a2ea 100644
>--- a/xen/include/public/io/protocols.h
>+++ b/xen/include/public/io/protocols.h
>@@ -26,6 +26,7 @@
> #define XEN_IO_PROTO_ABI_X86_32 "x86_32-abi"
> #define XEN_IO_PROTO_ABI_X86_64 "x86_64-abi"
> #define XEN_IO_PROTO_ABI_IA64 "ia64-abi"
>+#define XEN_IO_PROTO_ABI_ARM "arm-abi"
>
> #if defined(__i386__)
> # define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_X86_32
>@@ -33,6 +34,8 @@
> # define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_X86_64
> #elif defined(__ia64__)
> # define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_IA64
>+#elif defined(__arm__)
>+# define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_ARM
> #else
> # error arch fixup needed here
> #endif
Re: [help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git [ In reply to ]
stefano.stabellini at eu
Feb 8, 2012, 2:36 AM
Post #6 of 10 (4181 views)
Permalink
On Mon, 6 Feb 2012, Frank, Chen wrote:
> Hi Xen-ARMs,
>  
> I applied this patch, "error: unknown type name 'xen_callback_t' is fixed.

Thanks for testing!


> But I still meet the problem. The problem is
> where to download the cross compiler "arm-none-linux-gnueabi-gcc" which supports march=arm-V7a and mcpu=cortex-a15.
>  
> Would someone give me one avaiable URL to download the right compiler? 

Which cross-compiler are you using at the moment?
If you are on Ubuntu, we just need to

apt-get install gcc-arm-linux-gnueabi

in order to get Linaro's cross-compiler.
Re: [help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git [ In reply to ]
chysun2000 at 163
Feb 8, 2012, 4:59 AM
Post #7 of 10 (4189 views)
Permalink
Hi Xen-ARMs,


I used the latest compiler from Linaro.
But the compiler cannot support march=armv7-a and mcpu=cortex-a15

The error information is like this:
make -f /home/frank/workspace/xen/src/xen-arm-v6/xen/Rules.mk -C include
make[3]: Entering directory `/home/frank/workspace/xen/src/xen-arm-v6/xen/include'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/frank/workspace/xen/src/xen-arm-v6/xen/include'
make -f /home/frank/workspace/xen/src/xen-arm-v6/xen/Rules.mk -C arch/arm asm-offsets.s
make[3]: Entering directory `/home/frank/workspace/xen/src/xen-arm-v6/xen/arch/arm'
arm-linux-gnueabi-gcc -O1 -fno-omit-frame-pointer -marm -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/frank/workspace/xen/src/xen-arm-v6/xen/include -msoft-float -nopie -fno-stack-protector -fno-exceptions -Wnested-externs -DGCC_HAS_VISIBILITY_ATTRIBUTE -march=armv7-a -mcpu=cortex-a15 -fno-optimize-sibling-calls -g -D__XEN__ -include /home/frank/workspace/xen/src/xen-arm-v6/xen/include/xen/config.h -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD -MF .asm-offsets.s.d -S -o asm-offsets.s asm-offsets.c
asm-offsets.c:1:0: error: switch -mcpu=cortex-a15 conflicts with -march=armv7-a switch [-Werror]
cc1: all warnings being treated as errors


I modified xen/arch/arm/Rules.mk like the following, the compiling is OK.
diff --git a/xen/arch/arm/Rules.mk b/xen/arch/arm/Rules.mk
index 336e209..407fc82 100644
--- a/xen/arch/arm/Rules.mk
+++ b/xen/arch/arm/Rules.mk
@@ -22,7 +22,8 @@ ifneq ($(call cc-option,$(CC),-fvisibility=hidden,n),n)
CFLAGS += -DGCC_HAS_VISIBILITY_ATTRIBUTE
endif

-CFLAGS += -march=armv7-a -mcpu=cortex-a15
+#CFLAGS += -march=armv7-a -mcpu=cortex-a15
+CFLAGS += -mcpu=cortex-a15


I checked binary file xen, it does not have the unresolved symbol.


Best Regards,
Frank
--

在 2012-02-08 18:36:48，"Stefano Stabellini" <stefano.stabellini@eu.citrix.com> 写道：
>On Mon, 6 Feb 2012, Frank, Chen wrote:
>> Hi Xen-ARMs,
>> Â
>> I applied this patch, "error: unknown type name 'xen_callback_t' is fixed.
>
>Thanks for testing!
>
>
>> But I still meet the problem. The problem is
>> where to download the cross compiler "arm-none-linux-gnueabi-gcc" which supports march=arm-V7a and mcpu=cortex-a15.
>> Â
>> Would someone give me one avaiable URL to download the right compiler?Â
>
>Which cross-compiler are you using at the moment?
>If you are on Ubuntu, we just need to
>
>apt-get install gcc-arm-linux-gnueabi
>
>in order to get Linaro's cross-compiler.
Re: [help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git [ In reply to ]
Ian.Campbell at citrix
Feb 8, 2012, 8:53 AM
Post #8 of 10 (4166 views)
Permalink
On Mon, 2012-02-06 at 01:00 +0000, Frank, Chen wrote:
> The problem is where to download the cross compiler
> "arm-none-linux-gnueabi-gcc" which supports march=arm-V7a and
> mcpu=cortex-a15.
>
> Would someone give me one avaiable URL to download the right
> compiler?

I use
http://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.0/x86_64-gcc-4.6.0-nolibc_arm-unknown-linux-gnueabi.tar.bz2

Ian.




_______________________________________________
Xen-arm mailing list
Xen-arm@lists.xensource.com
http://lists.xensource.com/mailman/listinfo/xen-arm
Re: [help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git [ In reply to ]
chysun2000 at 163
Feb 8, 2012, 4:43 PM
Post #9 of 10 (4177 views)
Permalink
Hi Ian,

Thanks. :-)
I will try it.

Best Regards,
Frank
--




At 2012-02-09 00:53:08,"Ian Campbell" <Ian.Campbell@citrix.com> wrote:
>On Mon, 2012-02-06 at 01:00 +0000, Frank, Chen wrote:
>> The problem is where to download the cross compiler
>> "arm-none-linux-gnueabi-gcc" which supports march=arm-V7a and
>> mcpu=cortex-a15.
>>
>> Would someone give me one avaiable URL to download the right
>> compiler?
>
>I use
>http://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.0/x86_64-gcc-4.6.0-nolibc_arm-unknown-linux-gnueabi.tar.bz2
>
>Ian.
>
>
>
Re: [help] How to compile the unstable source for arm at sstabellini/xen-unstable.git/.git [ In reply to ]
chysun2000 at 163
Feb 8, 2012, 5:00 PM
Post #10 of 10 (4175 views)
Permalink
Hi Ian and Xen-ARMs,

I tried this compiler. The compile is OK.

Best Regards,
Frank
--




At 2012-02-09 00:53:08,"Ian Campbell" <Ian.Campbell@citrix.com> wrote:
>On Mon, 2012-02-06 at 01:00 +0000, Frank, Chen wrote:
>> The problem is where to download the cross compiler
>> "arm-none-linux-gnueabi-gcc" which supports march=arm-V7a and
>> mcpu=cortex-a15.
>>
>> Would someone give me one avaiable URL to download the right
>> compiler?
>
>I use
>http://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.0/x86_64-gcc-4.6.0-nolibc_arm-unknown-linux-gnueabi.tar.bz2
>
>Ian.
>
>
>

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal