This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] cross compiling 32 bit Xen on an x86_64 system

To: "Jerone Young" <jyoung5@xxxxxxxxxx>, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Subject: RE: [Xen-devel] cross compiling 32 bit Xen on an x86_64 system
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 21 Mar 2005 23:00:34 -0000
Cc: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, <ian.pratt@xxxxxxxxxxxx>
Delivery-date: Mon, 21 Mar 2005 23:12:08 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcUuYdXKpj3yo/msS0ao87SKerGpdQABAqqg
Thread-topic: [Xen-devel] cross compiling 32 bit Xen on an x86_64 system
> Here is the gcc line it comes up with:
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -m64 -
> D_GNU_SOURCE -fPIC -m32 -march=i686 -fPIC -
> I../../tools/python/xen/lowlevel/xu -I../../tools/libxc -
> I../../tools/libxutil -I../../tools/xcs -Ixen/lowlevel/xc -
> I/usr/include/python2.3 -c xen/lowlevel/xc/xc.c -o build/temp.linux-
> x86_64-2.3/xen/lowlevel/xc/xc.o -fno-strict-aliasing -Wall -Werror
> In file included from /usr/include/python2.3/Python.h:48,
>                  from xen/lowlevel/xc/xc.c:7:
> /usr/include/python2.3/pyport.h:554:2: #error "LONG_BIT definition
> appears wrong for platform (bad gcc/glibc config?).
> You will notice both "-m64" & "-m32 -march=i686" ("-m32 & -march=i686"
> are the CFLAGS we are specifying). This is were the problem is. The
> first set of CFLAGS with "-m64" are assumed by python.
> On a normal x86-64 compile you get: 
> gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -m64 -
> D_GNU_SOURCE -fPIC -m64 -fPIC -I../../tools/python/xen/lowlevel/xu -
> I../../tools/libxc -I../../tools/libxutil -I../../tools/xcs -
> Ixen/lowlevel/xc -I/usr/include/python2.3 -c xen/lowlevel/xc/xc.c -o
> build/temp.linux-x86_64-2.3/xen/lowlevel/xc/xc.o 
> -fno-strict-aliasing -
> Wall -Werror
> So it's figuring out where python is getting these CFLAGS.


It seems to be coming from the following lines in
Not sure how to fix it...

# Compiler options
OPT=            -DNDEBUG -O2 -g -pipe -m64 -D_GNU_SOURCE -fPIC
BASECFLAGS=      -fno-strict-aliasing


SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list