Go to file
Yann E. MORIN 69036c20f1 fs/ext2: add ability to build ext3/4 too
Use the host-e2fsprogs to tune2fs the generated rootfs.ext2 image,
and upgrade it to either one of ext2, ext3 or ext4.

Since calling tune2fs may require running e2fsck (tune2fs will warn
to do so when certain FS options are changed), we systematically call
e2fsck. This makes the code path simpler, and as a side-effect checks
that genext2fs did not generate garbage.

In turn, e2fsck will unconditionally add a UUID to the filesystem,
which is bad for reproducibility, so we call tune2fs again to remove
the UUID. This does not require checking the filesystem.

To ensure compatibility of Buildroot's .config, leave ext2 as the
default. Boards' .config can override this at will.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Peter Korsgaard <jacmet@uclibc.org>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-12 14:39:24 +02:00
arch toolchain/arm: drop generic and old, add fa526/626, unify strongarm 2013-04-11 09:22:48 +02:00
board configs: add RaspberryPi defconfig 2013-03-26 14:00:29 +01:00
boot barebox: add 2013.04.0, remove 2012.12.1 2013-04-11 15:52:16 +02:00
configs nitrogen6x_defconfig: drop double linux tarball location 2013-04-11 10:10:48 +02:00
docs manual: add manual generation date/git revision in the manual text 2013-03-27 09:54:59 +01:00
fs fs/ext2: add ability to build ext3/4 too 2013-04-12 14:39:24 +02:00
linux linux: fix 3.8.x stable version 2013-04-12 10:05:13 +02:00
package fs/ext2: add ability to build ext3/4 too 2013-04-12 14:39:24 +02:00
support support/kconfig: upgrade to 3.9-rc2 2013-04-11 09:30:39 +02:00
system system/securetty: Add ttyPS[0-1] 2013-04-11 23:32:11 +02:00
toolchain toolchain-external: support more gdbserver locations 2013-04-11 21:47:57 +02:00
.defconfig buildroot: get rid of s390 support 2009-01-12 14:36:14 +00:00
.gitignore .gitignore: ignore more patch related files 2010-11-18 12:07:23 +01:00
CHANGES Update for 2013.02 2013-02-28 22:48:28 +01:00
Config.in rework patch model 2013-03-19 23:10:49 +01:00
Config.in.legacy gdb: convert to the package infrastructure 2013-04-11 21:46:32 +02:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Makefile support/kconfig: add support for olddefconfig 2013-04-11 09:58:12 +02:00
Makefile.legacy legacy: add error target for host-pkg-config 2012-11-30 12:07:09 -08:00

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
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 sort of
    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!

Offline build:
==============

In order to do an offline-build (not connected to the net), fetch all
selected source by issuing a
$ make source

before you disconnect.
If your build-host is never connected, then you have to copy buildroot
and your toplevel .config to a machine that has an internet-connection
and issue "make source" there, then copy the content of your dl/ dir to
the build-host.

Building out-of-tree:
=====================

Buildroot supports building out of tree with a syntax similar
to the Linux kernel. To use it, add O=<directory> to the
make command line, E.G.:

$ make O=/tmp/build

And all the output files (including .config) will be located under /tmp/build.

More finegrained configuration:
===============================

You can specify a config-file for uClibc:
$ make UCLIBC_CONFIG_FILE=/my/uClibc.config

And you can specify a config-file for busybox:
$ make BUSYBOX_CONFIG_FILE=/my/busybox.config

To use a non-standard host-compiler (if you do not have 'gcc'),
make sure that the compiler is in your PATH and that the library paths are
setup properly, if your compiler is built dynamically:
$ make HOSTCC=gcc-4.3.orig HOSTCXX=gcc-4.3-mine

Depending on your configuration, there are some targets you can use to
use menuconfig of certain packages. This includes:
$ make HOSTCC=gcc-4.3 linux-menuconfig
$ make HOSTCC=gcc-4.3 uclibc-menuconfig
$ make HOSTCC=gcc-4.3 busybox-menuconfig

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@uclibc.org