From: Saul Wold <saul.wold@intel.com>
To: "Serban, Laurentiu" <laurentiu.serban@intel.com>,
Zhao Yi <yi.zhao@windriver.com>,
"Liu, Song" <song.liu@intel.com>,
"Stewart, David C" <david.c.stewart@intel.com>,
"Purdie, Richard" <richard.purdie@intel.com>,
"Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>,
Yocto Project Discussion <yocto@yoctoproject.org>,
"Stewart, David C" <david.c.stewart@intel.com>,
Matthew McClintock <msm@freescale.com>
Subject: Milestone 4, RC2 Build
Date: Mon, 10 Sep 2012 21:01:28 -0700 [thread overview]
Message-ID: <504EB798.60904@intel.com> (raw)
Folks,
Given the issues we had with the Eclipse and ADT installer during the
RC1 build and we decided to forgo the existing RC1 build and restart
with an RC2. There have been no changes to the Poky RC1 branch, but we
moved Eclipse forward to pick up some changes.
The current Autobuilder build artifacts are located at
http://autobuilder.yoctoproject.org/pub/nightly/20120910-5/
This includes the Eclipse plugin and adt-installer, there should be 2
versions of the installer if I understood Beth correct, please use the
one marked adt-installer-QA when it's populated.
I have seen 3 build failures, all related to libowl-av and sato rootfs,
they are in Atom-pc, qemuppc and mpc8315 targets. I am going attempt a
rebuild of the nightly-ppc standalone. There was also a failure in the
p1022, which I think Matthew is aware of.
All major repos have been have been Branched and we are using the 1.3_M4
branch, git hash dd3edc9fbb674682947e8218202fdbeef8635dd5
Thanks for your support in checking out these milestone.
Sau!
next reply other threads:[~2012-09-11 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 4:01 Saul Wold [this message]
2012-09-11 19:29 ` Milestone 4, RC2 Build McClintock Matthew-B29882
2012-09-11 20:26 ` Flanagan, Elizabeth
2012-09-11 20:47 ` McClintock Matthew-B29882
2012-09-11 21:49 ` Flanagan, Elizabeth
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=504EB798.60904@intel.com \
--to=saul.wold@intel.com \
--cc=david.c.stewart@intel.com \
--cc=elizabeth.flanagan@intel.com \
--cc=laurentiu.serban@intel.com \
--cc=msm@freescale.com \
--cc=richard.purdie@intel.com \
--cc=song.liu@intel.com \
--cc=yi.zhao@windriver.com \
--cc=yocto@yoctoproject.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.