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

To: Jacob Gorm Hansen <jacobg@xxxxxxx>
Subject: Re: [Xen-devel] cross compiling 32 bit Xen on an x86_64 system
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Mon, 21 Mar 2005 19:57:49 -0600
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 22 Mar 2005 02:00:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <423F6307.70306@xxxxxxx>
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>
Organization: IBM
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E37B1@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1111448530.4293.182.camel@xxxxxxxxxxxxxxxxxxxx> <423F6307.70306@xxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20041206)
Jacob Gorm Hansen wrote:

Michal Ostrowski wrote:

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.


One option would be to use vm-tools instead of xend (search this list for announcements and URL), as the former does not (yet) depend on Python.

I found the best way to deal with building python modules is the following:

PYINC=`python -c "import distutils.sysconfig; print distutils.sysconfig.get_python_inc()"` PYLIB=`python -c "import distutils.sysconfg; print distutils.sysconfig.get_python_lib(prefix='')"`

CFLAGS += -I$(PYINC)

And then to use $(DESTDIR)$(prefix)/$(PYLIB) for the install path of the module. You have to write your own rules to build the shared object but at least you don't have these cross-compiling issues.

This is how the python bindings are built in libxen.

Regards,
Anthony Liguori

Jacob


-------------------------------------------------------
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




-------------------------------------------------------
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