[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.