I just built an angstrom image and thinks failed. lzma image depends on lzma-native, grep and other programs that use .xz suffix for tarballs depend on xz-native. This fact itself is bad - it creates file conflicts in the sysroot.
But things were even worse: - xz-native staged xz binary and lzma as a symlink to xz. - lzma-native tried to stage lzma 4 minutes later But staging of lzma apparently went wrong. Instead of removal of lzma symlink and installation of lzma binary, bitbake followed the symlink and staged lzma as xz with a result of broken build environment. I have bitbake-1.8.18. -- ________________________________________________________________________ Stanislav Brabec http://www.penguin.cz/~utx/zaurus _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
