While I had this working I thought I'd complete the Appendix B example for the CONFIG_SMP change. I'm finding problems with the compile step after menuconfig is run to turn off SMP. I get a mismatch

I've updated the SRCREVs: bootfiles : 542ee2c3a5aea50377b97ec0308eb884900512ca kernel : f679f0534867d64a3672108d73bed5d349728f73 This build ok, but the kernel doesn't boot (screen shows the

ok, better answer than mine, and added to the FAQ. http://www.crashcourse.ca/wiki/index.php/Yocto_FAQ#How_can_I_remove_all_of_the_build_output_so_I_can_start_over.3F rday --

Jim, Yes - I am still running the very last part of my test. If that is the change then I will make it to the 1.2 version of the manual and publish it to the website. Scott

hey, there's an FAQ entry for that! :-) well, sort of ... if you want to avoid all that source

I just delete the tmp directory and that seems to get the result I want - remove all the binaries but doesn't delete the sources.

So now that Denzil has a branch in poky-extra, the only doc change is to add the checkout -b denzil statement for the poky-extra directory. Everything else is correct. Jim A

<dallas.a.clement@...> wrote: by default DL_DIR lives outside TMPDIR so you can delete the TMPDIR

I just finished testing with Denzil branch on poky and poky-extra. I made the Hello printk mods and used the new bbappend that Bruce setup in poky-extra for denzil. I think he had already uncommented

I'd like to clean all of my build output so that I can rebuild with a different toolchain. What is the best way to clean without having to redownload all of my source packages again? I can see that

Attendees: LaurentiuP, Jefro, Richard, Bruce, Michael, Ross, Mark, Sean, Jeff, Tom, Darren, Gilbert, Denys, Jessica, ScottR, Saul, Paul, Jim, Ciby, Alex, Song   Gilbert is from mentor Graphics,

Well, granted that OE/Poky/Yocto is fairly complex. I've followed OE for years (though never successfully built anything with it). I had my first successful build of (Poky?, Yocto?) just

When I attempted to rebuild minimal I hit the same error you did Jim regarding kern-tools-native. This would be expected as Bruce pointed out that problem is alive in denzil. I am going to set the

No, an FAQ should not get you the expertise to create a commercial grade product. Reading the documentation should though. You don't want users to have to study source code.

I am on task 1507 of 1606 of a minimal build (from the example). No issues so far.

Fixing the license check was just a matter of me locking the SRCREV for the tools to a value that works for denzil. I just pushed a denzil branch to poky-extras that built and booted the yocto kernel

That's never been case on this list as far as I recall, folk here are pretty responsive to questions being asked. At the same time, OE/Poky/Yocto is a fairly complex framework and nobody should

that's fine, i'll at least note this shortcut. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario,

yes, but it would also need information on ordering of consultation. from bitbake.conf: require conf/abi_version.conf include conf/site.conf include conf/auto.conf include conf/local.conf include

I have thought about this - it would be great if oe-init-build-env could copy/symlink your customised version from somewhere automatically every time; however the question would be how would it know