Re: [Xen-devel] [PATCH] build fixes for cross-compiling

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 28.09.11 at 23:31, Adin Scannell <adin@xxxxxxxxxxxxxxx> wrote:
> I always have problems cross-compiling tools (I build everything on a
> 64-bit machine and generally target a 32-bit host), because all the
> link steps are missing targets.  I've use this tiny patch on the base
> of my workspaces.
> 
> To my knowledge, this doesn't break anything -- but who knows with
> builds, particularly cross-compiling. I just thought I'd throw this
> there in case others have the same issue and it doesn't affect
> standard build environments.

Are you saying this actually works for you (building everything, not just
the tools)?

I do cross builds too, but generally the other way around (64-bit
build on 32-bit host), and hence need to only cross-build the
hypervisor to put underneath everything.

> diff -r a422e2a4451e config/x86_32.mk
> --- a/config/x86_32.mk
> +++ b/config/x86_32.mk
> @@ -8,6 +8,7 @@ CONFIG_XCUTILS := y
>  CONFIG_IOEMU := y
> 
>  CFLAGS += -m32 -march=i686
> +LDFLAGS += -m32 -march=i686

I can't seem to find an ld (native or cross) that would accept -m32,
-march=i686, ...

>
>  # Use only if calling $(LD) directly.
>  LDFLAGS_DIRECT_OpenBSD = _obsd
> diff -r a422e2a4451e config/x86_64.mk
> --- a/config/x86_64.mk
> +++ b/config/x86_64.mk
> @@ -9,6 +9,7 @@ CONFIG_XCUTILS := y
>  CONFIG_IOEMU := y
> 
>  CFLAGS += -m64
> +LDFLAGS += -m64

... or -m64. But $(LDFLAGS) gets passed to $(LD) when building Xen
(other than for the tools, where generally $(CC) is used to do the
linking).

Jan

> 
>  LIBLEAFDIR = $(LIBLEAFDIR_x86_64)
>  LIBDIR = $(LIBDIR_x86_64)




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel