Go to file
Simon Dawson 0e8dafcb3e sudo: fix main executable permissions
The sudo executable is installed without the setuid bit set, which prevents
sudo from working.

This patch adds a post-install hook to fix the permissions of the sudo
executable.

Signed-off-by: Simon Dawson <spdawson@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-08-04 23:43:54 +02:00
board qemu/x86: update to use kernel 3.4.7 2012-07-31 23:40:40 +02:00
boot Add MXS bootlets package 2012-07-21 00:34:57 +02:00
configs qemu/x86: update to use kernel 3.4.7 2012-07-31 23:40:40 +02:00
docs docs: update links to the manual 2012-08-02 10:25:23 +02:00
fs Add the www-data user group to the skeleton target filesystem 2012-04-26 15:22:15 +02:00
linux linux: bump default to kernel version 3.4.7 2012-07-31 23:38:55 +02:00
package sudo: fix main executable permissions 2012-08-04 23:43:54 +02:00
support pkg-stats: ensure infratype is reset for every package 2012-07-31 21:38:16 +02:00
target Simplify x86 target architecture variant handling 2012-07-31 00:00:29 +02:00
toolchain toolchain-external: microblaze toolchains are glibc-based 2012-08-02 21:44:15 +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 2012.08-rc1 2012-08-01 20:46:31 +02:00
Config.in Package downloads: allow restricting to primary site only 2012-07-22 18:29:33 +02:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Makefile Update for 2012.08-rc1 2012-08-01 20:46:31 +02: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