On Fri, 14 Dec 2012, Scott Garman wrote:
The do_deploy step is what actually copies the kernel to the images
directory. You can force this to happen again with:
bitbake virtual/kernel -c deploy
Not sure if you need a -f in there too (which would force the step to run
regardless of sstate stamp status).
I think something about the fact that the same kernel is often re-used for
several rootfs images for the same MACHINE is why we're more careful about
over-writing the kernel in the images directory. That's my guess.
Scott,
Thanks for the reply, I do have a modules tarball, not sure how it was
created, but it is there again.:-)
--
Regards,
Alan
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
