From: Anthony Liguori <aliguori@us.ibm.com>
To: Jacob Gorm Hansen <jacobg@diku.dk>
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 19:57:49 -0600 [thread overview]
Message-ID: <423F7B9D.5010107@us.ibm.com> (raw)
In-Reply-To: <423F6307.70306@diku.dk>
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@lists.sourceforge.net
> 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
next prev parent reply other threads:[~2005-03-22 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 23:00 cross compiling 32 bit Xen on an x86_64 system Ian Pratt
2005-03-21 23:42 ` Michal Ostrowski
2005-03-22 0:12 ` Jacob Gorm Hansen
2005-03-22 1:57 ` Anthony Liguori [this message]
2005-03-22 9:18 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2005-03-21 20:37 Subrahmanian, Raj
2005-03-21 21:55 ` Jerone Young
2005-03-22 9:07 ` Keir Fraser
2005-03-22 15:44 ` Jerone Young
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=423F7B9D.5010107@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=jacobg@diku.dk \
--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.