Helpful answer from Josh Lewis - this looks like a shortcoming in the build scripts, that fail to detect/parse the missing library issue when trying to locate the tools' version numbers.
I had the same issue but with gdb, which gave a different error syndrome; clue was in the name of the command being run:
NOTE: <type 'exceptions.IndexError'>:list index out of range while evaluating:
${@csl_get_gdb_version(d)}
ERROR: list index out of range while parsing /home/fred/freescale/QorIQ-DPAA-SDK-20111026-systembuilder/sb-core/recipes/meta/external-toolchain-csl.bb
NOTE: Handling BitBake files: \ (0408/0409) [99 %]Command execution failed: Traceback (most recent call last):
File "/home/fred/freescale/QorIQ-DPAA-SDK-20111026-systembuilder/scripts/bitbake/lib/bb/command.py", line 85, in runAsyncCommand
self.cooker.updateCache()
File "/home/fred/freescale/QorIQ-DPAA-SDK-20111026-systembuilder/scripts/bitbake/lib/bb/cooker.py", line 829, in updateCache
if not self.parser.parse_next():
File "/home/fred/freescale/QorIQ-DPAA-SDK-20111026-systembuilder/scripts/bitbake/lib/bb/cooker.py", line 1022, in parse_next
raise ParsingErrorsFound
ParsingErrorsFound
In this case for me, it was libncurses.so.5
The scripts should all be updated to detect the missing library conditions when trying to determine the tool version.