I have updated the tree and rebased it on top of latest OE-Core
now python3-jinja should reliably build. Let me know if there are more issues.


On Aug 1, 2013, at 9:53 PM, Saul Wold <[email protected]> wrote:

> On 08/01/2013 01:19 PM, Khem Raj wrote:
>> 
>> On Jul 31, 2013, at 4:05 PM, Saul Wold <[email protected]> wrote:
>> 
>>> On 07/31/2013 03:51 PM, Khem Raj wrote:
>>>> 
>>>> On Jul 31, 2013, at 3:49 PM, Saul Wold <[email protected]> wrote:
>>>> 
>>>>> 
>>>>> Still seems to failing in Jinja, I wonder if the dependencies are 
>>>>> correctly sinec it's nooking for native bits and the python3-native had 
>>>>> not been installed yet.
>>>>> 
>>>>> 
>>>> 
>>>> in my build from scratch several times, I never had this issue. Did you do 
>>>> an incremental build to get to this issue ?
>>>> 
>>> 
>>> Yes, most of my builds are incremental until I throw them against the 
>>> Autobuilder!
>> 
>> Saul,
>> 
>> I was able to reproduce the incremental build issue. I have now fixed it and 
>> pushed a rebased branch to pull tree
>> in contrib. Please try it out
>> 
> 
> Almost there!  It looks like you have a ${PN} in the tarball name instead of 
> ${BPN} and it's causing a multilib failure for zeromq.
> 
>> ERROR: Fetcher failure: Fetch command failed with exit code 8, output:
>> http://download.zeromq.org/lib32-zeromq-3.2.2.tar.gz:
>> 2013-08-02 00:24:06 ERROR 404: Not Found.
>> 
>> ERROR: Function failed: Fetcher failure for URL: 
>> 'http://download.zeromq.org/lib32-zeromq-3.2.2.tar.gz'. Unable to fetch URL 
>> from any source.
>> ERROR: Logfile of failure stored in: 
>> /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-world/build/build/tmp/work/x86-pokymllib32-linux/lib32-zeromq/3.2.2-r1/temp/log.do_fetch.9470
> 
> Notice the lib32-zeromq-3.2.2.tar.gz instead of zeromq-3.2.2.tar.gz
> 
> Thanks
>       Sau!
> 
> 
>> Thanks
>> -Khem
>> 
>> 
>> 

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to