From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] boost: Convert ??= weaker assingment to weak ?= assignment
Date: Mon, 09 Dec 2013 21:51:24 +0000 [thread overview]
Message-ID: <1386625884.25847.100.camel@ted> (raw)
In-Reply-To: <CAMKF1sokZrHWRn_2RGT3pKN_RZMy1MnvXCUXn-gDdm4p-1iHvQ@mail.gmail.com>
On Mon, 2013-12-09 at 09:34 -0800, Khem Raj wrote:
> On Mon, Dec 9, 2013 at 3:48 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > To illustrate why I'm struggling to follow this, "bitbake boost -e |
> > grep BOOST_LIBS" on OE-Core does not show python in the list...
> >
>
>
> I can see it. Its on debian python is 2.7.3
>
> kraj@builder:~$ cat /etc/os-release
> PRETTY_NAME="Debian GNU/Linux 7 (wheezy)"
> NAME="Debian GNU/Linux"
> VERSION_ID="7"
> VERSION="7 (wheezy)"
> ID=debian
> ANSI_COLOR="1;31"
> HOME_URL="http://www.debian.org/"
> SUPPORT_URL="http://www.debian.org/support/"
> BUG_REPORT_URL="http://bugs.debian.org/"
I doubt its host OS that is causing this, more likely something to do
with the configuration you have (I'm using python 2.7.5+ on Ubuntu
13.10). Which DISTRO is this? Which layers are enabled? Which version of
bitbake?
What does the history of PACKAGECONFIG show in bitbake boost -e?
Cheers,
Richard
next prev parent reply other threads:[~2013-12-09 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 1:42 [PATCH] boost: Convert ??= weaker assingment to weak ?= assignment Khem Raj
2013-12-08 21:36 ` Lukas Bulwahn
2013-12-09 11:48 ` Richard Purdie
2013-12-09 17:34 ` Khem Raj
2013-12-09 21:51 ` Richard Purdie [this message]
2013-12-09 23:11 ` Khem Raj
2013-12-10 10:32 ` Richard Purdie
2014-01-23 1:16 ` Khem Raj
2014-01-23 16:31 ` Chris Larson
2014-01-23 16:43 ` Khem Raj
2014-01-28 12:31 ` Richard Purdie
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=1386625884.25847.100.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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