97703978ac
After switching TARGET_LDFLAGS from --static to -static, one issue appears: from the point of view of libtool, -static only means to link statically against the 'uninstalled libtool libraries' (i.e the libraries that libtool has built in the current package), but otherwise links dynamically with the other libraries. To really get a completely static build, you need to pass -all-static to libtool. Unfortunately, -all-static is only a valid option for libtool, not as a general LDFLAGS, so we cannot to TARGET_LDFLAGS = -all-static without breaking virtually all packages. As pointed out 10 years ago on the libtool mailing list, the current naming of the options is very confusing and the source of issues, and there was a proposal to change -static to have the behavior of -all-static, and instead introduce a separate -lt-static to have the current behavior of -static. But that never got merged, because it was breaking the current behavior. See: http://lists.gnu.org/archive/html/libtool/2004-11/msg00017.html However, in Buildroot, when we pass -static, we really mean it, and we want a completely static build. Therefore, this patch adapts our ltmain.sh patches so that they alter the behavior of -static to make it work like -all-static. The changes are small and quite easy to understand, and have been tested to work fine with a small selection of packages. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
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