From: Mark Hatle <mark.hatle@windriver.com>
To: poky <poky@yoctoproject.org>
Subject: [PATCH 0/1] pseudo: Update to the latest upstream version
Date: Thu, 13 Jan 2011 22:54:31 -0600 [thread overview]
Message-ID: <4D2FD707.4080509@windriver.com> (raw)
Update pseudo to the latest version to resolve a number of optimization defects.
The problems were present on both 64-bit and 32-bit systems, but generally only
caused issues on 32-bit hosts.
Note: once you upgrade you need to be sure to clean out pseudo. In order to do
this ../bitbake/bin/bitbake -c cleanall pseudo-native
Followed by ../bitbake/bin/bitbake pseudo-native
Otherwise you can end up in a wierd situation where the old pseudo is being
used to build the new one.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: mhatle/pseudo
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/pseudo
Thanks,
Mark Hatle <mark.hatle@windriver.com>
---
Mark Hatle (1):
pseudo: Update to the latest upstream version
.../conf/distro/include/poky-default-revisions.inc | 2 +-
.../895fa7e359e8026a608fba052c2994e42901e45f.patch | 235 --------------------
meta/recipes-devtools/pseudo/pseudo_git.bb | 2 +-
3 files changed, 2 insertions(+), 237 deletions(-)
delete mode 100644
meta/recipes-devtools/pseudo/pseudo/895fa7e359e8026a608fba052c2994e42901e45f.patch
--
1.7.3.4
next reply other threads:[~2011-01-14 4:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 4:54 Mark Hatle [this message]
2011-01-14 4:55 ` [PATCH 1/1] pseudo: Update to the latest upstream version Mark Hatle
2011-01-14 19:38 ` [PATCH 0/1] " Saul Wold
2011-01-14 19:39 ` Mark Hatle
2011-01-14 21:17 ` Mark Hatle
2011-01-17 8:35 ` Saul Wold
2011-01-17 15:19 ` Richard Purdie
2011-01-17 17:06 ` Mark Hatle
2011-01-17 8:19 ` Xu, Dongxiao
2011-01-18 22:33 ` 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=4D2FD707.4080509@windriver.com \
--to=mark.hatle@windriver.com \
--cc=poky@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.