On Thursday 02 February 2012 12:50:16 Samuel Stirtzel wrote: > There are other CMake configure pitfalls (all cross compiling scripts > in kdelibs are commented out) but it seems that at least the most of > them showed already during build time.
Unfortunately when I tried to build kdelibs4 I got the following: | cd /home/paul/poky/poky/build-kde/tmp/work/i586-poky- linux/kdelibs4-4.8.0+git1+1439483a67135f483632f4c4cd239e96d2ed61fc- r0/git/build/kjs && /home/paul/poky/poky/build-kde/tmp/sysroots/x86_64- linux/usr/bin/icemaker /home/paul/poky/poky/build-kde/tmp/work/i586-poky- linux/kdelibs4-4.8.0+git1+1439483a67135f483632f4c4cd239e96d2ed61fc- r0/git/kjs/bytecode | /bin/sh: /home/paul/poky/poky/build-kde/tmp/sysroots/x86_64- linux/usr/bin/icemaker: No such file or directory | make[2]: *** [kjs/opcodes.h] Error 127 | make[2]: Leaving directory `/home/paul/poky/poky/build-kde/tmp/work/i586- poky-linux/kdelibs4-4.8.0+git1+1439483a67135f483632f4c4cd239e96d2ed61fc- r0/git/build' Any ideas? Is this a PARALLEL_MAKE issue? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
