Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tasslehoff Kjappfot <tasskjapp@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Error compiling Boost with Python support on 64-bit host for 32-bit target.
Date: Tue, 24 Apr 2012 23:46:07 +0200	[thread overview]
Message-ID: <4F971F1F.5080306@gmail.com> (raw)
In-Reply-To: <1335260672.12692.114.camel@ted>

On 04/24/2012 11:44 AM, Richard Purdie wrote:
> On Tue, 2012-04-24 at 23:02 +0200, Tasslehoff Kjappfot wrote:
>> boost.inc:
>>
>> # To enable python, uncomment the following:
>> #BOOST_LIBS += "python"
>> #DEPENDS += "python"
>> #PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}"
>> #PYTHON_VERSION = "2.5"
>>
>> If this is uncommented, stuff fails with messages like:
>>
>> | ...failed gcc.compile.c++
>> bin.v2/libs/python/build/69ffc88faf507005827aa061bd65b9bd/wrapper.o...
>> | gcc.compile.c++
>> bin.v2/libs/python/build/69ffc88faf507005827aa061bd65b9bd/import.o
>> | In file included from
>> /src/openembedded/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include/python2.7/Python.h:58:0,
>> |                  from ./boost/python/detail/wrap_python.hpp:142,
>> |                  from ./boost/python/detail/prefix.hpp:13,
>> |                  from ./boost/python/ssize_t.hpp:9,
>> |                  from ./boost/python/object.hpp:8,
>> |                  from ./boost/python/import.hpp:8,
>> |                  from libs/python/src/import.cpp:6:
>> |
>> /src/openembedded/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include/python2.7/pyport.h:849:2:
>> error: #error "LONG_BIT definition appears wrong for platform (bad
>> gcc/glibc config?)."
>>
>> I have problems figuring out how to solve this (other than by
>> reinstalling Ubuntu 32-bit).
> You have to wonder why its looking in the native sysroot and not the
> target one. It would probably find better values in the target one...
>
> Cheers,
>
> Richard
> d-core
I thought so too, but I wasn't able to convince it to do so. Will have 
to try harder :)



  reply	other threads:[~2012-04-24  9:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24  5:50 [PATCH 0/1]:gdk-pixbuf: Add --with-x11 when building lsb image Xiaofeng Yan
2012-04-24  5:50 ` [PATCH 1/1] gdk-pixbuf: " Xiaofeng Yan
2012-04-24  5:53   ` Koen Kooi
2012-04-24  6:12     ` Xiaofeng Yan
2012-04-24  6:29       ` Koen Kooi
2012-04-24  7:29         ` Richard Purdie
2012-04-24  8:59           ` Xiaofeng Yan
2012-04-24 21:02   ` Error compiling Boost with Python support on 64-bit host for 32-bit target Tasslehoff Kjappfot
2012-04-24  9:44     ` Richard Purdie
2012-04-24 21:46       ` Tasslehoff Kjappfot [this message]
2012-04-24 21:04     ` Tasslehoff Kjappfot
2012-04-24 23:14     ` [PATCH] boost: set python-root correctly Tasslehoff Kjappfot
2012-04-24 11:52       ` Koen Kooi
2012-04-25  0:12     ` Tasslehoff Kjappfot
2012-04-27 21:05       ` Saul Wold

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=4F971F1F.5080306@gmail.com \
    --to=tasskjapp@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox