Table of Contents
- I. Getting started
- II. User guide
- 6. Buildroot configuration
- 7. Configuration of other components
- 8. General Buildroot usage
- 8.1. make tips
- 8.2. Understanding when a full rebuild is necessary
- 8.3. Understanding how to rebuild packages
- 8.4. Offline builds
- 8.5. Building out-of-tree
- 8.6. Environment variables
- 8.7. Dealing efficiently with filesystem images
- 8.8. Graphing the dependencies between packages
- 8.9. Graphing the build duration
- 8.10. Graphing the filesystem size contribution of packages
- 8.11. Integration with Eclipse
- 8.12. Advanced usage
- 9. Project-specific customization
- 9.1. Recommended directory structure
- 9.2. Keeping customizations outside of Buildroot
- 9.3. Storing the Buildroot configuration
- 9.4. Storing the configuration of other components
- 9.5. Customizing the generated target filesystem
- 9.6. Adding custom user accounts
- 9.7. Customization after the images have been created
- 9.8. Adding project-specific patches
- 9.9. Adding project-specific packages
- 9.10. Quick guide to storing your project-specific customizations
- 10. Frequently Asked Questions & Troubleshooting
- 10.1. The boot hangs after Starting network…
- 10.2. Why is there no compiler on the target?
- 10.3. Why are there no development files on the target?
- 10.4. Why is there no documentation on the target?
- 10.5. Why are some packages not visible in the Buildroot config menu?
- 10.6. Why not use the target directory as a chroot directory?
- 10.7. Why doesn’t Buildroot generate binary packages (.deb, .ipkg…)?
- 10.8. How to speed-up the build process?
- 11. Known issues
- 12. Legal notice and licensing
- 13. Beyond Buildroot
- III. Developer guide
- 14. How Buildroot works
- 15. Coding style
- 16. Adding support for a particular board
- 17. Adding new packages to Buildroot
- 17.1. Package directory
- 17.2. Config files
- 17.3. The
.mkfile - 17.4. The
.hashfile - 17.5. Infrastructure for packages with specific build systems
- 17.6. Infrastructure for autotools-based packages
- 17.7. Infrastructure for CMake-based packages
- 17.8. Infrastructure for Python packages
- 17.9. Infrastructure for LuaRocks-based packages
- 17.10. Infrastructure for Perl/CPAN packages
- 17.11. Infrastructure for virtual packages
- 17.12. Infrastructure for packages using kconfig for configuration files
- 17.13. Infrastructure for rebar-based packages
- 17.14. Infrastructure for Waf-based packages
- 17.15. Infrastructure for packages building kernel modules
- 17.16. Infrastructure for asciidoc documents
- 17.17. Infrastructure specific to the Linux kernel package
- 17.18. Hooks available in the various build steps
- 17.19. Gettext integration and interaction with packages
- 17.20. Tips and tricks
- 17.21. Conclusion
- 18. Patching a package
- 19. Download infrastructure
- 20. Debugging Buildroot
- 21. Contributing to Buildroot
- 22. DEVELOPERS file and get-developers
- IV. Appendix
List of Examples
Buildroot 2017.02.9 manual generated on 2018-01-01 -11:25:52 UTC from git revision 8f03647169
The Buildroot manual is written by the Buildroot developers. +
Table of Contents
- I. Getting started
- II. User guide
- 6. Buildroot configuration
- 7. Configuration of other components
- 8. General Buildroot usage
- 8.1. make tips
- 8.2. Understanding when a full rebuild is necessary
- 8.3. Understanding how to rebuild packages
- 8.4. Offline builds
- 8.5. Building out-of-tree
- 8.6. Environment variables
- 8.7. Dealing efficiently with filesystem images
- 8.8. Graphing the dependencies between packages
- 8.9. Graphing the build duration
- 8.10. Graphing the filesystem size contribution of packages
- 8.11. Integration with Eclipse
- 8.12. Advanced usage
- 9. Project-specific customization
- 9.1. Recommended directory structure
- 9.2. Keeping customizations outside of Buildroot
- 9.3. Storing the Buildroot configuration
- 9.4. Storing the configuration of other components
- 9.5. Customizing the generated target filesystem
- 9.6. Adding custom user accounts
- 9.7. Customization after the images have been created
- 9.8. Adding project-specific patches
- 9.9. Adding project-specific packages
- 9.10. Quick guide to storing your project-specific customizations
- 10. Frequently Asked Questions & Troubleshooting
- 10.1. The boot hangs after Starting network…
- 10.2. Why is there no compiler on the target?
- 10.3. Why are there no development files on the target?
- 10.4. Why is there no documentation on the target?
- 10.5. Why are some packages not visible in the Buildroot config menu?
- 10.6. Why not use the target directory as a chroot directory?
- 10.7. Why doesn’t Buildroot generate binary packages (.deb, .ipkg…)?
- 10.8. How to speed-up the build process?
- 11. Known issues
- 12. Legal notice and licensing
- 13. Beyond Buildroot
- III. Developer guide
- 14. How Buildroot works
- 15. Coding style
- 16. Adding support for a particular board
- 17. Adding new packages to Buildroot
- 17.1. Package directory
- 17.2. Config files
- 17.3. The
.mkfile - 17.4. The
.hashfile - 17.5. Infrastructure for packages with specific build systems
- 17.6. Infrastructure for autotools-based packages
- 17.7. Infrastructure for CMake-based packages
- 17.8. Infrastructure for Python packages
- 17.9. Infrastructure for LuaRocks-based packages
- 17.10. Infrastructure for Perl/CPAN packages
- 17.11. Infrastructure for virtual packages
- 17.12. Infrastructure for packages using kconfig for configuration files
- 17.13. Infrastructure for rebar-based packages
- 17.14. Infrastructure for Waf-based packages
- 17.15. Infrastructure for packages building kernel modules
- 17.16. Infrastructure for asciidoc documents
- 17.17. Infrastructure specific to the Linux kernel package
- 17.18. Hooks available in the various build steps
- 17.19. Gettext integration and interaction with packages
- 17.20. Tips and tricks
- 17.21. Conclusion
- 18. Patching a package
- 19. Download infrastructure
- 20. Debugging Buildroot
- 21. Contributing to Buildroot
- 22. DEVELOPERS file and get-developers
- IV. Appendix
List of Examples
Buildroot 2017.02.10 manual generated on 2018-01-31 +19:26:28 UTC from git revision 91850b3497
The Buildroot manual is written by the Buildroot developers. It is licensed under the GNU General Public License, version 2. Refer to the COPYING file in the Buildroot sources for the full text of this license.
Copyright © 2004-2017 The Buildroot developers
Buildroot is a tool that simplifies and automates the process of @@ -16,8 +16,8 @@ processors everyone is used to having in his PC. They can be PowerPC processors, MIPS processors, ARM processors, etc.
Buildroot supports numerous processors and their variants; it also comes with default configurations for several boards available off-the-shelf. Besides this, a number of third-party projects are based on, -or develop their BSP [1] or -SDK [2] on top of Buildroot.
Buildroot is designed to run on Linux systems.
While Buildroot itself will build most host packages it needs for the +or develop their BSP [1] or +SDK [2] on top of Buildroot.
Buildroot is designed to run on Linux systems.
While Buildroot itself will build most host packages it needs for the compilation, certain standard Linux utilities are expected to be already installed on the host system. Below you will find an overview of the mandatory and optional packages (note that package names may vary @@ -272,7 +272,7 @@ processor. Under most Linux systems, the compilation toolchain uses the GNU libc (glibc) as the C standard library. This compilation toolchain is called the "host compilation toolchain". The machine on which it is running, and on which you’re working, is called the "host -system" [3].
The compilation toolchain is provided by your distribution, and +system" [3].
The compilation toolchain is provided by your distribution, and Buildroot has nothing to do with it (other than using it to build a cross-compilation toolchain and other tools that are run on the development host).
As said above, the compilation toolchain that comes with your system
@@ -551,7 +551,7 @@ The third solution is systemd.
The solution recommended by Buildroot developers is to use the BusyBox init as it is sufficient for most embedded -systems. systemd can be used for more complex situations.
[3] This terminology differs from what is used by GNU +systems. systemd can be used for more complex situations.
[3] This terminology differs from what is used by GNU configure, where the host is the machine on which the application will run (which is usually the same as target)
Before attempting to modify any of the components below, make sure you
have already configured Buildroot itself, and have enabled the
@@ -2673,7 +2673,7 @@ flags.
The argument to be given to LIBFOO_CONFIG_SCRIPTS is the file name(s)
of the shell script(s) needing fixing. All these names are relative to
$(STAGING_DIR)/usr/bin and if needed multiple names can be given.
In addition, the scripts listed in LIBFOO_CONFIG_SCRIPTS are removed
-from $(TARGET_DIR)/usr/bin, since they are not needed on the target.
Example 17.1. Config script: divine package
Package divine installs shell script $(STAGING_DIR)/usr/bin/divine-config.
So its fixup would be:
DIVINE_CONFIG_SCRIPTS = divine-config
Example 17.2. Config script: imagemagick package:
Package imagemagick installs the following scripts:
+from $(TARGET_DIR)/usr/bin, since they are not needed on the target.
Example 17.1. Config script: divine package
Package divine installs shell script $(STAGING_DIR)/usr/bin/divine-config.
So its fixup would be:
DIVINE_CONFIG_SCRIPTS = divine-config
Example 17.2. Config script: imagemagick package:
Package imagemagick installs the following scripts: $(STAGING_DIR)/usr/bin/{Magick,Magick++,MagickCore,MagickWand,Wand}-config
So it’s fixup would be:
IMAGEMAGICK_CONFIG_SCRIPTS = \
Magick-config Magick++-config \
MagickCore-config MagickWand-config Wand-configOn line 14, we specify the list of dependencies this package relies @@ -4601,7 +4601,7 @@ large number of commits in the series;
The main Buildroot directory contains a file named DEVELOPERS that
+- http://code.bulix.org/
The main Buildroot directory contains a file named DEVELOPERS that
lists the developers involved with various areas of Buildroot. Thanks
to this file, the get-developer tool allows to:
-
Calculate the list of developers to whom patches should be sent, by
diff --git a/bsp/buildroot/docs/manual/manual.pdf b/bsp/buildroot/docs/manual/manual.pdf
index d03ffc30..6500d7ff 100644
Binary files a/bsp/buildroot/docs/manual/manual.pdf and b/bsp/buildroot/docs/manual/manual.pdf differ
diff --git a/bsp/buildroot/docs/manual/manual.text b/bsp/buildroot/docs/manual/manual.text
index ceeeaf5b..c6f25028 100644
--- a/bsp/buildroot/docs/manual/manual.text
+++ b/bsp/buildroot/docs/manual/manual.text
@@ -155,8 +155,8 @@ List of Examples
---------------------------------------------------------------------
-Buildroot 2017.02.9 manual generated on 2018-01-01 11:25:58 UTC from
-git revision 8f03647169
+Buildroot 2017.02.10 manual generated on 2018-01-31 19:26:34 UTC from
+git revision 91850b3497
The Buildroot manual is written by the Buildroot developers. It is
licensed under the GNU General Public License, version 2. Refer to
diff --git a/bsp/buildroot/package/Makefile.in b/bsp/buildroot/package/Makefile.in
index b32ad8e4..523cc678 100644
--- a/bsp/buildroot/package/Makefile.in
+++ b/bsp/buildroot/package/Makefile.in
@@ -388,7 +388,7 @@ DISABLE_NLS :=--disable-nls
endif
ifneq ($(BR2_INSTALL_LIBSTDCPP),y)
-TARGET_CONFIGURE_OPTS += CXX=false
+TARGET_CONFIGURE_OPTS += CXX=false CXXCPP=cpp
endif
ifeq ($(BR2_STATIC_LIBS),y)
diff --git a/bsp/buildroot/package/avahi/avahi_tmpfiles.conf b/bsp/buildroot/package/avahi/avahi_tmpfiles.conf
index f9aebdfd..da23c147 100644
--- a/bsp/buildroot/package/avahi/avahi_tmpfiles.conf
+++ b/bsp/buildroot/package/avahi/avahi_tmpfiles.conf
@@ -1 +1 @@
-d /tmp/avahi-autopid 0755 avahi avahi
+d /tmp/avahi-autoipd 0755 avahi avahi
diff --git a/bsp/buildroot/package/berkeleydb/0001-cwd-db_config.patch b/bsp/buildroot/package/berkeleydb/0001-cwd-db_config.patch
new file mode 100644
index 00000000..08ce5a39
--- /dev/null
+++ b/bsp/buildroot/package/berkeleydb/0001-cwd-db_config.patch
@@ -0,0 +1,21 @@
+Do not access DB_CONFIG when db_home is not set
+
+Fixes CVE-2017-10140:
+https://bugzilla.redhat.com/show_bug.cgi?id=1464032#c9
+
+Downloaded from
+http://pkgs.fedoraproject.org/cgit/rpms/libdb.git/commit/?id=8047fa8580659fcae740c25e91b490539b8453eb
+
+Signed-off-by: Bernd Kuhls
++#endif ++ ++DH *get_dh2048() ++{ ++ static unsigned char dhp_2048[] = { ++ 0xBF, 0x6C, 0xC6, 0xBD, 0xEA, 0x10, 0x84, 0x59, 0x40, 0xC2, ++ 0xC6, 0xA2, 0x9B, 0x19, 0xD3, 0x2E, 0x2F, 0xAB, 0xE6, 0xE4, ++ 0x1E, 0x91, 0x0D, 0x59, 0xDC, 0x96, 0x3F, 0x6E, 0x65, 0x38, ++ 0xB9, 0xBE, 0xBB, 0x8F, 0xDF, 0x73, 0xAC, 0xAC, 0xB3, 0x2F, ++ 0xA7, 0x02, 0x0B, 0x87, 0xB7, 0x3F, 0x3A, 0x42, 0x8A, 0x94, ++ 0xDD, 0xEC, 0x33, 0xA4, 0x25, 0xB1, 0xBF, 0x84, 0x91, 0x87, ++ 0xD8, 0x1C, 0x42, 0xB9, 0x8E, 0x00, 0x1F, 0x49, 0xED, 0x57, ++ 0xA4, 0x48, 0xB0, 0xCC, 0xD8, 0xB8, 0x83, 0xCA, 0x3E, 0xDF, ++ 0xA2, 0xF2, 0x07, 0x71, 0x71, 0x18, 0x1F, 0x50, 0x45, 0x3A, ++ 0x66, 0x04, 0x7F, 0x15, 0xB2, 0xA8, 0x02, 0x77, 0xCE, 0xC6, ++ 0xF9, 0x7C, 0x63, 0xE4, 0x52, 0x41, 0xFA, 0x62, 0xB9, 0x0D, ++ 0xDC, 0x08, 0x62, 0xEC, 0x00, 0xAB, 0xB0, 0xF7, 0x79, 0x48, ++ 0x75, 0x22, 0x85, 0xCC, 0x67, 0x3C, 0xEA, 0x09, 0x32, 0xAC, ++ 0x30, 0xED, 0x1E, 0x67, 0xDC, 0x74, 0xF8, 0xD9, 0xC3, 0xD0, ++ 0xA0, 0x60, 0x4D, 0xCE, 0x52, 0xBC, 0xA3, 0xE5, 0x18, 0x7B, ++ 0x0B, 0xC8, 0xCE, 0x70, 0xA2, 0xC8, 0x21, 0xCA, 0xCE, 0xA5, ++ 0xD4, 0xCB, 0x85, 0xFC, 0xC7, 0x07, 0x5C, 0x05, 0x87, 0xFC, ++ 0x2F, 0x67, 0x4D, 0x2D, 0x4F, 0xA4, 0xEE, 0x63, 0x98, 0x49, ++ 0xE4, 0x2E, 0xD7, 0x3F, 0x7D, 0x69, 0x68, 0x0A, 0xA2, 0x3E, ++ 0x5A, 0x04, 0xD4, 0xDD, 0xBB, 0xC7, 0xB4, 0x34, 0xB7, 0x21, ++ 0xD3, 0xAC, 0x99, 0xD7, 0x87, 0x45, 0x5E, 0x18, 0x68, 0x16, ++ 0x3A, 0xAF, 0xE2, 0x04, 0x57, 0xB8, 0x6A, 0xB8, 0x2F, 0x75, ++ 0xD5, 0x79, 0x96, 0x60, 0x8D, 0xD1, 0xCC, 0xD1, 0x33, 0x85, ++ 0x53, 0x88, 0x87, 0x34, 0xA6, 0x4B, 0x49, 0x24, 0x53, 0xD6, ++ 0xF1, 0x1E, 0x4E, 0x98, 0x4D, 0x6B, 0x44, 0x31, 0x94, 0xFF, ++ 0x46, 0xC2, 0x38, 0x2E, 0xEA, 0xBB ++ }; ++ static unsigned char dhg_2048[] = { ++ 0x05 ++ }; ++ DH *dh = DH_new(); ++ BIGNUM *dhp_bn, *dhg_bn; ++ ++ if (dh == NULL) ++ return NULL; ++ dhp_bn = BN_bin2bn(dhp_2048, sizeof (dhp_2048), NULL); ++ dhg_bn = BN_bin2bn(dhg_2048, sizeof (dhg_2048), NULL); ++ if (dhp_bn == NULL || dhg_bn == NULL ++ || !DH_set0_pqg(dh, dhp_bn, NULL, dhg_bn)) { ++ DH_free(dh); ++ BN_free(dhp_bn); ++ BN_free(dhg_bn); ++ return NULL; ++ } ++ return dh; ++} +diff --git a/svc.c b/svc.c +index 1341397..758dfbd 100644 +--- a/svc.c ++++ b/svc.c +@@ -1512,6 +1512,39 @@ do_RSAgen(void) + return; + } + ++ ++#if OPENSSL_VERSION_NUMBER < 0x10100000 ++static inline int DH_set0_pqg(DH *dh, BIGNUM *p, BIGNUM *q, BIGNUM *g) ++{ ++ /* If the fields p and g in d are NULL, the corresponding input ++ * parameters MUST be non-NULL. q may remain NULL. ++ */ ++ if ((dh->p == NULL && p == NULL) ++ || (dh->g == NULL && g == NULL)) ++ return 0; ++ ++ if (p != NULL) { ++ BN_free(dh->p); ++ dh->p = p; ++ } ++ if (q != NULL) { ++ BN_free(dh->q); ++ dh->q = q; ++ } ++ if (g != NULL) { ++ BN_free(dh->g); ++ dh->g = g; ++ } ++ ++ if (q != NULL) { ++ dh->length = BN_num_bits(q); ++ } ++ ++ return 1; ++} ++#endif ++ ++ + #include "dh512.h" + + #if DH_LEN == 1024 diff --git a/bsp/buildroot/package/rpcbind/0005-rpcbproc_callit_com-Stop-freeing-a-static-pointer.patch b/bsp/buildroot/package/rpcbind/0005-rpcbproc_callit_com-Stop-freeing-a-static-pointer.patch new file mode 100644 index 00000000..c482af5d --- /dev/null +++ b/bsp/buildroot/package/rpcbind/0005-rpcbproc_callit_com-Stop-freeing-a-static-pointer.patch @@ -0,0 +1,98 @@ +From 4e201b75928ff7d4894cd30ab0f5f67b9cd95f5c Mon Sep 17 00:00:00 2001 +From: Steve Dickson (tag), w_space); + +- if (endofName > tagEnd) ++ if (!endofName || endofName > tagEnd) + endofName = const_cast (tagEnd); + + *endofName = '\0'; +@@ -214,7 +214,7 @@ ESICustomParser::parse(char const *dataToParse, size_t const lengthOfData, bool + + char * endofName = strpbrk(const_cast (tag), w_space); + +- if (endofName > tagEnd) ++ if (!endofName || endofName > tagEnd) + endofName = const_cast (tagEnd); + + *endofName = '\0'; +-- +2.11.0 + diff --git a/bsp/buildroot/package/squid/0004-Fix-indirect-IP-logging-for-transactions-without-a-c.patch b/bsp/buildroot/package/squid/0004-Fix-indirect-IP-logging-for-transactions-without-a-c.patch new file mode 100644 index 00000000..51fff300 --- /dev/null +++ b/bsp/buildroot/package/squid/0004-Fix-indirect-IP-logging-for-transactions-without-a-c.patch @@ -0,0 +1,31 @@ +From 8232b83d3fa47a1399f155cb829db829369fbae9 Mon Sep 17 00:00:00 2001 +From: squidadm