On PPC Macintosh, `uname -m` is "Power Macintosh". It looks like directory paths which rely on the output of uname to construct architecture-specific names, aren't always getting quoted when passed to external shell commands. For example, building gnu-config-native, we get a "cp" command that looks like this: cp "/Users/matt/poky/meta/packages/gnu-config/gnu-config/gnu-configize.in" \ "/Users/matt/poky/build/tmp/work/Power" \ "Macintosh-darwin/gnu-config-native-0.1+cvs20050701-r4/./" I had a look around in the BitBake sources, but didn't find any explicit uses of "cp", so I'm not sure about which callsite does this.
Its from base.bbclass in the unpack task. I think I've committed a fix for this and a few others but it looks like we have many other call sites which aren't quoting paths safely. I'll continue to work on this but it could take a while to find them all. Note that I don't have a machine with a space in "uname -m" so this is difficult for me to test.
This may be a lost cause. Configure scripts created by autoconf often do things like: (cd $srcdir && test -r ./$ac_unique_file) 2>/dev/null || { echo "$as_me: error: sources are in $srcdir, but \`cd $srcdir' does not work ">72 } I don't think that will ever work unless $srcdir is double-quoted.
I think the current approach possibly is a lost cause. I've had to revert the change to base.bbclass I made since things like 'cp /someplace/*.m4 /someotherplace' don't work if you add in quotes since it disables the shell expansion. I was thinking we need to inject quotes at the point the bad paths in question enter Poky so that things like build/tmp/work/Power Macintosh-darwin/ become build/tmp/work/"Power Macintosh-darwin"/ to avoid the above problem. That still leaves the problem of configure and probably other tools failing to cope with these kind of paths though. It might be possible to substitute the space out the paths causing problems since they're ones Poky creates although that might be quite an involved job.
This is more of a can't fix rather than won't fix since until autotools and other utils accept spaces in its paths, there is no point in changing bitbake and the metadata as previously mentioned.
Changing OS to OS X 10.x