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 >
