OK this is a hit or miss since trying another bitbake failed. So at this 
point I am lost. And not sure where else to go for help so any suggestions 
would be helpful.

On Monday, June 13, 2016 at 2:51:54 AM UTC-4, Michael wrote:
>
> Lars
>
> Actually, seems I was able to bitbake without errors by deleting 
> python-imaging from meta and using the latest copy of meta-ros. Still 
> waiting for wic to finish, seems to take forever each time I make a change. 
> Also noticed the depends needs to have tcl added, will leave a message on 
> the git to see if it can be modified. Thanks again for all of your help.
>
> Cheers, Michael
>
> On Saturday, June 11, 2016 at 12:50:10 PM UTC-4, Michael wrote:
>>
>> Lars
>>
>> I totally agree that there are many. I did find that meta-ros supplies 
>> python-imagining. For now am still working with the issue trying to 
>> determine the actual fault. One thing I did notice and would like to 
>> confirm it is not the problem is - 
>>
>> cc1: warning: include location "/usr/include/tcl8.6" is unsafe for 
>> cross-compilation [-Wpoison-system-directories]
>>
>> Would like to stick with a standard build so I do not face issues down 
>> the road. Thanks again.
>>
>> Cheers, Michael
>>
>> On Wednesday, June 8, 2016 at 4:39:06 AM UTC-4, Lukas Bulwahn wrote:
>>>
>>> Dear Michael, dear Lars,
>>>
>>> there is huge number of different configurations and versions (in total 
>>> >10e9 or probably even >10e12 possible build configurations) to use 
>>> meta-ros with openembedded-core and the meta-openembedded layers (so much 
>>> larger than the number of users). Checking all configurations is simply 
>>> impossible for this small project and hence, some issues remain unchecked.
>>> The python-imaging recipe is part of the openembedded-core layer (at 
>>> least it was until three days ago as you noticed); and they provide an own 
>>> mailing list to discuss issues on the openembedded-core layer.
>>>
>>> Simply dropping python-imaging from rosbag might work, but possibly you 
>>> will stumble over python runtime failures later when you need this library.
>>>
>>> Lukas
>>>
>>

Reply via email to