From: Mark Hatle <mark.hatle@windriver.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] pseudo: Update to the latest upstream version
Date: Fri, 14 Jan 2011 15:17:05 -0600 [thread overview]
Message-ID: <4D30BD51.7030305@windriver.com> (raw)
In-Reply-To: <4D30A67B.2070004@windriver.com>
A potential solution to this problem has been pushed to the poky-contrib
mhatle/pseudo tree.
If anyone is interested in trying this, I'd appreciate it. I've so far not been
able to reproduce the original problem locally, but based on the symptoms I
believe we've got a likely fix in place.
--Mark
On 1/14/11 1:39 PM, Mark Hatle wrote:
> On 1/14/11 1:38 PM, Saul Wold wrote:
>> On 01/13/2011 08:54 PM, Mark Hatle wrote:
>>> 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
>>>
>> Mark,
>>
>> I did not pull this because of a failure seen on the autobuilder, the
>> failure was in eglibc-initial trying to compile.
>>
>> The error was:
>>
>> arm-poky-linux-gnueabi-gcc: error trying to exec 'cc1': execvp: No such
>> file or directory
>
> pseudo does capture execvp. So it's possible something is going wrong there.
> I'm investigating...
>
> --Mark
>
>> I know that this seems strange for pseudo to cause, but I removed the
>> psuedo change and this problem went away. It could be a build timing
>> issue or an install location issue.
>>
>> Check the autobuilder log at:
>> http://autobuilder.pokylinux.org:8010/builders/distro-testing/builds/44/steps/shell_1/logs/stdio
>>
>> Unfortunately because I rebuild distro-testing the individual logs are
>> gone. Let me know if we need to rebuild with the error for further
>> diagnoses.
>>
>> Thanks
>> Sau!
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2011-01-14 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 4:54 [PATCH 0/1] pseudo: Update to the latest upstream version Mark Hatle
2011-01-14 4:55 ` [PATCH 1/1] " 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 [this message]
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=4D30BD51.7030305@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox