mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-09-08 23:51:08 -09:00
690d8ff5bc
Fixes mesa3d build errors: http://autobuild.buildroot.net/results/d10/d105a0b3ca11fad34f9a2dae0dae9bd041d918a6/ http://autobuild.buildroot.net/results/d71/d7121443715024d15a66ff1abf1261803c10cd35/ http://autobuild.buildroot.net/results/ce6/ce64164d76972f82acab277afc9c95a876c6433e/ checking for python2... python2 checking python2 module: libxml2... no configure: error: failed to find required module libxml2 make: *** [/home/test/test/1/output/build/mesa3d-10.0.4/.stamp_configured] Error 1 mesa3d needs python2 bindings installed by libxml2. To enforce their build option BR2_PACKAGE_HOST_LIBXML2_PYTHON is used exclusively by mesa3d so this patch does not affect other packages. Without this patch host-libxml2 installs the python bindings in $(HOST_DIR)/usr/lib/$(PYTHON3_VERSION_MAJOR) using this defconfig: BR2_PACKAGE_MESA3D=y BR2_PACKAGE_PYTHON3=y because $(HOST_DIR)/usr/bin/python points to $(HOST_DIR)/usr/bin/python3: Quote from host-libxml2 configure log: Found python in /home/fli4l/br2/buildroot/output/host/usr/bin/python Found Python version 3.4 HOST_$(PACKAGE)_NEEDS_HOST_PYTHON does not work here because libxml2 does not use the python-package infrastructure. libxml2-python2.patch extends the python detection code in host-libxml2 to first look for python2, to keep the patch small I did not update the indentions: Found python2 in /home/fli4l/br2/buildroot/output/host/usr/bin/python2 Found Python version 2.7 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Tested-by: Samuel Martin <s.martin49@gmail.com> 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