From: Jerone Young <jyoung5@us.ibm.com>
To: "Subrahmanian, Raj" <raj.subrahmanian@unisys.com>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: cross compiling 32 bit Xen on an x86_64 system
Date: Mon, 21 Mar 2005 15:55:54 -0600 [thread overview]
Message-ID: <1111442154.13943.20.camel@thinkpad> (raw)
In-Reply-To: <94C8C9E8B25F564F95185BDA64AB05F601111AA7@USTR-EXCH5.na.uis.unisys.com>
This is a python issue that I can't see a way around. The issue you are
seeing is because we are using the setup function in "distutils.core"
module
http://python.fyxm.net/doc/2.4/dist/module-distutils.core.html
and it does not pass all the correct flags when compiling
xen/lowlevel/xc/xc.c
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.
On Mon, 2005-03-21 at 15:37 -0500, Subrahmanian, Raj wrote:
> All,
>
> I am trying to cross-compile 32 Xen on my x86_64 box.
>
> I turned on XEN_TARGET_ARCH=x86_32
>
> There are problems with incompatible header files while compiling the python subdirectory.
> Is anyone else running into similar problems?
>
> thanks
> Raj
>
>
> -------------------------------------------------------
> 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_ide95&alloc_id\x14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-21 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 20:37 cross compiling 32 bit Xen on an x86_64 system Subrahmanian, Raj
2005-03-21 21:55 ` Jerone Young [this message]
2005-03-22 9:07 ` Keir Fraser
2005-03-22 15:44 ` Jerone Young
-- strict thread matches above, loose matches on Subject: below --
2005-03-21 23:00 Ian Pratt
2005-03-21 23:42 ` Michal Ostrowski
2005-03-22 0:12 ` Jacob Gorm Hansen
2005-03-22 1:57 ` Anthony Liguori
2005-03-22 9:18 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1111442154.13943.20.camel@thinkpad \
--to=jyoung5@us.ibm.com \
--cc=raj.subrahmanian@unisys.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.