65473afee4
uClibc-ng does not support linuxthreads or linuxthreads.old on architectures that have NPTL support. This creates another complicated dependency: dependeing on the uClibc version being used, not the same thread implementations are available. In order to handle this situation, this patch introduces three hidden booleans: - BR2_UCLIBC_VERSION_SUPPORTS_LINUXTHREADS - BR2_UCLIBC_VERSION_SUPPORTS_LINUXTHREADS_OLD - BR2_UCLIBC_VERSION_SUPPORTS_NPTL They are selected by the different uClibc versions, depending on which thread implementation they support on the different architectures. Then, the choice of the thread implementation can rely on those booleans to know if a given thread implementation is available in the current architecture / uClibc version selection. This makes sure that unusable thread implementation do not get selected, therefore fixing build issues such as: http://autobuild.buildroot.org/results/89e/89e423bee040cbce3e82cd89f1191efaac490c0d/ The support table is as follows (only taking into account architectures that allow the selection of BR2_TOOLCHAIN_BUILDROOT_UCLIBC, other architectures are not considered) : ----uclibc---- uclibc-xtensa- --uclibc-arc-- --uclibc-ng--- LT LT.old NPTL LT LT.old NPTL LT LT.old NPTL LT LT.old NPTL arc(le|eb) y y n n n n (1) arm(eb) y y y n y y (2) bfin n y n y y n i386 y y y n n y (3) m68k y y y y y n mips(64)(el) y y y n n y powerpc y y y n n y sh y y y n n y sparc y y y n n y xtensa n y n n n y x86_64 y y y n n y (1) : uclibc-ng only has NPTL support for ARC but it requires a more recent compiler version that hasn't been officially released by Synopsys. (2) : the general idea of uclibc-ng is to only support NPTL on architectures where it is available. However, in order to support ARM noMMU platforms, LT.old support has been kept on ARM. (3) : except i386 itself, which doesn't have what's needed for NPTL support. i386 is simply not supported by uclibc-ng basically. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| .defconfig | ||
| .gitignore | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| Makefile | ||
| Makefile.legacy | ||
| 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