491b44e86a
buildroot, the header files will be re-extracted, but they will not be put in exactly the right place if the name of the extracted directory includes the kernel version numbers. For example, linux-libc-headers-2.4.25.tar.bz2 will be extracted to $(TOOLCHAIN_BUILD_DIR)/linux-libc-headers-2.4.25, and then the mv command will move the newly extracted headers into the already existing $(TOOLCHAIN_BUILD_DIR)/linux directory, instead of replacing that directory as desired. The fix is to first remove the $(TOOLCHAIN_BUILD_DIR)/linux directory and then do the mv command. http://bugs.busybox.net/view.php?id=296 |
||
---|---|---|
docs | ||
package | ||
target | ||
toolchain | ||
.defconfig | ||
Config.in | ||
Makefile |
To build and use the buildroot stuff, do the following: 1) run 'make' 2) select the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) Use your shiny new root filesystem. Depending on which sortof root filesystem you selected, you may want to loop mount it, chroot into it, nfs mount it on your target device, burn it to flash, or whatever is appropriate for your target system. You do not need to be root to build or run buildroot. Have fun! -Erik Please feed suggestions, bug reports, insults, and bribes back to: Erik Andersen <andersen@codepoet.org>