From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: M4 rc1 build prerequisites
Date: Tue, 11 Apr 2017 12:10:40 +0100 [thread overview]
Message-ID: <1491909040.12091.11.camel@linuxfoundation.org> (raw)
I just wanted to give people an idea of where we're at with 2.3. I'm
aware of and would like to see the following issues fixed:
a) runqemu and other tools failing in various circumstances due to RSS.
b) DISTRO_FEATURES contaminating native/nativesdk builds, we need
separate configuration of these.
c) Patrick has found some task checksum changes which are concerning
and we need to look into.
If anyone has other things they're expecting to see in 2.3 and which
aren't in master-next, you might want to mention them.
I'm meant to be trying to take some vacation which really isn't working
out :(.
Cheers,
Richard
next reply other threads:[~2017-04-11 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 11:10 Richard Purdie [this message]
2017-04-11 16:22 ` M4 rc1 build prerequisites Peter Kjellerstedt
2017-04-12 8:44 ` Paul Eggleton
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=1491909040.12091.11.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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