On Mon, 2014-04-14 at 18:44 -0400, Denys Dmytriyenko wrote: > On Mon, Apr 14, 2014 at 02:11:05PM -0600, Gary Thomas wrote: > > Very interesting results! These are the results from the build hosts I > > have: > > Fedora 13 (i686) - fails > > Fedora 17 (i686) - fails > > Ubuntu 12.04 (x86_64) - boots > > Interesting indeed. I have no idea what's so special about Fedora host - this > is the first time I hear about issues with it. I may try experimenting with > different VMs once I have more time...
I've been having a look at this. The biggest differences I can find between working and non working builds is the path length to the build directory for the kernel. This is from comparing vmlinux files from working and non working builds. Works: /home/paul/poky/build/tmp/work/beaglebone-poky-linux-gnueabi Doesn't Work: /media/data1/build1/poky/build/tmp/work/beaglebone-poky-linux-gnueabi I also have been wondering if the version strings may be making a difference. http://dan.rpsys.net/uImage-rp2 is a uImage from a broken build where I truncated the path length to a "working" build path length and patched in the same version strings: const char linux_banner[] = "Linux version 3.14.0-yocto-standard (paul@ubuntu-build01) (gcc version 4.8.2 (GCC) ) #1 PREEMPT Mon Apr 14 16:00:52 BST 2014\n"; const char linux_proc_banner[] = "%s version %s (paul@ubuntu-build01) (gcc version 4.8.2 (GCC) ) %s\n"; to init/version.c. I don't have hardware and would be interested to know if the kernel linked to above works or not. If it doesn't, it rules out these path and string lengths, if it does work, it points to a problem there. Cheers, Richard -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto