From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>,
"Huang, Jie (Jackie)" <jackie.huang@windriver.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] boost: add python to default PACKAGECONFIG options
Date: Tue, 22 Aug 2017 20:55:54 +0100 [thread overview]
Message-ID: <1503431754.32591.130.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=U1Wp8heeowiTNTwQd9vjmbP6AvSFYe8V8UYuSGQrs7Mw@mail.gmail.com>
On Tue, 2017-08-22 at 12:51 -0700, Andre McCurdy wrote:
> On Tue, Aug 22, 2017 at 12:42 AM, <jackie.huang@windriver.com>
> wrote:
> >
> > From: Jackie Huang <jackie.huang@windriver.com>
> >
> > We want to provide python libs by default, and some other
> > popular Linux distributions like redhat/fedora does the same.
> Has something changed? Is there anything in oe-core or meta-oe which
> now needs boost python support enabled?
Does it even actually build on all arches?
I'm rather behind with patch review right now as people are putting so
many patches out there with what seems like minimal testing and
expecting me/Ross and the autobuilder to figure out the problems for
them.
Each time one fails, it blocks the queue with the rest of them in and I
have to retest until I get something clean.
Testing this change is quite a way down my priority list I'm afraid.
Cheers,
Richard
next prev parent reply other threads:[~2017-08-22 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 7:42 [PATCH] boost: add python to default PACKAGECONFIG options jackie.huang
2017-08-22 19:51 ` Andre McCurdy
2017-08-22 19:55 ` Richard Purdie [this message]
2017-08-23 1:26 ` Randy MacLeod
2017-08-23 8:01 ` Huang, Jie (Jackie)
2017-08-24 6:31 ` Huang, Jie (Jackie)
2017-08-23 21:04 ` Philip Balister
2017-09-05 8:44 ` Andreas Müller
2017-09-05 9:02 ` Andreas Müller
2017-09-05 9:03 ` Andreas Müller
-- strict thread matches above, loose matches on Subject: below --
2016-09-30 6:31 jackie.huang
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=1503431754.32591.130.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--cc=jackie.huang@windriver.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 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.