WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

I came across a variant of this problem trying to cross-compile myself. 
Python's distutils.core package seem to have "gcc" hardcoded in it, and
there is no way to redirect it to another compiler when trying to build
these modules.  In other words, python seems not to be able to
cross-compile these things.

On Mon, 2005-03-21 at 23:00 +0000, Ian Pratt wrote:
> > 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.
> 
> Interesting.
> 
> It seems to be coming from the following lines in
> /usr/lib64/python2.3/config/Makefile
> Not sure how to fix it...
> 
> # Compiler options
> OPT=            -DNDEBUG -O2 -g -pipe -m64 -D_GNU_SOURCE -fPIC
> BASECFLAGS=      -fno-strict-aliasing
> CFLAGS=         $(BASECFLAGS) $(OPT)
> 
> 
> 
> Ian

-- 
Michal Ostrowski <mostrows@xxxxxxxxxxxxxx>



-------------------------------------------------------
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.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel