Go to file
Gustavo Zacarias 1cd15cb15a dhcp: update dhclient-script
The previous no-op dhclient-script is useless and in fact can lead
users to believe things will work.
dhclient-script is supposed to, among many other things, bring the
interface up for dhclient to pump an address, set the interface
address, set resolv.conf appropiately and set the default gateway.
It's a complex script since it has to deal with a lot of details so
let's just use the best fit which is the OpenWRT one since it uses the
"legacy" tools (ifconfig, route, ...) which can be easily provided by
busybox and/or net-tools.
There are newer and more feature-complete versions around but they
require full iproute2 ip and wouldn't fit as well with the busybox-only
approach.

License: likely GPLv2+
Source:
http://git.openwrt.org/?p=packages.git;a=blob;f=net/isc-dhcp/files/dhclient-script;h=4afebc0ad20ebac51c5baae5ed01c6713e3a0fd0;hb=HEAD

Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-11-28 12:34:55 +01:00
arch arch/Config.in.x86: drop BR2_x86_generic 2014-11-07 19:51:06 +01:00
board configs/apf9328: bump to a modern kernel 2014-11-11 23:00:58 +01:00
boot barebox: bump to version 2014.11.0 2014-11-06 09:13:28 +01:00
configs configs/apf9328: bump to a modern kernel 2014-11-11 23:00:58 +01:00
docs manual: Add newline before block code 2014-11-22 20:13:43 +01:00
fs package: indentation cleanup 2014-10-26 05:47:05 +01:00
linux linux: bump default version to 3.17.4 2014-11-21 21:45:38 +01:00
package dhcp: update dhclient-script 2014-11-28 12:34:55 +01:00
support Change /bin/bash shebangs into /usr/bin/env bash 2014-10-25 01:55:37 +02:00
system system/permissions: /etc/random-seed must be mode 600 2014-11-25 22:37:43 +01:00
toolchain toolchain/external: fix building the wrapper on MIPS 2014-11-27 22:47:08 +01:00
.defconfig buildroot: get rid of s390 support 2009-01-12 14:36:14 +00:00
.gitignore update gitignore 2013-05-04 12:41:55 +02:00
CHANGES Update for 2014.11-rc2 2014-11-21 13:19:45 +01:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Config.in Config.in: remove BR2_DEBIAN_MIRROR completely 2014-10-25 11:26:45 +02:00
Config.in.legacy Config.in.legacy: fix typo 2014-11-09 08:54:47 +01:00
Makefile Makefile: use more sensible names for locale related variables 2014-11-21 21:50:35 +01:00
Makefile.legacy Makefile.legacy: fix recursive invocation with BUILDROOT_DL_DIR and _CONFIG 2014-02-11 08:14:57 +01:00
README docs: Move README file to root 2014-03-03 21:28:39 +01:00

README

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@buildroot.org