Re: [PATCH 0/1] pseudo: Update to the latest upstream version

[Mark Hatle <mark.hatle@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