From 0291dfaa64fbccc76c6c35d09c6f62993f1228cc Mon Sep 17 00:00:00 2001 From: Pascal Vizeli Date: Sat, 11 Jan 2020 16:41:13 +0000 Subject: [PATCH] Update Buildroot 2019.02.8 --- ...e.patch => 0009-odroid-ux4-firmware.patch} | 12 +- ...tools-start-only-inside-a-vmware-env.patch | 32 - buildroot-patches/0010-Bump-bluez-5.52.patch | 51 + buildroot/CHANGES | 181 +++ buildroot/DEVELOPERS | 75 +- buildroot/Makefile | 6 +- buildroot/arch/Config.in.x86 | 13 +- buildroot/board/beaglebone/uEnv.txt | 5 +- buildroot/board/qemu/aarch64-virt/readme.txt | 2 +- buildroot/board/qemu/arm-versatile/readme.txt | 2 +- buildroot/board/qemu/arm-vexpress/readme.txt | 2 +- buildroot/board/qemu/m68k-q800/readme.txt | 2 +- .../board/qemu/mips32r2-malta/readme.txt | 2 +- .../board/qemu/mips32r2el-malta/readme.txt | 2 +- .../board/qemu/mips32r6-malta/readme.txt | 2 +- .../board/qemu/mips32r6el-malta/readme.txt | 2 +- buildroot/board/qemu/mips64-malta/readme.txt | 2 +- .../board/qemu/mips64el-malta/readme.txt | 2 +- .../board/qemu/mips64r6-malta/readme.txt | 2 +- .../board/qemu/mips64r6el-malta/readme.txt | 2 +- buildroot/board/qemu/ppc-g3beige/readme.txt | 2 +- buildroot/board/qemu/ppc64-e5500/readme.txt | 2 +- buildroot/board/qemu/ppc64-pseries/readme.txt | 2 +- .../board/qemu/ppc64le-pseries/readme.txt | 2 +- buildroot/board/qemu/riscv32-virt/readme.txt | 2 +- buildroot/board/qemu/riscv64-virt/readme.txt | 2 +- buildroot/board/qemu/sh4-r2d/readme.txt | 2 +- buildroot/board/qemu/sh4eb-r2d/readme.txt | 2 +- buildroot/board/qemu/sparc-ss10/readme.txt | 2 +- buildroot/board/qemu/sparc64-sun4u/readme.txt | 2 +- buildroot/board/qemu/x86/readme.txt | 2 +- buildroot/board/qemu/x86_64/readme.txt | 2 +- .../arm-trusted-firmware.mk | 6 +- buildroot/boot/barebox/barebox.mk | 4 + buildroot/configs/aarch64_efi_defconfig | 2 +- buildroot/configs/beaglebone_defconfig | 1 - .../docs/manual/adding-packages-cargo.txt | 2 +- .../docs/manual/adding-packages-python.txt | 10 +- buildroot/docs/manual/common-usage.txt | 4 +- buildroot/docs/manual/configure.txt | 54 +- buildroot/docs/manual/contribute.txt | 4 +- buildroot/docs/manual/manual.html | 205 ++-- buildroot/docs/manual/manual.pdf | Bin 539146 -> 540805 bytes buildroot/docs/manual/manual.text | 239 ++-- buildroot/docs/manual/quickstart.txt | 28 +- buildroot/docs/manual/rebuilding-packages.txt | 22 +- .../manual/using-buildroot-development.txt | 10 + buildroot/fs/common.mk | 2 +- buildroot/fs/tar/tar.mk | 3 + buildroot/linux/Config.in | 2 +- buildroot/linux/linux.hash | 8 +- buildroot/linux/linux.mk | 2 + buildroot/package/Config.in | 3 +- buildroot/package/Config.in.host | 1 + ...Makefile-unconditionally-disable-SSP.patch | 35 + ...Makefile-unconditionally-disable-PIE.patch | 33 + buildroot/package/apache/apache.hash | 4 +- buildroot/package/apache/apache.mk | 2 +- buildroot/package/asterisk/asterisk.hash | 4 +- buildroot/package/asterisk/asterisk.mk | 2 +- buildroot/package/atk/Config.in | 2 + buildroot/package/atk/atk.mk | 4 +- buildroot/package/augeas/augeas.mk | 3 - buildroot/package/autofs/autofs.mk | 11 +- buildroot/package/azmq/Config.in | 2 +- buildroot/package/batctl/batctl.mk | 2 +- buildroot/package/batman-adv/batman-adv.mk | 2 +- buildroot/package/bcg729/Config.in | 2 +- buildroot/package/berkeleydb/berkeleydb.mk | 17 + buildroot/package/bind/0001-cross.patch | 13 +- ...perations-in-bin-named-client.c-with.patch | 133 --- buildroot/package/bind/Config.in | 2 +- buildroot/package/bind/bind.hash | 6 +- buildroot/package/bind/bind.mk | 2 +- .../bluez5_utils-headers.mk | 2 +- .../package/bluez5_utils/bluez5_utils.hash | 2 +- .../package/bluez5_utils/bluez5_utils.mk | 2 +- buildroot/package/brotli/brotli.mk | 8 + buildroot/package/busybox/busybox.config | 4 +- buildroot/package/busybox/udhcpc.script | 2 +- buildroot/package/bwm-ng/bwm-ng.mk | 2 +- .../bzip2/0002-improve-build-system.patch | 14 +- buildroot/package/bzip2/Config.in | 2 + buildroot/package/bzip2/bzip2.hash | 6 +- buildroot/package/bzip2/bzip2.mk | 4 +- buildroot/package/ca-certificates/Config.in | 2 +- buildroot/package/chrony/chrony.mk | 7 +- buildroot/package/clamav/Config.in | 1 + buildroot/package/clamav/clamav.hash | 2 +- buildroot/package/clamav/clamav.mk | 4 +- buildroot/package/cloop/cloop.mk | 3 +- buildroot/package/collectd/collectd.hash | 2 +- buildroot/package/collectd/collectd.mk | 6 +- .../package/connman-gtk/connman-gtk.hash | 1 + buildroot/package/connman-gtk/connman-gtk.mk | 4 +- buildroot/package/connman/connman.mk | 1 + buildroot/package/copas/Config.in | 2 +- buildroot/package/cryptopp/cryptopp.mk | 11 +- ...lative-linking-with-absolute-linking.patch | 46 - ...old-ln-versions-without-the-r-option.patch | 214 ++++ ...otext.c-link-with-libiconv-if-needed.patch | 122 ++ .../package/cups-filters/cups-filters.mk | 21 +- buildroot/package/cups/cups.hash | 2 +- buildroot/package/cups/cups.mk | 2 +- .../package/dahdi-linux/dahdi-linux.hash | 4 +- buildroot/package/dahdi-linux/dahdi-linux.mk | 2 +- .../package/dahdi-tools/dahdi-tools.hash | 4 +- buildroot/package/dahdi-tools/dahdi-tools.mk | 2 +- buildroot/package/daq/daq.mk | 7 + buildroot/package/davfs2/davfs2.hash | 2 +- buildroot/package/davfs2/davfs2.mk | 2 +- buildroot/package/dbus/dbus.hash | 4 +- buildroot/package/dbus/dbus.mk | 2 +- buildroot/package/dehydrated/dehydrated.hash | 4 +- buildroot/package/dehydrated/dehydrated.mk | 2 +- buildroot/package/dialog/dialog.mk | 2 +- buildroot/package/dmraid/Config.in | 2 + buildroot/package/docker-cli/docker-cli.hash | 2 +- buildroot/package/docker-cli/docker-cli.mk | 4 +- .../package/docker-engine/docker-engine.hash | 2 +- .../package/docker-engine/docker-engine.mk | 4 +- .../package/docker-proxy/docker-proxy.hash | 3 +- .../package/docker-proxy/docker-proxy.mk | 2 +- ...dd-c-argument-to-build-precompiled-h.patch | 34 + buildroot/package/doom-wad/Config.in | 2 + .../dovecot-pigeonhole.hash | 2 +- .../dovecot-pigeonhole/dovecot-pigeonhole.mk | 2 +- buildroot/package/dovecot/dovecot.hash | 2 +- buildroot/package/dovecot/dovecot.mk | 11 +- ...uccessfull-login-of-disabled-user-78.patch | 35 + .../0004-Fix-build-with-latest-glibc.patch | 22 + buildroot/package/e2fsprogs/e2fsprogs.hash | 4 +- buildroot/package/e2fsprogs/e2fsprogs.mk | 5 +- ...t-fix-relocations-for-read-only-data.patch | 58 + buildroot/package/elf2flt/Config.in.host | 2 + ...source-leak-in-elf-32-64-_updatefile.patch | 32 + ...ix_memalign-instead-of-aligned_alloc.patch | 58 + buildroot/package/elfutils/elfutils.hash | 4 +- buildroot/package/elfutils/elfutils.mk | 2 +- buildroot/package/eudev/Config.in | 3 +- buildroot/package/eudev/Config.in.host | 3 + buildroot/package/eudev/eudev.mk | 38 + .../0001-Add-missing-limits.h-include.patch | 38 + buildroot/package/exfat-utils/exfat-utils.mk | 2 + buildroot/package/exfat/exfat.mk | 2 + buildroot/package/exim/0004-glibc.patch | 27 - ...-libnsl.patch => 0004-remove-libnsl.patch} | 0 ...ix-base64d-buffer-size-CVE-2018-6789.patch | 37 - .../package/exim/0005-Fix-uClibc-build.patch | 35 + ...ix-buffer-overflow-in-string_vformat.patch | 44 + .../exim/0007-Fix-CVE-2019-10149.patch | 51 - buildroot/package/exim/exim.hash | 3 +- buildroot/package/exim/exim.mk | 16 +- buildroot/package/expat/expat.hash | 8 +- buildroot/package/expat/expat.mk | 4 +- buildroot/package/expect/expect.hash | 4 +- buildroot/package/expect/expect.mk | 2 +- ...k-for-syntax-element-inconsistencies.patch | 64 + ...fadj-sanitize-frequency-band-borders.patch | 71 ++ .../0003-Fix-a-couple-buffer-overflows.patch | 50 + ...prevent-crash-on-SCE-followed-by-CPE.patch | 54 + ...-fix-asbolute-symlink-of-libfaifa.so.patch | 32 + buildroot/package/faifa/Config.in | 2 +- ...nicate-check-return-status-of-msgrcv.patch | 2 +- ...003-Select-TCP-when-lack-of-SYSV-IPC.patch | 77 ++ buildroot/package/fakeroot/fakeroot.mk | 8 +- buildroot/package/fastd/Config.in | 2 +- buildroot/package/ffmpeg/ffmpeg.hash | 2 +- buildroot/package/ffmpeg/ffmpeg.mk | 2 +- ...ation-overflow-when-computing-sector.patch | 68 ++ ...-of-elements-in-a-vector-found-by-os.patch | 62 + buildroot/package/file/file.hash | 4 +- buildroot/package/file/file.mk | 2 +- buildroot/package/flashbench/Config.in | 2 +- buildroot/package/fmt/Config.in | 2 + buildroot/package/freerdp/freerdp.mk | 4 +- .../package/freescale-imx/imx-uuc/imx-uuc.mk | 2 +- buildroot/package/freeswitch/freeswitch.hash | 14 +- buildroot/package/freeswitch/freeswitch.mk | 2 +- buildroot/package/fswebcam/Config.in | 2 +- buildroot/package/fwts/Config.in | 2 +- ...nsa-backport-fix-for-PR-target-90922.patch | 43 + .../1003-xtensa-fix-PR-target-91880.patch | 49 + ...nsa-backport-fix-for-PR-target-90922.patch | 43 + .../0002-xtensa-fix-PR-target-91880.patch | 49 + ...-check-return-value-in-gdImageBmpPtr.patch | 80 ++ ...l-infinite-loop-in-gdImageCreateFrom.patch | 61 + ...lized-read-in-gdImageCreateFromXbm-C.patch | 41 + ...Potential-double-free-in-gdImage-Ptr.patch | 219 ++++ ...m-taglib-config-when-cross-compiling.patch | 46 + ...-the-crazy-md5-file-copying-nonsense.patch | 252 ---- .../package/ghostscript/ghostscript.hash | 4 +- buildroot/package/ghostscript/ghostscript.mk | 2 +- ...13-Heap-Buffer-Overflow-2-in-functio.patch | 31 + ...19-MemorySanitizer-FPE-on-unknown-ad.patch | 28 + buildroot/package/giflib/giflib.hash | 2 + buildroot/package/git/git.mk | 8 + buildroot/package/glib-networking/Config.in | 2 + .../glib-networking/glib-networking.mk | 1 - .../glibc.hash | 2 +- buildroot/package/glibc/glibc.mk | 2 +- buildroot/package/gnupg2/gnupg2.hash | 8 +- buildroot/package/gnupg2/gnupg2.mk | 2 +- buildroot/package/gnuradio/Config.in | 4 + buildroot/package/gnutls/gnutls.mk | 8 +- .../package/go/0002-Fix-CVE-2019-16276.patch | 123 ++ .../package/go/0003-Fix-CVE-2019-17596.patch | 27 + buildroot/package/go/go.hash | 2 +- buildroot/package/go/go.mk | 2 +- buildroot/package/gob2/gob2.hash | 2 + buildroot/package/gob2/gob2.mk | 2 + buildroot/package/gqview/Config.in | 2 +- buildroot/package/gr-osmosdr/Config.in | 2 + .../gst1-rtsp-server/gst1-rtsp-server.mk | 3 + buildroot/package/gtkperf/Config.in | 2 + buildroot/package/gtkperf/gtkperf.hash | 1 + buildroot/package/gtkperf/gtkperf.mk | 3 +- buildroot/package/gupnp-tools/gupnp-tools.mk | 5 +- buildroot/package/gvfs/gvfs.mk | 9 +- buildroot/package/haproxy/haproxy.hash | 2 +- buildroot/package/haproxy/haproxy.mk | 2 +- buildroot/package/haveged/haveged.hash | 5 +- buildroot/package/haveged/haveged.mk | 4 +- .../package/hicolor-icon-theme/Config.in | 2 + buildroot/package/ifenslave/Config.in | 2 +- buildroot/package/ifplugd/ifplugd.mk | 2 +- .../package/imagemagick/imagemagick.hash | 2 +- buildroot/package/imagemagick/imagemagick.mk | 5 +- .../intel-microcode/intel-microcode.hash | 2 +- .../intel-microcode/intel-microcode.mk | 4 +- .../package/ipsec-tools/ipsec-tools.hash | 3 + buildroot/package/ipsec-tools/ipsec-tools.mk | 2 + ...x-userspace-kernel-headers-collision.patch | 45 - ...s-monitor-fix-build-with-older-glibc.patch | 77 -- ...build-with-kernel-headers-before-4.2.patch | 51 - ...les-monitor-fix-build-with-musl-libc.patch | 44 - ...he-headers-conflict-workaround-to-in.patch | 37 - buildroot/package/iptables/iptables.hash | 2 +- buildroot/package/iptables/iptables.mk | 2 +- buildroot/package/irssi/irssi.hash | 2 +- buildroot/package/irssi/irssi.mk | 2 +- buildroot/package/iw/Config.in | 2 +- ...001-verify-data-range-CVE-2018-19541.patch | 35 + ...ck-null-in-jp2_decode-CVE-2018-19542.patch | 24 + .../0003-test-asclen-CVE-2018-19540.patch | 29 + buildroot/package/jasper/jasper.hash | 2 +- buildroot/package/jasper/jasper.mk | 4 +- buildroot/package/joe/joe.mk | 2 +- ...-Fix-int-overflow-segfault-w-big-BMP.patch | 51 - ...on-t-allow-quantization-w-non-RGB-CS.patch | 39 - buildroot/package/jpeg-turbo/jpeg-turbo.hash | 10 +- buildroot/package/jpeg-turbo/jpeg-turbo.mk | 2 +- buildroot/package/json-glib/json-glib.mk | 4 + buildroot/package/kexec-lite/Config.in | 2 + buildroot/package/kf5/Config.in | 2 + .../kf5-extra-cmake-modules.mk | 2 +- .../kf5-modemmanager-qt.mk | 2 +- .../kf5-networkmanager-qt.mk | 2 +- .../kodi-jsonschemabuilder.mk | 1 + .../kodi-texturepacker/kodi-texturepacker.mk | 1 + buildroot/package/kodi/Config.in | 2 - buildroot/package/kodi/kodi.hash | 2 + buildroot/package/kodi/kodi.mk | 2 +- .../package/kvm-unit-tests/kvm-unit-tests.mk | 13 +- buildroot/package/leafnode2/Config.in | 4 +- buildroot/package/lftp/lftp.mk | 3 + .../0007-RAR-reader-fix-use-after-free.patch | 36 + buildroot/package/libass/Config.in | 2 +- ...0001-flopen-fix-build-with-musl-libc.patch | 40 - buildroot/package/libbsd/Config.in | 2 - buildroot/package/libbsd/libbsd.hash | 6 +- buildroot/package/libbsd/libbsd.mk | 4 +- buildroot/package/libbson/Config.in | 2 + .../0001-libcdaudio-enable-autoreconf.patch | 43 + buildroot/package/libcdaudio/libcdaudio.mk | 3 + buildroot/package/libcurl/libcurl.hash | 4 +- buildroot/package/libcurl/libcurl.mk | 2 +- buildroot/package/libdnet/libdnet.mk | 1 + buildroot/package/libdvdnav/Config.in | 2 +- buildroot/package/libdvdread/Config.in | 2 +- buildroot/package/liberation/Config.in | 2 + buildroot/package/libftdi/libftdi.hash | 5 + buildroot/package/libftdi/libftdi.mk | 4 + buildroot/package/libftdi1/libftdi1.mk | 8 +- ...ult-to-underscore-yes-for-cross-buil.patch | 48 + .../package/libgcrypt/0001-reconfigure.patch | 27 - ...re.ac-add-an-option-to-disable-tests.patch | 66 ++ buildroot/package/libgcrypt/libgcrypt.hash | 8 +- buildroot/package/libgcrypt/libgcrypt.mk | 8 +- buildroot/package/libgit2/libgit2.hash | 2 +- buildroot/package/libgit2/libgit2.mk | 4 +- ...e-Limit-access-to-files-when-copying.patch | 56 + buildroot/package/libglob/Config.in | 2 + .../libgpg-error/0001-gawk5-support.patch | 162 +++ .../package/libgpg-error/libgpg-error.mk | 2 + buildroot/package/libgtk2/libgtk2.mk | 5 +- buildroot/package/libgtk3/libgtk3.mk | 6 +- buildroot/package/libhid/Config.in | 2 +- buildroot/package/libiscsi/Config.in | 2 +- buildroot/package/liblockfile/Config.in | 2 + buildroot/package/libmodplug/libmodplug.hash | 2 +- buildroot/package/libmodplug/libmodplug.mk | 2 +- buildroot/package/libmspack/Config.in | 7 + buildroot/package/libmspack/libmspack.hash | 3 + buildroot/package/libmspack/libmspack.mk | 13 + ...d-Libs.private-field-to-libnftnl.pc.patch} | 0 ...libnftnl_xfree-to-avoid-symbol-namin.patch | 1032 ----------------- buildroot/package/libnftnl/libnftnl.hash | 2 +- buildroot/package/libnftnl/libnftnl.mk | 2 +- buildroot/package/libnspr/0001-nios2.patch | 30 +- .../package/libnspr/0002-microblaze.patch | 32 +- buildroot/package/libnspr/0003-nds32.patch | 73 ++ buildroot/package/libnspr/libnspr.hash | 2 +- buildroot/package/libnspr/libnspr.mk | 2 +- ...ix-build-if-arm-doesn-t-support-NEON.patch | 50 + buildroot/package/libnss/libnss.hash | 4 +- buildroot/package/libnss/libnss.mk | 18 +- buildroot/package/libopenssl/libopenssl.hash | 4 +- buildroot/package/libopenssl/libopenssl.mk | 10 +- ...dd-missing-limits.h-for-musl-systems.patch | 26 - buildroot/package/libpcap/libpcap.hash | 2 +- buildroot/package/libpcap/libpcap.mk | 2 +- ...001-pciaccess.pc.in-add-Libs.Private.patch | 28 + buildroot/package/libpciaccess/Config.in | 4 + buildroot/package/libpri/libpri.mk | 3 +- buildroot/package/librsvg/librsvg.mk | 4 +- ...n-uClibc-ng-syscall-on-x86_64-system.patch | 80 ++ buildroot/package/libseccomp/libseccomp.hash | 2 +- buildroot/package/libseccomp/libseccomp.mk | 4 +- buildroot/package/libsecret/Config.in | 2 +- buildroot/package/libsecret/libsecret.mk | 3 +- buildroot/package/libsexy/Config.in | 2 +- buildroot/package/libshout/libshout.mk | 2 +- buildroot/package/libsigrok/libsigrok.hash | 1 + buildroot/package/libsigrok/libsigrok.mk | 18 +- buildroot/package/libss7/libss7.mk | 3 +- .../0001-drop-custom-buildconf-script.patch | 28 +- buildroot/package/libssh2/libssh2.hash | 2 +- buildroot/package/libssh2/libssh2.mk | 4 +- buildroot/package/libstrophe/libstrophe.hash | 2 +- buildroot/package/libstrophe/libstrophe.mk | 2 +- buildroot/package/libsvgtiny/libsvgtiny.hash | 1 + buildroot/package/libsvgtiny/libsvgtiny.mk | 2 + ...01-libtorrent.pc.in-add-Libs.Private.patch | 30 + buildroot/package/libunwind/libunwind.mk | 4 +- buildroot/package/libvips/libvips.mk | 3 +- buildroot/package/libvncserver/Config.in | 2 +- buildroot/package/libvorbis/Config.in | 2 + buildroot/package/linux-fusion/Config.in | 2 + .../package/linux-headers/Config.in.host | 8 +- .../package/linux-headers/linux-headers.mk | 4 +- buildroot/package/linux-tools/Config.in | 5 +- ...-scripts-build-use-bin-bash-as-shell.patch | 28 + ...e-add-lmbench-to-list-of-executables.patch | 29 + buildroot/package/lmbench/lmbench.mk | 3 +- buildroot/package/logrotate/logrotate.hash | 1 + buildroot/package/lua-sdl2/lua-sdl2.mk | 10 +- buildroot/package/luasql-sqlite3/Config.in | 2 +- buildroot/package/luksmeta/luksmeta.hash | 2 +- buildroot/package/luksmeta/luksmeta.mk | 3 +- buildroot/package/lvm2/lvm2.mk | 7 +- ...-rename-internal-memfd_create-to-mem.patch | 43 + buildroot/package/lzma/lzma.hash | 3 + buildroot/package/lzma/lzma.mk | 2 + .../0001-add-extra-check-for-librt.patch | 2 + ...002-fix-build-error-with-newer-cmake.patch | 44 + buildroot/package/mariadb/mariadb.hash | 14 +- buildroot/package/mariadb/mariadb.mk | 11 +- buildroot/package/matchbox-common/Config.in | 2 + buildroot/package/matchbox-desktop/Config.in | 2 + buildroot/package/matchbox-fakekey/Config.in | 2 + buildroot/package/matchbox-keyboard/Config.in | 2 + buildroot/package/matchbox-lib/Config.in | 2 + buildroot/package/matchbox-panel/Config.in | 2 + .../matchbox-startup-monitor/Config.in | 2 + buildroot/package/mbedtls/mbedtls.hash | 6 +- buildroot/package/mbedtls/mbedtls.mk | 2 +- buildroot/package/mdadm/Config.in | 2 +- buildroot/package/mediastreamer/Config.in | 2 +- buildroot/package/mesa3d/Config.in | 2 +- buildroot/package/meson/meson.mk | 6 +- buildroot/package/metacity/Config.in | 2 + buildroot/package/metacity/metacity.mk | 5 +- buildroot/package/mii-diag/Config.in | 2 + buildroot/package/minicom/minicom.mk | 4 + buildroot/package/minizip/Config.in | 1 + ...uses-problems-on-some-x86_64-systems.patch | 73 ++ buildroot/package/mjpegtools/mjpegtools.mk | 2 + buildroot/package/mongodb/mongodb.hash | 2 +- buildroot/package/mongodb/mongodb.mk | 2 +- buildroot/package/mongoose/mongoose.hash | 2 +- buildroot/package/mongoose/mongoose.mk | 2 +- buildroot/package/monit/monit.hash | 4 +- buildroot/package/monit/monit.mk | 2 +- buildroot/package/mosquitto/Config.in | 2 +- buildroot/package/mosquitto/mosquitto.hash | 2 +- buildroot/package/mosquitto/mosquitto.mk | 2 +- buildroot/package/mp4v2/Config.in | 2 +- buildroot/package/mpd/Config.in | 2 +- buildroot/package/mpg123/mpg123.hash | 8 +- buildroot/package/mpg123/mpg123.mk | 2 +- ...balance-in-corner-cases-of-i386-math.patch | 200 ++++ ...ression-in-i386-asm-for-atan2-atan2f.patch | 37 + buildroot/package/musl/Config.in | 2 + buildroot/package/mxsldr/Config.in.host | 2 +- buildroot/package/mysql/Config.in | 2 - buildroot/package/ncurses/ncurses.hash | 2 + buildroot/package/ncurses/ncurses.mk | 2 +- buildroot/package/neardal/Config.in | 2 +- buildroot/package/neardal/neardal.mk | 12 +- buildroot/package/netperf/Config.in | 2 +- buildroot/package/nfs-utils/Config.in | 2 +- buildroot/package/nfs-utils/nfs-utils.mk | 12 +- buildroot/package/nghttp2/nghttp2.hash | 2 +- buildroot/package/nghttp2/nghttp2.mk | 2 +- ...ake-sys_nerr-guessing-cross-friendly.patch | 4 +- buildroot/package/nginx/nginx.hash | 4 +- buildroot/package/nginx/nginx.mk | 2 +- buildroot/package/nodejs/Config.in | 1 + buildroot/package/nodejs/nodejs.hash | 4 +- buildroot/package/nodejs/nodejs.mk | 25 +- buildroot/package/numactl/Config.in | 2 +- buildroot/package/openblas/Config.in | 4 +- buildroot/package/opencv3/Config.in | 4 + buildroot/package/opencv3/opencv3.mk | 7 +- ...fix-libtool-static-behavior-to-match.patch | 56 + buildroot/package/openldap/openldap.hash | 10 +- buildroot/package/openldap/openldap.mk | 2 +- buildroot/package/opentyrian-data/Config.in | 2 +- ..._poll-h-to-fix-build-failure-on-musl.patch | 798 +++++++++++++ ...ns-about-glibc-being-only-libc-imple.patch | 27 + ...e-configure-test-for-struct-timespec.patch | 48 + ...finition-of-ALLPERMS-and-ACCESSPERMS.patch | 61 + ...-test-for-feature-instead-of-platfor.patch | 150 +++ ...onfigure-test-for-sys-stat.h-include.patch | 28 + .../0009-Set-permissions-on-rules-file.patch | 23 + .../0010-Change-DEVPATH-to-devpath.patch | 25 + buildroot/package/openvmtools/Config.in | 6 +- buildroot/package/openvmtools/S10vmtoolsd | 2 + buildroot/package/openvmtools/openvmtools.mk | 4 + .../package/openvmtools/vmtoolsd.service | 4 +- buildroot/package/opkg/Config.in | 2 +- buildroot/package/oprofile/Config.in | 2 + .../package/oracle-mysql/oracle-mysql.mk | 4 +- buildroot/package/ortp/Config.in | 2 +- buildroot/package/pcmanfm/pcmanfm.mk | 3 +- .../package/perl-gdgraph/perl-gdgraph.hash | 3 +- .../package/perl-gdgraph/perl-gdgraph.mk | 4 +- .../perl-gdtextutil/perl-gdtextutil.hash | 3 +- .../perl-gdtextutil/perl-gdtextutil.mk | 3 +- buildroot/package/php/php.hash | 2 +- buildroot/package/php/php.mk | 2 +- buildroot/package/pigpio/pigpio.mk | 10 + buildroot/package/pkg-generic.mk | 11 +- buildroot/package/pkg-kconfig.mk | 2 +- buildroot/package/postgresql/Config.in | 2 +- buildroot/package/postgresql/postgresql.hash | 8 +- buildroot/package/postgresql/postgresql.mk | 4 +- ...move-predefined-O2-optimization-flag.patch | 21 + buildroot/package/prboom/prboom.mk | 9 + .../proftpd/0002-fix-CVE-2019-12815.patch | 382 ++++++ buildroot/package/proftpd/proftpd.hash | 1 + buildroot/package/proj/proj.mk | 8 + buildroot/package/prosody/prosody.hash | 8 +- buildroot/package/prosody/prosody.mk | 2 +- buildroot/package/protobuf/protobuf.mk | 8 + buildroot/package/psplash/psplash.hash | 1 + buildroot/package/psplash/psplash.mk | 1 + .../0001-Fix-compilation-with-NO_GSSAPI.patch | 266 ----- .../0002-unix-uxpoll-need-_XOPEN_SOURCE.patch | 39 - .../putty/0003-Fix-uClibc-build-issues.patch | 93 -- buildroot/package/putty/putty.hash | 7 +- buildroot/package/putty/putty.mk | 4 +- .../package/python-django/python-django.hash | 4 +- .../package/python-django/python-django.mk | 4 +- buildroot/package/python-idna/Config.in | 2 + .../package/python-numpy/python-numpy.mk | 2 - .../python-pysnmp-apps/python-pysnmp-apps.mk | 2 +- .../python-urllib3/python-urllib3.hash | 4 +- .../package/python-urllib3/python-urllib3.mk | 4 +- ...get_python_inc-for-cross-compilation.patch | 20 +- buildroot/package/python/python.hash | 6 +- buildroot/package/python/python.mk | 6 +- ...e-the-build-of-pyc-files-conditional.patch | 4 +- ...re-to-disable-the-build-of-certain-e.patch | 6 +- ...ook-in-usr-lib-termcap-for-libraries.patch | 2 +- .../0006-Don-t-add-multiarch-paths.patch | 2 +- .../0007-Abort-on-failed-module-build.patch | 2 +- ...ig.sh.in-ensure-sed-invocations-only.patch | 2 +- ...locale-and-set-to-default-when-addin.patch | 2 +- ...-disable-installation-of-test-module.patch | 4 +- .../0014-Add-an-option-to-disable-pydoc.patch | 10 +- ...015-Add-an-option-to-disable-lib2to3.patch | 12 +- ...option-to-disable-the-sqlite3-module.patch | 6 +- ...d-an-option-to-disable-the-tk-module.patch | 6 +- ...-option-to-disable-the-curses-module.patch | 4 +- .../0019-Add-an-option-to-disable-expat.patch | 6 +- .../0023-Add-an-option-to-disable-IDLE.patch | 8 +- ...024-Add-an-option-to-disable-decimal.patch | 2 +- ...thon-config.sh-don-t-reassign-prefix.patch | 2 +- ...-Fix-cross-compiling-the-uuid-module.patch | 2 +- ...up-CC-print-multiarch-output-for-mus.patch | 48 + buildroot/package/python3/python3.hash | 6 +- buildroot/package/python3/python3.mk | 14 +- .../0002-configure-improve-usbfs-check.patch | 60 - ...age-of-mcontext-structure-on-ARM-uCl.patch | 0 ...ly-sized-SIOCGSTAMP-with-new-kernels.patch | 337 ++++++ ...fix-crash-when-compiling-with-uClibc.patch | 43 + ...ser-assume-__NR_gettid-always-exists.patch | 44 + ...e-gettid-to-sys_gettid-to-avoid-clas.patch | 91 ++ buildroot/package/qemu/qemu.hash | 2 +- buildroot/package/qemu/qemu.mk | 7 +- buildroot/package/qt5/qt5.mk | 2 +- .../0006-Fix-compile-issue-with-gcc-9.patch | 32 + .../0004-fix-icu-build-for-qt5webkit.patch | 74 ++ buildroot/package/qt5/qt5base/qmake.conf.in | 5 +- buildroot/package/qt5/qt5base/qt5base.mk | 7 + buildroot/package/qt5/qt5enginio/Config.in | 15 +- buildroot/package/quagga/quagga.mk | 15 + buildroot/package/rabbitmq-c/rabbitmq-c.hash | 2 +- buildroot/package/rabbitmq-c/rabbitmq-c.mk | 4 +- buildroot/package/rauc/Config.in | 2 + buildroot/package/redis/redis.hash | 2 +- buildroot/package/redis/redis.mk | 2 +- buildroot/package/rpcbind/rpcbind.mk | 1 + buildroot/package/ruby/ruby.hash | 4 +- buildroot/package/ruby/ruby.mk | 6 +- buildroot/package/rygel/rygel.mk | 4 +- .../0003-Define-_GNU_SOURCE-when-needed.patch | 115 ++ ...ion-of-Samba-4.7.4-with-disabled-ADS.patch | 41 - ...on-64bit-platforms-by-including-std.patch} | 0 ...o.c-include-stdint.h-before-cmoka.h.patch} | 0 ...-build-of-manpages-and-documentation.patch | 123 -- buildroot/package/samba4/samba4.hash | 4 +- buildroot/package/samba4/samba4.mk | 5 +- buildroot/package/sdl_mixer/sdl_mixer.mk | 3 + buildroot/package/socat/socat.mk | 8 +- buildroot/package/sox/sox.mk | 12 +- .../spice-protocol/spice-protocol.hash | 5 +- .../package/spice-protocol/spice-protocol.mk | 2 +- .../0001-configure.ac-add-enable-tests.patch | 54 + buildroot/package/spice/spice.hash | 3 +- buildroot/package/spice/spice.mk | 7 +- ...ude-os-deps.m4-fix-cross-compilation.patch | 42 + ...re.ac-use-pkg-config-to-find-libxml2.patch | 79 -- buildroot/package/squid/squid.hash | 8 +- buildroot/package/squid/squid.mk | 6 +- buildroot/package/subversion/subversion.hash | 2 +- buildroot/package/subversion/subversion.mk | 2 +- buildroot/package/sudo/sudo.hash | 4 +- buildroot/package/sudo/sudo.mk | 2 +- buildroot/package/swupdate/Config.in | 2 +- .../systemd-bootchart/systemd-bootchart.mk | 6 + buildroot/package/systemd/Config.in | 1 + ...-config-file-for-cross-compiling-906.patch | 66 ++ buildroot/package/tcpdump/tcpdump.hash | 6 +- buildroot/package/tcpdump/tcpdump.mk | 2 +- ...001-configure-ac-fix-without-libdnet.patch | 76 ++ buildroot/package/tcpreplay/tcpreplay.hash | 4 +- buildroot/package/tcpreplay/tcpreplay.mk | 13 +- buildroot/package/tftpd/tftpd.hash | 3 + buildroot/package/tftpd/tftpd.mk | 2 + buildroot/package/thttpd/S90thttpd | 54 + buildroot/package/thttpd/thttpd.mk | 15 +- ...leak-that-was-assigned-CVE-2019-6128.patch | 53 - buildroot/package/tiff/tiff.hash | 2 +- buildroot/package/tiff/tiff.mk | 2 +- ...pie-linking-according-to-disable-pie.patch | 34 + buildroot/package/tvheadend/tvheadend.mk | 4 + buildroot/package/tz/tz.mk | 17 +- buildroot/package/tzdata/tzdata.mk | 19 +- .../0004-sparc-remove-asm-constraint.patch | 40 + ...rPC-sync-with-termios-fix-from-glibc.patch | 172 +++ buildroot/package/unscd/unscd.hash | 2 +- buildroot/package/unscd/unscd.mk | 2 +- buildroot/package/unzip/unzip.hash | 4 + buildroot/package/unzip/unzip.mk | 30 +- buildroot/package/util-linux/util-linux.mk | 6 +- buildroot/package/vlc/vlc.hash | 12 +- buildroot/package/vlc/vlc.mk | 2 +- buildroot/package/vte/vte.mk | 2 +- buildroot/package/vtun/vtun.mk | 6 +- ...uild-failure-after-r243644-in-GTK-Li.patch | 36 - buildroot/package/webkitgtk/webkitgtk.hash | 8 +- buildroot/package/webkitgtk/webkitgtk.mk | 6 +- ...fix-compilation-with-FreeRDP-2.0-rc4.patch | 218 ++++ .../wireless-regdb/wireless-regdb.hash | 2 +- .../package/wireless-regdb/wireless-regdb.mk | 2 +- buildroot/package/wireshark/wireshark.hash | 4 +- buildroot/package/wireshark/wireshark.mk | 2 +- buildroot/package/x11r7/libxcb/libxcb.hash | 9 +- buildroot/package/x11r7/libxcb/libxcb.mk | 2 +- .../xfont_font-util/xfont_font-util.hash | 11 +- .../x11r7/xfont_font-util/xfont_font-util.mk | 2 +- .../x11r7/xlib_libICE/xlib_libICE.hash | 9 +- .../package/x11r7/xlib_libICE/xlib_libICE.mk | 4 +- .../x11r7/xlib_libXfont/xlib_libXfont.hash | 3 + .../x11r7/xlib_libXfont/xlib_libXfont.mk | 8 + .../x11r7/xlib_libXfont2/xlib_libXfont2.mk | 8 + .../0001-modesettings-needs-dri2.patch | 0 ...ure.ac-Fix-check-for-CLOCK_MONOTONIC.patch | 0 ...003-Remove-check-for-useSIGIO-option.patch | 0 ...0004-include-misc.h-fix-uClibc-build.patch | 0 ...nd-Makefile.am-fix-build-without-glx.patch | 0 .../x11r7/xserver_xorg-server/Config.in | 4 +- .../xserver_xorg-server.hash | 10 +- buildroot/package/xen/xen.hash | 2 +- buildroot/package/xen/xen.mk | 2 +- ...6-Fix-build-break-with-newer-GCC-7-x.patch | 34 + buildroot/package/yad/yad.mk | 3 +- buildroot/package/yaffs2utils/yaffs2utils.mk | 2 +- buildroot/package/zeromq/zeromq.hash | 6 +- buildroot/package/zeromq/zeromq.mk | 2 +- buildroot/package/znc/znc.hash | 2 +- buildroot/package/znc/znc.mk | 2 +- .../support/dependencies/dependencies.sh | 4 + buildroot/support/download/git | 2 +- buildroot/support/misc/Buildroot.cmake | 1 + .../support/scripts/check-kernel-headers.sh | 7 +- buildroot/support/testing/infra/emulator.py | 9 +- .../support/testing/tests/package/test_lua.py | 2 +- .../testing/tests/package/test_perl.py | 2 +- buildroot/system/Config.in | 2 + buildroot/toolchain/Config.in | 6 + buildroot/toolchain/helpers.mk | 7 +- .../toolchain/toolchain-buildroot/Config.in | 2 + .../pkg-toolchain-external.mk | 5 + buildroot/utils/check-package | 7 +- buildroot/utils/genrandconfig | 10 +- buildroot/utils/test-pkg | 25 +- 630 files changed, 8470 insertions(+), 3892 deletions(-) rename buildroot-patches/{0010-odroid-ux4-firmware.patch => 0009-odroid-ux4-firmware.patch} (65%) delete mode 100644 buildroot-patches/0009-openvmtools-start-only-inside-a-vmware-env.patch create mode 100644 buildroot-patches/0010-Bump-bluez-5.52.patch create mode 100644 buildroot/package/am33x-cm3/0002-Makefile-unconditionally-disable-SSP.patch create mode 100644 buildroot/package/am33x-cm3/0003-Makefile-unconditionally-disable-PIE.patch delete mode 100644 buildroot/package/bind/0002-Replace-atomic-operations-in-bin-named-client.c-with.patch delete mode 100644 buildroot/package/cups-filters/0001-Replace-relative-linking-with-absolute-linking.patch create mode 100644 buildroot/package/cups-filters/0001-install-support-old-ln-versions-without-the-r-option.patch create mode 100644 buildroot/package/cups-filters/0002-filter-texttotext.c-link-with-libiconv-if-needed.patch create mode 100644 buildroot/package/domoticz/0003-CMakeLists.txt-add-c-argument-to-build-precompiled-h.patch create mode 100644 buildroot/package/dropbear/0003-Fix-for-issue-successfull-login-of-disabled-user-78.patch create mode 100644 buildroot/package/duma/0004-Fix-build-with-latest-glibc.patch create mode 100644 buildroot/package/elf2flt/0002-elf2flt-fix-relocations-for-read-only-data.patch create mode 100644 buildroot/package/elfutils/0004-libelf-Fix-possible-resource-leak-in-elf-32-64-_updatefile.patch create mode 100644 buildroot/package/elfutils/0005-libelf-Use-posix_memalign-instead-of-aligned_alloc.patch create mode 100644 buildroot/package/eudev/Config.in.host create mode 100644 buildroot/package/evtest/0001-Add-missing-limits.h-include.patch delete mode 100644 buildroot/package/exim/0004-glibc.patch rename buildroot/package/exim/{0006-remove-libnsl.patch => 0004-remove-libnsl.patch} (100%) delete mode 100644 buildroot/package/exim/0005-Fix-base64d-buffer-size-CVE-2018-6789.patch create mode 100644 buildroot/package/exim/0005-Fix-uClibc-build.patch create mode 100644 buildroot/package/exim/0006-Fix-buffer-overflow-in-string_vformat.patch delete mode 100644 buildroot/package/exim/0007-Fix-CVE-2019-10149.patch create mode 100644 buildroot/package/faad2/0001-syntax.c-check-for-syntax-element-inconsistencies.patch create mode 100644 buildroot/package/faad2/0002-sbr_hfadj-sanitize-frequency-band-borders.patch create mode 100644 buildroot/package/faad2/0003-Fix-a-couple-buffer-overflows.patch create mode 100644 buildroot/package/faad2/0004-add-patch-to-prevent-crash-on-SCE-followed-by-CPE.patch create mode 100644 buildroot/package/faifa/0003-Makefile.in-fix-asbolute-symlink-of-libfaifa.so.patch create mode 100644 buildroot/package/fakeroot/0003-Select-TCP-when-lack-of-SYSV-IPC.patch create mode 100644 buildroot/package/file/0001-Detect-multiplication-overflow-when-computing-sector.patch create mode 100644 buildroot/package/file/0002-Limit-the-number-of-elements-in-a-vector-found-by-os.patch create mode 100644 buildroot/package/gcc/7.4.0/1002-xtensa-backport-fix-for-PR-target-90922.patch create mode 100644 buildroot/package/gcc/7.4.0/1003-xtensa-fix-PR-target-91880.patch create mode 100644 buildroot/package/gcc/8.3.0/0001-xtensa-backport-fix-for-PR-target-90922.patch create mode 100644 buildroot/package/gcc/8.3.0/0002-xtensa-fix-PR-target-91880.patch create mode 100644 buildroot/package/gd/0001-bmp-check-return-value-in-gdImageBmpPtr.patch create mode 100644 buildroot/package/gd/0002-Fix-420-Potential-infinite-loop-in-gdImageCreateFrom.patch create mode 100644 buildroot/package/gd/0003-Fix-501-Uninitialized-read-in-gdImageCreateFromXbm-C.patch create mode 100644 buildroot/package/gd/0004-Fix-492-Potential-double-free-in-gdImage-Ptr.patch create mode 100644 buildroot/package/gerbera/0002-Fix-find_program-taglib-config-when-cross-compiling.patch delete mode 100644 buildroot/package/ghostscript/0002-Bug-700986-Remove-the-crazy-md5-file-copying-nonsense.patch create mode 100644 buildroot/package/giflib/0001-Address-SF-bug-113-Heap-Buffer-Overflow-2-in-functio.patch create mode 100644 buildroot/package/giflib/0002-Address-SF-bug-119-MemorySanitizer-FPE-on-unknown-ad.patch rename buildroot/package/glibc/{glibc-2.28-94-g4aeff335ca19286ee2382d8eba794ae5fd49281a => glibc-2.28-110-g57922433fa038faa6e37798b9655f85a94978d89}/glibc.hash (69%) create mode 100644 buildroot/package/go/0002-Fix-CVE-2019-16276.patch create mode 100644 buildroot/package/go/0003-Fix-CVE-2019-17596.patch delete mode 100644 buildroot/package/iptables/0001-ebtables-vlan-fix-userspace-kernel-headers-collision.patch delete mode 100644 buildroot/package/iptables/0002-xtables-monitor-fix-build-with-older-glibc.patch delete mode 100644 buildroot/package/iptables/0003-include-fix-build-with-kernel-headers-before-4.2.patch delete mode 100644 buildroot/package/iptables/0004-xtables-monitor-fix-build-with-musl-libc.patch delete mode 100644 buildroot/package/iptables/0005-include-extend-the-headers-conflict-workaround-to-in.patch create mode 100644 buildroot/package/jasper/0001-verify-data-range-CVE-2018-19541.patch create mode 100644 buildroot/package/jasper/0002-check-null-in-jp2_decode-CVE-2018-19542.patch create mode 100644 buildroot/package/jasper/0003-test-asclen-CVE-2018-19540.patch delete mode 100644 buildroot/package/jpeg-turbo/0001-tjLoadImage-Fix-int-overflow-segfault-w-big-BMP.patch delete mode 100644 buildroot/package/jpeg-turbo/0002-wrbmp.c-Don-t-allow-quantization-w-non-RGB-CS.patch create mode 100644 buildroot/package/libarchive/0007-RAR-reader-fix-use-after-free.patch delete mode 100644 buildroot/package/libbsd/0001-flopen-fix-build-with-musl-libc.patch create mode 100644 buildroot/package/libcdaudio/0001-libcdaudio-enable-autoreconf.patch create mode 100644 buildroot/package/libgcrypt/0001-build-Don-t-default-to-underscore-yes-for-cross-buil.patch delete mode 100644 buildroot/package/libgcrypt/0001-reconfigure.patch create mode 100644 buildroot/package/libgcrypt/0002-configure.ac-add-an-option-to-disable-tests.patch create mode 100644 buildroot/package/libglib2/0005-gfile-Limit-access-to-files-when-copying.patch create mode 100644 buildroot/package/libgpg-error/0001-gawk5-support.patch create mode 100644 buildroot/package/libmspack/Config.in create mode 100644 buildroot/package/libmspack/libmspack.hash create mode 100644 buildroot/package/libmspack/libmspack.mk rename buildroot/package/libnftnl/{0002-Add-Libs.private-field-to-libnftnl.pc.patch => 0001-Add-Libs.private-field-to-libnftnl.pc.patch} (100%) delete mode 100644 buildroot/package/libnftnl/0001-Rename-xfree-to-libnftnl_xfree-to-avoid-symbol-namin.patch create mode 100644 buildroot/package/libnspr/0003-nds32.patch create mode 100644 buildroot/package/libnss/0003-Bug-1590676-Fix-build-if-arm-doesn-t-support-NEON.patch delete mode 100644 buildroot/package/libpcap/0001-pcap-usb-linux.c-add-missing-limits.h-for-musl-systems.patch create mode 100644 buildroot/package/libpciaccess/0001-pciaccess.pc.in-add-Libs.Private.patch create mode 100644 buildroot/package/libseccomp/0002-Circumvent-bug-in-uClibc-ng-syscall-on-x86_64-system.patch create mode 100644 buildroot/package/libtorrent/0001-libtorrent.pc.in-add-Libs.Private.patch create mode 100644 buildroot/package/lmbench/0001-scripts-build-use-bin-bash-as-shell.patch create mode 100644 buildroot/package/lmbench/0002-src-Makefile-add-lmbench-to-list-of-executables.patch create mode 100644 buildroot/package/lxc/0001-syscall_wrappers-rename-internal-memfd_create-to-mem.patch create mode 100644 buildroot/package/mariadb/0002-fix-build-error-with-newer-cmake.patch create mode 100644 buildroot/package/mjpegtools/0001-PROGRAM_NOPIC-apparently-causes-problems-on-some-x86_64-systems.patch create mode 100644 buildroot/package/musl/0004-fix-x87-stack-imbalance-in-corner-cases-of-i386-math.patch create mode 100644 buildroot/package/musl/0005-fix-build-regression-in-i386-asm-for-atan2-atan2f.patch create mode 100644 buildroot/package/openldap/0004-revert-ITS-3977-fix-libtool-static-behavior-to-match.patch create mode 100644 buildroot/package/openvmtools/0003-Rename-poll-h-into-vm_poll-h-to-fix-build-failure-on-musl.patch create mode 100644 buildroot/package/openvmtools/0004-Remove-assumptions-about-glibc-being-only-libc-imple.patch create mode 100644 buildroot/package/openvmtools/0005-Use-configure-test-for-struct-timespec.patch create mode 100644 buildroot/package/openvmtools/0006-Fix-definition-of-ALLPERMS-and-ACCESSPERMS.patch create mode 100644 buildroot/package/openvmtools/0007-Use-configure-to-test-for-feature-instead-of-platfor.patch create mode 100644 buildroot/package/openvmtools/0008-Use-configure-test-for-sys-stat.h-include.patch create mode 100644 buildroot/package/openvmtools/0009-Set-permissions-on-rules-file.patch create mode 100644 buildroot/package/openvmtools/0010-Change-DEVPATH-to-devpath.patch create mode 100644 buildroot/package/prboom/0002-configure-remove-predefined-O2-optimization-flag.patch create mode 100644 buildroot/package/proftpd/0002-fix-CVE-2019-12815.patch delete mode 100644 buildroot/package/putty/0001-Fix-compilation-with-NO_GSSAPI.patch delete mode 100644 buildroot/package/putty/0002-unix-uxpoll-need-_XOPEN_SOURCE.patch delete mode 100644 buildroot/package/putty/0003-Fix-uClibc-build-issues.patch create mode 100644 buildroot/package/python3/0033-configure.ac-fixup-CC-print-multiarch-output-for-mus.patch delete mode 100644 buildroot/package/qemu/0002-configure-improve-usbfs-check.patch rename buildroot/package/qemu/{ => 3.1.1.1}/0001-user-exec-fix-usage-of-mcontext-structure-on-ARM-uCl.patch (100%) create mode 100644 buildroot/package/qemu/3.1.1.1/0002-linux-user-fix-to-handle-variably-sized-SIOCGSTAMP-with-new-kernels.patch create mode 100644 buildroot/package/qemu/3.1.1.1/0003-util-cacheinfo-fix-crash-when-compiling-with-uClibc.patch create mode 100644 buildroot/package/qemu/3.1.1.1/0004-linux-user-assume-__NR_gettid-always-exists.patch create mode 100644 buildroot/package/qemu/3.1.1.1/0005-linux-user-rename-gettid-to-sys_gettid-to-avoid-clas.patch create mode 100644 buildroot/package/qt5/qt5base/5.11.3/0006-Fix-compile-issue-with-gcc-9.patch create mode 100644 buildroot/package/qt5/qt5base/5.6.3/0004-fix-icu-build-for-qt5webkit.patch create mode 100644 buildroot/package/safeclib/0003-Define-_GNU_SOURCE-when-needed.patch delete mode 100644 buildroot/package/samba4/0002-Fix-compilation-of-Samba-4.7.4-with-disabled-ADS.patch rename buildroot/package/samba4/{0003-Fix-uClibc-build-on-64bit-platforms-by-including-std.patch => 0002-Fix-uClibc-build-on-64bit-platforms-by-including-std.patch} (100%) rename buildroot/package/samba4/{0005-test_regfio.c-include-stdint.h-before-cmoka.h.patch => 0003-test_regfio.c-include-stdint.h-before-cmoka.h.patch} (100%) delete mode 100644 buildroot/package/samba4/0004-Disable-build-of-manpages-and-documentation.patch create mode 100644 buildroot/package/spice/0001-configure.ac-add-enable-tests.patch create mode 100644 buildroot/package/squid/0001-acinclude-os-deps.m4-fix-cross-compilation.patch delete mode 100644 buildroot/package/squid/0001-configure.ac-use-pkg-config-to-find-libxml2.patch create mode 100644 buildroot/package/taglib/0001-fix-taglib-config-file-for-cross-compiling-906.patch create mode 100644 buildroot/package/tcpreplay/0001-configure-ac-fix-without-libdnet.patch create mode 100644 buildroot/package/thttpd/S90thttpd delete mode 100644 buildroot/package/tiff/0001-Fix-for-simple-memory-leak-that-was-assigned-CVE-2019-6128.patch create mode 100644 buildroot/package/tvheadend/0002-Makefile-fix-pie-linking-according-to-disable-pie.patch create mode 100644 buildroot/package/uclibc/0004-sparc-remove-asm-constraint.patch create mode 100644 buildroot/package/uclibc/0005-PowerPC-sync-with-termios-fix-from-glibc.patch delete mode 100644 buildroot/package/webkitgtk/0001-Build-failure-after-r243644-in-GTK-Li.patch create mode 100644 buildroot/package/weston/0002-rdp-compositor-fix-compilation-with-FreeRDP-2.0-rc4.patch rename buildroot/package/x11r7/xserver_xorg-server/{1.20.4 => 1.20.5}/0001-modesettings-needs-dri2.patch (100%) rename buildroot/package/x11r7/xserver_xorg-server/{1.20.4 => 1.20.5}/0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch (100%) rename buildroot/package/x11r7/xserver_xorg-server/{1.20.4 => 1.20.5}/0003-Remove-check-for-useSIGIO-option.patch (100%) rename buildroot/package/x11r7/xserver_xorg-server/{1.20.4 => 1.20.5}/0004-include-misc.h-fix-uClibc-build.patch (100%) rename buildroot/package/x11r7/xserver_xorg-server/{1.20.4 => 1.20.5}/0005-hw-xwayland-Makefile.am-fix-build-without-glx.patch (100%) create mode 100644 buildroot/package/xvisor/0001-x86-Fix-build-break-with-newer-GCC-7-x.patch diff --git a/buildroot-patches/0010-odroid-ux4-firmware.patch b/buildroot-patches/0009-odroid-ux4-firmware.patch similarity index 65% rename from buildroot-patches/0010-odroid-ux4-firmware.patch rename to buildroot-patches/0009-odroid-ux4-firmware.patch index ecbfab213..b1705efaa 100644 --- a/buildroot-patches/0010-odroid-ux4-firmware.patch +++ b/buildroot-patches/0009-odroid-ux4-firmware.patch @@ -1,7 +1,7 @@ -diff --git a/buildroot/package/linux-firmware/Config.in b/buildroot/package/linux-firmware/Config.in +diff --git a/package/linux-firmware/Config.in b/package/linux-firmware/Config.in index 6b182dc6..8e3be238 100644 ---- a/buildroot/package/linux-firmware/Config.in -+++ b/buildroot/package/linux-firmware/Config.in +--- a/package/linux-firmware/Config.in ++++ b/package/linux-firmware/Config.in @@ -44,6 +44,12 @@ config BR2_PACKAGE_LINUX_FIRMWARE_QCOM_ADRENO help Firmware files for Qualcomm Adreno GPU firmware @@ -15,10 +15,10 @@ index 6b182dc6..8e3be238 100644 endmenu # Video menu "Bluetooth firmware" -diff --git a/buildroot/package/linux-firmware/linux-firmware.mk b/buildroot/package/linux-firmware/linux-firmware.mk +diff --git a/package/linux-firmware/linux-firmware.mk b/package/linux-firmware/linux-firmware.mk index 86e1d1e7..6453c402 100644 ---- a/buildroot/package/linux-firmware/linux-firmware.mk -+++ b/buildroot/package/linux-firmware/linux-firmware.mk +--- a/package/linux-firmware/linux-firmware.mk ++++ b/package/linux-firmware/linux-firmware.mk @@ -39,6 +39,12 @@ LINUX_FIRMWARE_FILES += qcom/a* LINUX_FIRMWARE_ALL_LICENSE_FILES += LICENSE.qcom qcom/NOTICE.txt endif diff --git a/buildroot-patches/0009-openvmtools-start-only-inside-a-vmware-env.patch b/buildroot-patches/0009-openvmtools-start-only-inside-a-vmware-env.patch deleted file mode 100644 index 83877f449..000000000 --- a/buildroot-patches/0009-openvmtools-start-only-inside-a-vmware-env.patch +++ /dev/null @@ -1,32 +0,0 @@ -From f80ba7397087960c033bc8ba43959e399aefb250 Mon Sep 17 00:00:00 2001 -From: Pascal Vizeli -Date: Wed, 26 Jun 2019 13:38:47 +0000 -Subject: [PATCH 1/1] openvmtools: start only inside a vmware env - -Signed-off-by: Pascal Vizeli ---- - package/openvmtools/vmtoolsd.service | 5 +++-- - 1 file changed, 3 insertions(+), 2 deletions(-) - -diff --git a/package/openvmtools/vmtoolsd.service b/package/openvmtools/vmtoolsd.service -index 17a4df44c2..1d2a3566cf 100644 ---- a/package/openvmtools/vmtoolsd.service -+++ b/package/openvmtools/vmtoolsd.service -@@ -1,11 +1,12 @@ - [Unit] - Description=vmtoolsd for openvmtools - After=syslog.target network.target -+ConditionVirtualization=vmware - - [Service] - Type=forking --PIDFile=/var/run/vmtoolsd.pid --ExecStart=/usr/bin/vmtoolsd -b /var/run/vmtoolsd.pid -+PIDFile=/run/vmtoolsd.pid -+ExecStart=/usr/bin/vmtoolsd -b /run/vmtoolsd.pid - Restart=on-failure - KillMode=process - KillSignal=SIGKILL --- -2.17.1 - diff --git a/buildroot-patches/0010-Bump-bluez-5.52.patch b/buildroot-patches/0010-Bump-bluez-5.52.patch new file mode 100644 index 000000000..81ef9ef31 --- /dev/null +++ b/buildroot-patches/0010-Bump-bluez-5.52.patch @@ -0,0 +1,51 @@ +From 4e3d6b2b4d600babb79492fbcd04d7bbd16a2a58 Mon Sep 17 00:00:00 2001 +From: Pascal Vizeli +Date: Mon, 30 Dec 2019 13:18:34 +0000 +Subject: [PATCH 1/1] Bump bluez 5.52 + +Signed-off-by: Pascal Vizeli +--- + package/bluez5_utils-headers/bluez5_utils-headers.mk | 2 +- + package/bluez5_utils/bluez5_utils.hash | 2 +- + package/bluez5_utils/bluez5_utils.mk | 2 +- + 3 files changed, 3 insertions(+), 3 deletions(-) + +diff --git a/package/bluez5_utils-headers/bluez5_utils-headers.mk b/package/bluez5_utils-headers/bluez5_utils-headers.mk +index 020e8b4d4e..c61f93a23c 100644 +--- a/package/bluez5_utils-headers/bluez5_utils-headers.mk ++++ b/package/bluez5_utils-headers/bluez5_utils-headers.mk +@@ -5,7 +5,7 @@ + ################################################################################ + + # Keep the version and patches in sync with bluez5_utils +-BLUEZ5_UTILS_HEADERS_VERSION = 5.50 ++BLUEZ5_UTILS_HEADERS_VERSION = 5.52 + BLUEZ5_UTILS_HEADERS_SOURCE = bluez-$(BLUEZ5_UTILS_VERSION).tar.xz + BLUEZ5_UTILS_HEADERS_SITE = $(BR2_KERNEL_MIRROR)/linux/bluetooth + BLUEZ5_UTILS_HEADERS_DL_SUBDIR = bluez5_utils +diff --git a/package/bluez5_utils/bluez5_utils.hash b/package/bluez5_utils/bluez5_utils.hash +index b965708559..00112bc0b6 100644 +--- a/package/bluez5_utils/bluez5_utils.hash ++++ b/package/bluez5_utils/bluez5_utils.hash +@@ -1,4 +1,4 @@ + # From https://www.kernel.org/pub/linux/bluetooth/sha256sums.asc: +-sha256 5ffcaae18bbb6155f1591be8c24898dc12f062075a40b538b745bfd477481911 bluez-5.50.tar.xz ++sha256 f7144ce2039202cfac18ccb52426efea11c98e4f6e1bb8041bcb994b8378560a bluez-5.52.tar.xz + sha256 b499eddebda05a8859e32b820a64577d91f1de2b52efa2a1575a2cb4000bc259 COPYING + sha256 ec60b993835e2c6b79e6d9226345f4e614e686eb57dc13b6420c15a33a8996e5 COPYING.LIB +diff --git a/package/bluez5_utils/bluez5_utils.mk b/package/bluez5_utils/bluez5_utils.mk +index 15c9b670a7..7c5202b717 100644 +--- a/package/bluez5_utils/bluez5_utils.mk ++++ b/package/bluez5_utils/bluez5_utils.mk +@@ -5,7 +5,7 @@ + ################################################################################ + + # Keep the version and patches in sync with bluez5_utils-headers +-BLUEZ5_UTILS_VERSION = 5.50 ++BLUEZ5_UTILS_VERSION = 5.52 + BLUEZ5_UTILS_SOURCE = bluez-$(BLUEZ5_UTILS_VERSION).tar.xz + BLUEZ5_UTILS_SITE = $(BR2_KERNEL_MIRROR)/linux/bluetooth + BLUEZ5_UTILS_INSTALL_STAGING = YES +-- +2.17.1 + diff --git a/buildroot/CHANGES b/buildroot/CHANGES index e3d7ad3bf..f95245379 100644 --- a/buildroot/CHANGES +++ b/buildroot/CHANGES @@ -1,3 +1,182 @@ +2019.02.8, released December 7th, 2019 + + Important / security related fixes. + + Infrastructure: Make HOST__DL_OPTS inherit from + _DL_OPTS by default, just like it is done for a number of + other package variables + + Add _KEEP_PY_FILES to exclude specific python .py files + from the removal done by BR2_PACKAGE_PYTHON{,3}_PYC_ONLY for + the (rare) case where the .py files are needed at runtime + rather than .pyc. + + Fix -reconfigure handling for packages using the kconfig + infrastructure. + + Toolchain: ensure external toolchain kernel headers version + check correctly stop the build on mismatch + + Deconfigs: beaglebone: fix boot issue + + Updated/fixed packages: am33x-cm3, asterisk, bind, chrony, + clamav, collectd, connman, faifa, gob2, haproxy, + intel-microcode, ipsec-tools, jasper, jpeg-turbo, kodi, + kvm-unit-tests, libftdi, libftdi1, libnss, libstrophe, + libsvgtiny, lvm2, lzma, mariadb, minicom, neardal, nodejs, + opencv3, openvmtools, oracle-mysql, perl-gdgraph, + perl-gdtextutil, php, postgresql, prosody, python-django, + rabbitmq-c, rauc, redis, rpcbind, socat, spice, + spice-protocol, tftpd, tiff, webkitgtk + + New packages: libmspack + + Issues resolved (http://bugs.uclibc.org): + + #12166: Compiling nodejs for SAMA5D3 always crash with illegal inst.. + #12171: Python-opencv needs config.py and config-3.7.py to run.. + #12211: host-nodejs 10.15.3 package fail to build + #12316: tzdata fails to install with empty "default local time" + +2019.02.7, Released November 10th, 2019 + + Important / security related fixes. + + support/testing: use a kernel with HW_RANDOM_VIRTIO to work + around issues with lack of entrophy + + Toolchain: Also copy libssp.so for external toolchains if SSP + is enabled to handle toolchains providing SSP support in + libssp rather than in the C library + + Download: Also use the package download method for extra + downloads from the same site, so it does not get confused by + URLs containing '+' + + Fakeroot now works correctly under Microsoft Windows 10 + Services for Linux, which does not provide SYSV IPC support + + utils/test-pkg: ensure to exit with an error upon failure + + Updated/fixed packages: asterisk, azmq, cups-filters, + domoticz, duma, elf2flt, eudev, exfat, exfat-utils, fakeroot, + file, freerdp, gd, ghostscript, go, gvfs, intel-microcode, + kvm-unit-tests, libarchive, libnspr, libnss, libopenssl, + libpcap, libpciaccess, librsvg, libseccomp, libsigrok, + libtorrent, libunwind, linux-tools, lua-sdl2, lxc, minizip, + mjpegtools, mongoose, php, python, python-pysnmp-apps, + python3, qemu, qt5base, ruby, safeclib, samba4, sdl_mixer, + sox, sudo, systemd, tcpdump, unscd, util-lkinux, vtun, xvisor, + yaffs2utils + + Issues resolved (http://bugs.uclibc.org): + + #11366: [2018.08] SysV IPC not available for fakeroot on WSL + #12261: sudo versions prior to 1.8.28 are affected + +2019.02.6, Released October 3rd, 2019 + + Important / security related fixes. + + Defconfigs: AArch64-efi: Fix grub configuration, Beaglebone: + Use default console settings + + Dependencies: Ensure host has JSON::PP perl module installed + if webkitgtk/wpewebkit packages are enabled as it is needed + during their build process. + + Toolchain: Generate check-headers program under BUILD_DIR + rather than /tmp to fix issues with distributions mounting + /tmp noexec. + + Updated/fixed packages: asterisk, augeas, bind, bwm-ng, cups, + cups-filters, docker-cli, docker-engine, docker-proxy, + dropbear, e2fsprogs, eudev, exim, expat, gcc, go, ifplugd, + haveged, iptables, joe, kf5-extra-cmake-modules, + kf5-modemmanager-qt, kf5-networkmanager-qt, libcurl, + libgcrypt, libgpg-error, libnftl, libnspr, libnss, libopenssl, + luksmeta, mariadb, mbedtls, mongodb, mosquitto, ncurses, + nfs-utils, nghttp2, nodejs, openvmtools, php, protobuf, putty, + qemu, qt5base, samba4, swupdate, systemd-bootchart, thttpd, + uclibc, unzip, util-linux, wireshark + + Issues resolved (http://bugs.uclibc.org): + + #10806: Allow nfs-utils to use ipv6 + #11781: mariadb build error + #12031: Build of cups-filters fails while linking, apparently due.. + #12141: eudev package is missing "render" and "kvm" groups + #12181: dropbear: norootlogin (-w) no longer works when PAM is enabled + #12241: Permission denied while running "make" + +2019.02.5, Released September 2nd, 2019 + + Important / security related fixes. + + Filesystems: Pass extra pax options to tar for binary + reproducibility. + + Updated/fixed packages: apache, arm-trusted-firmware, + asterisk, atk, autofs, batctl, batman-adv, berkeleydb, brotli, + busybox, bzip2, clamav, cloop, cmake, collectd, connman-gtk, + cryptopp, dahdi-linux, dahdi-tools, daq, dehydrated, dovecot, + dovecot-pigeonhole,, elfutils, evtest, exim, expect, giflib, + git, glib-networking, glibc, gnupg2, gnutls, go, + gst1-rtsp-server, gtkperf, gupnp-tools, gvfs, imagemagick, + imx-uuc, intel-microcode, json-glib, lftp, libbsd, libcurl, + libgit2, libgtk3, libmodplug, libnss, libpri, libshout, + libss7, libssh2, libvips, libxcb, linux-headers, mdadm, + mesa3d, metacity, mpg123, mosquitto, musl, nginx, openblas, + opencv3, openldap, openvmtools, pcmanfm, php, pigpio, + postgresql, prboom, proftpd, proj, python, python-django, + python-idna, python-numpy, python-urllib3, python3, qemu, qt5, + qt5base, qt5enginio, quagga, rygel, squid, subversion, + tcpreplay, unzip, vlc, vte, webkitgtk, weston, wireless-regdb, + xen, xfont_font-util, xlib_libICE, xlib_libXfont, + xlib_libXfont2, yad, zeromq + + Issues resolved (http://bugs.uclibc.org): + + #11741: pigpio does not build host-pigpio + #11876: automount using host mount/umount + #11881: Build breaks with lftp package enabled and libexpat1-dev inst.. + #11921: dahdi fails to build + #11961: libpri build failure + #12096: tcpreplay: build fails if libdumbnet-dev is installed in the.. + #12106: daq: build fails if libdumbnet-dev is installed in the host + #12126: vc4 has neon as hard dependency + +2019.02.4, Released July 10th, 2019 + + Important / security related fixes. + + arch: x86: Fix typo breaking 'core-avx2' variant, add Westmere + variant. + + linux: Workaround -Werror related build failure on powerpc, + by forcing CONFIG_PPC_DISABLE_WERROR on. + + support/testing: Emulate a machine with 256MB RAM to fix + issues with certain tests running out of memory. + + test-pkg: Correct long option handling and clean output dir + after a successful build to save disk space. + + Ensure custom _OVERRIDE_SRCDIR_RSYNC_EXCLUSIONS are + passed before the standard exclusions so they are not ignored + by rsync when using override-srcdir. + + Defconfigs: QEMU: use 'rootwait' kernel option to ensure root + partition is available before mounting. + + Updated/fixed packages: barebox, bzip2, davfs2, dbus, dialog, + docker-cli, docker-engine, expat, faad2, ffmpeg, freeswitch, + gerbera, haveged, irssi, libcdadio, libgit2, libglib2, + libsecret, libvncserver, lmbench, logrotate, mariadb, meson, + mongoose, monit, mpd, openblas, php, postgresql, psplash, + python, python-django, python3, qt5base, samba4, taglib, + tvheadend, vlc, webkitgtk, xserver_xorg-server, znc + 2019.02.3, Released June 7th, 2019 Important / security related fixes. @@ -26,6 +205,8 @@ sqlite, subversion, supertux, systemd, tslib, uclibc, v4l2loopback, webkitgtk, woff2 + Issues resolved (http://bugs.uclibc.org): + #11816: Only selected coreutils binaries are installed #11841: grub-efi.cfg not used when building EFI disk image #11911: systemd v240 memory leak in systemd-journald diff --git a/buildroot/DEVELOPERS b/buildroot/DEVELOPERS index 0d185ee97..58adad5c1 100644 --- a/buildroot/DEVELOPERS +++ b/buildroot/DEVELOPERS @@ -26,9 +26,6 @@ # infrastructure, and will be CC'ed on all patches that add or # modify packages that use this infrastructure. -N: Abhilash Tuse -F: package/gstreamer1/gst1-rtsp-server/ - N: Adam Duskett F: package/audit/ F: package/busybox/ @@ -127,7 +124,6 @@ N: Anders Darander F: package/ktap/ N: André Hentschel -F: package/azure-iot-sdk-c/ F: package/libkrb5/ F: package/openal/ F: package/p7zip/ @@ -148,9 +144,6 @@ F: package/zstd/ N: Andrey Yurovsky F: package/rauc/ -N: Andy Kennedy -F: package/libunwind/ - N: Angelo Compagnucci F: package/corkscrew/ F: package/fail2ban/ @@ -209,11 +202,12 @@ F: package/sqlcipher/ F: package/stress/ N: Asaf Kahlon +F: package/collectd/ F: package/libuv/ F: package/python* F: package/zeromq/ -N: Ash Charles +N: Ash Charles F: package/pru-software-support/ F: package/ti-cgt-pru/ @@ -267,7 +261,6 @@ F: package/alsa-utils/ F: package/apache/ F: package/apr/ F: package/apr-util/ -F: package/asterisk/ F: package/bcg729/ F: package/bluez-tools/ F: package/boinc/ @@ -316,6 +309,7 @@ F: package/libilbc/ F: package/libldns/ F: package/libmicrohttpd/ F: package/libminiupnpc/ +F: package/libmspack/ F: package/libnatpmp/ F: package/libnpth/ F: package/libogg/ @@ -563,9 +557,6 @@ F: package/log4cpp/ N: Daniel Nicoletti F: package/cutelyst/ -N: Daniel Nyström -F: package/e2tools/ - N: Daniel Price F: package/nodejs/ F: package/redis/ @@ -633,9 +624,6 @@ F: package/unscd/ N: Dushara Jayasinghe F: package/prosody/ -N: Ed Swierk -F: package/xxhash/ - N: Eric Le Bihan F: docs/manual/adding-packages-meson.txt F: package/adwaita-icon-theme/ @@ -819,7 +807,9 @@ F: package/ser2net/ N: Francois Perrad F: board/olimex/a20_olinuxino +F: board/olimex/imx233_olinuxino/ F: configs/olimex_a20_olinuxino_* +F: configs/olimex_imx233_olinuxino_defconfig F: package/4th/ F: package/chipmunk/ F: package/dado/ @@ -892,7 +882,7 @@ F: package/tesseract-ocr/ F: package/webp/ F: package/xapian/ -N: Giulio Benetti +N: Giulio Benetti F: package/minicom/ F: package/sunxi-mali-mainline/ F: package/sunxi-mali-mainline-driver/ @@ -1131,10 +1121,6 @@ F: package/phidgetwebservice/ F: package/rapidxml/ F: package/sphinxbase/ -N: Jonathan Liu -F: package/python-meld3/ -F: package/supervisor/ - N: Jörg Krause F: board/lemaker/bananapro/ F: configs/bananapro_defconfig @@ -1201,9 +1187,6 @@ F: package/python-pygame/ N: Julien Corjon F: package/qt5/ -N: Julien Floret -F: package/lldpd/ - N: Julien Grossholtz F: package/paho-mqtt-c @@ -1223,9 +1206,6 @@ F: package/cpuload/ F: package/bwm-ng/ F: package/ramsmp/ -N: Kevin Joly -F: package/libgphoto2/ - N: Koen Martens F: package/capnproto/ F: package/linuxconsoletools/ @@ -1329,9 +1309,6 @@ F: package/luaossl/ F: package/rs485conf/ F: package/turbolua/ -N: Marcin Nowakowski -F: package/libkcapi/ - N: Marcus Folkesson F: package/libostree/ F: package/libselinux/ @@ -1354,7 +1331,7 @@ F: package/lynx/ N: Mario Rugiero F: package/ratpoison/ -N: Mark Corbin +N: Mark Corbin F: arch/arch.mk.riscv F: arch/Config.in.riscv F: board/qemu/riscv32-virt/ @@ -1363,10 +1340,6 @@ F: boot/riscv-pk/ F: configs/qemu_riscv32_virt_defconfig F: configs/qemu_riscv64_virt_defconfig -N: Markos Chandras -F: package/harfbuzz/ -F: package/libsecret/ - N: Martin Bark F: board/raspberrypi/ F: configs/raspberrypi3_defconfig @@ -1387,7 +1360,7 @@ F: package/tslib/ F: package/x11r7/xdriver_xf86-input-tslib/ F: package/x11vnc/ -N: Mathieu Audat +N: Mathieu Audat F: board/technologic/ts4900/ F: configs/ts4900_defconfig F: package/ts4900-fpga/ @@ -1547,6 +1520,9 @@ F: package/python-pyzmq/ N: Michael Trimarchi F: package/python-spidev/ +N: Michael Vetter +F: package/jasper/ + N: Michał Łyszczek F: board/altera/socrates_cyclone5/ F: board/pine64/rock64 @@ -1566,9 +1542,6 @@ F: package/shadowsocks-libev/ N: Mirza Krak F: package/mender/ -N: Morgan Delestre -F: package/monkey/ - N: Murat Demirten F: package/jpeg-turbo/ F: package/libgeotiff/ @@ -1698,6 +1671,8 @@ F: package/python-webob/ F: package/python-websocket-client/ F: package/sedutil/ F: package/triggerhappy/ +F: package/wireguard/ +F: support/testing/tests/package/test_docker_compose.py N: Peter Seiderer F: board/raspberrypi/ @@ -1781,9 +1756,6 @@ F: package/libdvbpsi/ F: package/mraa/ F: package/synergy/ -N: Pranit Sirsat -F: package/paho-mqtt-c/ - N: Qais Yousef F: package/bellagio/ @@ -1814,7 +1786,13 @@ N: Ricardo Martincoski F: package/atop/ N: Ricardo Martincoski -F: support/testing/ +F: support/testing/infra/ +F: support/testing/run-tests +F: support/testing/tests/core/test_file_capabilities.py +F: support/testing/tests/download/ +F: support/testing/tests/package/*_python*.py +F: support/testing/tests/package/test_atop.py +F: support/testing/tests/package/test_syslog_ng.py F: utils/check-package F: utils/checkpackagelib/ @@ -1840,6 +1818,8 @@ F: package/vnstat/ N: Romain Naour F: package/aubio/ F: package/bullet/ +F: package/clang/ +F: package/clinfo/ F: package/efl/ F: package/enlightenment/ F: package/flare-engine/ @@ -1847,9 +1827,11 @@ F: package/flare-game/ F: package/irrlicht/ F: package/liblinear/ F: package/lensfun/ +F: package/libclc/ F: package/libgta/ F: package/libspatialindex/ F: package/linux-syscall-support/ +F: package/llvm/ F: package/lugaru/ F: package/mcelog/ F: package/mesa3d/ @@ -2036,9 +2018,6 @@ F: package/tovid/ F: package/udftools/ F: package/xorriso/ -N: Steve Thomas -F: package/isl/ - N: Steven Noonan F: package/hwloc/ F: package/powertop/ @@ -2176,7 +2155,7 @@ F: package/pixz/ N: Vinicius Tinti F: package/python-thrift/ -N: Vivien Didelot +N: Vivien Didelot F: board/technologic/ts5500/ F: configs/ts5500_defconfig @@ -2258,6 +2237,8 @@ F: package/zisofs-tools/ F: support/download/ N: Yegor Yefremov +F: configs/beaglebone_defconfig +F: configs/beaglebone_qt5_defconfig F: package/acl/ F: package/attr/ F: package/bluez_utils/ @@ -2266,6 +2247,7 @@ F: package/bootstrap/ F: package/cannelloni/ F: package/can-utils/ F: package/circus/ +F: package/dhcpcd/ F: package/feh/ F: package/giblib/ F: package/imlib2/ @@ -2282,6 +2264,7 @@ F: package/libubox/ F: package/libuci/ F: package/linux-firmware/ F: package/modem-manager/ +F: package/nftables/ F: package/nuttcp/ F: package/parted/ F: package/phytool/ diff --git a/buildroot/Makefile b/buildroot/Makefile index 2c8146e87..dfa62870c 100644 --- a/buildroot/Makefile +++ b/buildroot/Makefile @@ -92,9 +92,9 @@ all: .PHONY: all # Set and export the version string -export BR2_VERSION := 2019.02.3 +export BR2_VERSION := 2019.02.8 # Actual time the release is cut (for reproducible builds) -BR2_VERSION_EPOCH = 1559893000 +BR2_VERSION_EPOCH = 1575746000 # Save running make version since it's clobbered by the make package RUNNING_MAKE_VERSION := $(MAKE_VERSION) @@ -248,7 +248,6 @@ ifeq ($(BR2_REPRODUCIBLE),y) export TZ = UTC export LANG = C export LC_ALL = C -export GZIP = -n endif # To put more focus on warnings, be less verbose as default @@ -811,6 +810,7 @@ endif # merged /usr .PHONY: target-post-image target-post-image: $(TARGETS_ROOTFS) target-finalize staging-finalize @rm -f $(ROOTFS_COMMON_TAR) + $(Q)mkdir -p $(BINARIES_DIR) @$(foreach s, $(call qstrip,$(BR2_ROOTFS_POST_IMAGE_SCRIPT)), \ $(call MESSAGE,"Executing post-image script $(s)"); \ $(EXTRA_ENV) $(s) $(BINARIES_DIR) $(call qstrip,$(BR2_ROOTFS_POST_SCRIPT_ARGS))$(sep)) diff --git a/buildroot/arch/Config.in.x86 b/buildroot/arch/Config.in.x86 index f7c53a0fa..331ee06bf 100644 --- a/buildroot/arch/Config.in.x86 +++ b/buildroot/arch/Config.in.x86 @@ -101,6 +101,15 @@ config BR2_x86_corei7 select BR2_X86_CPU_HAS_SSSE3 select BR2_X86_CPU_HAS_SSE4 select BR2_X86_CPU_HAS_SSE42 +config BR2_x86_westmere + bool "westmere" + select BR2_X86_CPU_HAS_MMX + select BR2_X86_CPU_HAS_SSE + select BR2_X86_CPU_HAS_SSE2 + select BR2_X86_CPU_HAS_SSE3 + select BR2_X86_CPU_HAS_SSSE3 + select BR2_X86_CPU_HAS_SSE4 + select BR2_X86_CPU_HAS_SSE42 config BR2_x86_corei7_avx bool "corei7-avx" select BR2_X86_CPU_HAS_MMX @@ -235,8 +244,9 @@ config BR2_ARCH default "i686" if BR2_x86_nocona && BR2_i386 default "i686" if BR2_x86_core2 && BR2_i386 default "i686" if BR2_x86_corei7 && BR2_i386 + default "i686" if BR2_x86_westmere && BR2_i386 default "i686" if BR2_x86_corei7_avx && BR2_i386 - default "i686" if BR2_x86_corei7_avx2 && BR2_i386 + default "i686" if BR2_x86_core_avx2 && BR2_i386 default "i686" if BR2_x86_atom && BR2_i386 default "i686" if BR2_x86_silvermont && BR2_i386 default "i686" if BR2_x86_opteron && BR2_i386 @@ -271,6 +281,7 @@ config BR2_GCC_TARGET_ARCH default "corei7-avx" if BR2_x86_corei7_avx default "core-avx2" if BR2_x86_core_avx2 default "atom" if BR2_x86_atom + default "westmere" if BR2_x86_westmere default "silvermont" if BR2_x86_silvermont default "k8" if BR2_x86_opteron default "k8-sse3" if BR2_x86_opteron_sse3 diff --git a/buildroot/board/beaglebone/uEnv.txt b/buildroot/board/beaglebone/uEnv.txt index a665f2088..8fce54d87 100644 --- a/buildroot/board/beaglebone/uEnv.txt +++ b/buildroot/board/beaglebone/uEnv.txt @@ -3,6 +3,9 @@ devtype=mmc bootdir= bootfile=zImage bootpartition=mmcblk0p2 +console=ttyS0,115200n8 +loadaddr=0x82000000 +fdtaddr=0x88000000 set_mmc1=if test $board_name = A33515BB; then setenv bootpartition mmcblk1p2; fi -set_bootargs=setenv bootargs console=ttyO0,115200n8 root=/dev/${bootpartition} rw rootfstype=ext4 rootwait +set_bootargs=setenv bootargs console=${console} root=/dev/${bootpartition} rw rootfstype=ext4 rootwait uenvcmd=run set_mmc1; run set_bootargs;run loadimage;run loadfdt;printenv bootargs;bootz ${loadaddr} - ${fdtaddr} diff --git a/buildroot/board/qemu/aarch64-virt/readme.txt b/buildroot/board/qemu/aarch64-virt/readme.txt index 1ff2fba47..f868905d9 100644 --- a/buildroot/board/qemu/aarch64-virt/readme.txt +++ b/buildroot/board/qemu/aarch64-virt/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-aarch64 -M virt -cpu cortex-a53 -nographic -smp 1 -kernel output/images/Image -append "root=/dev/vda console=ttyAMA0" -netdev user,id=eth0 -device virtio-net-device,netdev=eth0 -drive file=output/images/rootfs.ext4,if=none,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 + qemu-system-aarch64 -M virt -cpu cortex-a53 -nographic -smp 1 -kernel output/images/Image -append "rootwait root=/dev/vda console=ttyAMA0" -netdev user,id=eth0 -device virtio-net-device,netdev=eth0 -drive file=output/images/rootfs.ext4,if=none,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/arm-versatile/readme.txt b/buildroot/board/qemu/arm-versatile/readme.txt index 33cdb7b81..f3a9e1ab4 100644 --- a/buildroot/board/qemu/arm-versatile/readme.txt +++ b/buildroot/board/qemu/arm-versatile/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user + qemu-system-arm -M versatilepb -kernel output/images/zImage -dtb output/images/versatile-pb.dtb -drive file=output/images/rootfs.ext2,if=scsi,format=raw -append "rootwait root=/dev/sda console=ttyAMA0,115200" -serial stdio -net nic,model=rtl8139 -net user Or for the noMMU emulation: diff --git a/buildroot/board/qemu/arm-vexpress/readme.txt b/buildroot/board/qemu/arm-vexpress/readme.txt index 35137e050..7f7b43a3b 100644 --- a/buildroot/board/qemu/arm-vexpress/readme.txt +++ b/buildroot/board/qemu/arm-vexpress/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-arm -M vexpress-a9 -smp 1 -m 256 -kernel output/images/zImage -dtb output/images/vexpress-v2p-ca9.dtb -drive file=output/images/rootfs.ext2,if=sd,format=raw -append "console=ttyAMA0,115200 root=/dev/mmcblk0" -serial stdio -net nic,model=lan9118 -net user + qemu-system-arm -M vexpress-a9 -smp 1 -m 256 -kernel output/images/zImage -dtb output/images/vexpress-v2p-ca9.dtb -drive file=output/images/rootfs.ext2,if=sd,format=raw -append "console=ttyAMA0,115200 rootwait root=/dev/mmcblk0" -serial stdio -net nic,model=lan9118 -net user The login prompt will appear in the terminal that started Qemu. The graphical window is the framebuffer. diff --git a/buildroot/board/qemu/m68k-q800/readme.txt b/buildroot/board/qemu/m68k-q800/readme.txt index bead8cdde..b516bacdf 100644 --- a/buildroot/board/qemu/m68k-q800/readme.txt +++ b/buildroot/board/qemu/m68k-q800/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-m68k -M q800 -kernel output/images/vmlinux -nographic -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/sda console=ttyS0" + qemu-system-m68k -M q800 -kernel output/images/vmlinux -nographic -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/sda console=ttyS0" The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/mips32r2-malta/readme.txt b/buildroot/board/qemu/mips32r2-malta/readme.txt index d1bbcc474..9ff3c4b81 100644 --- a/buildroot/board/qemu/mips32r2-malta/readme.txt +++ b/buildroot/board/qemu/mips32r2-malta/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-mips -M malta -kernel output/images/vmlinux -serial stdio -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/hda" -net nic,model=pcnet -net user + qemu-system-mips -M malta -kernel output/images/vmlinux -serial stdio -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/hda" -net nic,model=pcnet -net user The login prompt will appear in the terminal that started Qemu. The graphical window is the framebuffer. No keyboard support has been diff --git a/buildroot/board/qemu/mips32r2el-malta/readme.txt b/buildroot/board/qemu/mips32r2el-malta/readme.txt index 4f59d3430..745bfea60 100644 --- a/buildroot/board/qemu/mips32r2el-malta/readme.txt +++ b/buildroot/board/qemu/mips32r2el-malta/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-mipsel -M malta -kernel output/images/vmlinux -serial stdio -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/hda" -net nic,model=pcnet -net user + qemu-system-mipsel -M malta -kernel output/images/vmlinux -serial stdio -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/hda" -net nic,model=pcnet -net user The login prompt will appear in the terminal that started Qemu. The graphical window is the framebuffer. No keyboard support has been diff --git a/buildroot/board/qemu/mips32r6-malta/readme.txt b/buildroot/board/qemu/mips32r6-malta/readme.txt index 04de7e5c3..6a026b216 100644 --- a/buildroot/board/qemu/mips32r6-malta/readme.txt +++ b/buildroot/board/qemu/mips32r6-malta/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: -qemu-system-mips -M malta -cpu mips32r6-generic -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/hda" -nographic +qemu-system-mips -M malta -cpu mips32r6-generic -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/hda" -nographic The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/mips32r6el-malta/readme.txt b/buildroot/board/qemu/mips32r6el-malta/readme.txt index 88602de0b..f69fd21af 100644 --- a/buildroot/board/qemu/mips32r6el-malta/readme.txt +++ b/buildroot/board/qemu/mips32r6el-malta/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: -qemu-system-mipsel -M malta -cpu mips32r6-generic -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/hda" -net nic,model=pcnet -net user -nographic +qemu-system-mipsel -M malta -cpu mips32r6-generic -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/hda" -net nic,model=pcnet -net user -nographic The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/mips64-malta/readme.txt b/buildroot/board/qemu/mips64-malta/readme.txt index f0e7fef79..ea3a92541 100644 --- a/buildroot/board/qemu/mips64-malta/readme.txt +++ b/buildroot/board/qemu/mips64-malta/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-mips64 -M malta -kernel output/images/vmlinux -serial stdio -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/hda" + qemu-system-mips64 -M malta -kernel output/images/vmlinux -serial stdio -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/hda" The login prompt will appear in the terminal that started Qemu. The graphical window is the framebuffer. diff --git a/buildroot/board/qemu/mips64el-malta/readme.txt b/buildroot/board/qemu/mips64el-malta/readme.txt index 03b149bc8..144da9383 100644 --- a/buildroot/board/qemu/mips64el-malta/readme.txt +++ b/buildroot/board/qemu/mips64el-malta/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-mips64el -M malta -kernel output/images/vmlinux -serial stdio -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/hda" + qemu-system-mips64el -M malta -kernel output/images/vmlinux -serial stdio -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/hda" The login prompt will appear in the terminal that started Qemu. The graphical window is the framebuffer. diff --git a/buildroot/board/qemu/mips64r6-malta/readme.txt b/buildroot/board/qemu/mips64r6-malta/readme.txt index bf5b517a3..cfa16fd86 100644 --- a/buildroot/board/qemu/mips64r6-malta/readme.txt +++ b/buildroot/board/qemu/mips64r6-malta/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-mips64 -M malta -cpu I6400 -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/hda" -nographic + qemu-system-mips64 -M malta -cpu I6400 -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/hda" -nographic The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/mips64r6el-malta/readme.txt b/buildroot/board/qemu/mips64r6el-malta/readme.txt index d51bffd08..61a6ceb5f 100644 --- a/buildroot/board/qemu/mips64r6el-malta/readme.txt +++ b/buildroot/board/qemu/mips64r6el-malta/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-mips64el -M malta -cpu I6400 -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/hda" -nographic + qemu-system-mips64el -M malta -cpu I6400 -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/hda" -nographic The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/ppc-g3beige/readme.txt b/buildroot/board/qemu/ppc-g3beige/readme.txt index 1c3b51539..608814ee3 100644 --- a/buildroot/board/qemu/ppc-g3beige/readme.txt +++ b/buildroot/board/qemu/ppc-g3beige/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-ppc -M g3beige -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "console=ttyS0 root=/dev/hda" -serial stdio -net nic,model=rtl8139 -net user + qemu-system-ppc -M g3beige -kernel output/images/vmlinux -drive file=output/images/rootfs.ext2,format=raw -append "console=ttyS0 rootwait root=/dev/hda" -serial stdio -net nic,model=rtl8139 -net user The login prompt will appear in the terminal that started Qemu. The graphical window is the framebuffer. diff --git a/buildroot/board/qemu/ppc64-e5500/readme.txt b/buildroot/board/qemu/ppc64-e5500/readme.txt index cfc563974..808076698 100644 --- a/buildroot/board/qemu/ppc64-e5500/readme.txt +++ b/buildroot/board/qemu/ppc64-e5500/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-ppc64 -M ppce500 -cpu e5500 -m 256 -kernel output/images/uImage -drive file=output/images/rootfs.ext2,if=virtio,format=raw -append "console=ttyS0 root=/dev/vda" -serial mon:stdio -nographic + qemu-system-ppc64 -M ppce500 -cpu e5500 -m 256 -kernel output/images/uImage -drive file=output/images/rootfs.ext2,if=virtio,format=raw -append "console=ttyS0 rootwait root=/dev/vda" -serial mon:stdio -nographic The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/ppc64-pseries/readme.txt b/buildroot/board/qemu/ppc64-pseries/readme.txt index 5069df9e5..6a3e96a2e 100644 --- a/buildroot/board/qemu/ppc64-pseries/readme.txt +++ b/buildroot/board/qemu/ppc64-pseries/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-ppc64 -M pseries -cpu POWER7 -m 256 -kernel output/images/vmlinux -append "console=hvc0 root=/dev/sda" -drive file=output/images/rootfs.ext2,if=scsi,index=0,format=raw -serial stdio -display curses + qemu-system-ppc64 -M pseries -cpu POWER7 -m 256 -kernel output/images/vmlinux -append "console=hvc0 rootwait root=/dev/sda" -drive file=output/images/rootfs.ext2,if=scsi,index=0,format=raw -serial stdio -display curses The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/ppc64le-pseries/readme.txt b/buildroot/board/qemu/ppc64le-pseries/readme.txt index c23da70df..2728675df 100644 --- a/buildroot/board/qemu/ppc64le-pseries/readme.txt +++ b/buildroot/board/qemu/ppc64le-pseries/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: -qemu-system-ppc64 -M pseries -cpu POWER8 -m 256 -kernel output/images/vmlinux -append "console=hvc0 root=/dev/sda" -drive file=output/images/rootfs.ext2,if=scsi,index=0,format=raw -serial stdio -display curses +qemu-system-ppc64 -M pseries -cpu POWER8 -m 256 -kernel output/images/vmlinux -append "console=hvc0 rootwait root=/dev/sda" -drive file=output/images/rootfs.ext2,if=scsi,index=0,format=raw -serial stdio -display curses The login prompt will appear in the terminal window. diff --git a/buildroot/board/qemu/riscv32-virt/readme.txt b/buildroot/board/qemu/riscv32-virt/readme.txt index 2da99580e..24d44f0a9 100644 --- a/buildroot/board/qemu/riscv32-virt/readme.txt +++ b/buildroot/board/qemu/riscv32-virt/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-riscv32 -M virt -kernel output/images/bbl -append "root=/dev/vda ro console=ttyS0" -drive file=output/images/rootfs.ext2,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 -netdev user,id=net0 -device virtio-net-device,netdev=net0 -nographic + qemu-system-riscv32 -M virt -kernel output/images/bbl -append "rootwait root=/dev/vda ro console=ttyS0" -drive file=output/images/rootfs.ext2,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 -netdev user,id=net0 -device virtio-net-device,netdev=net0 -nographic The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/riscv64-virt/readme.txt b/buildroot/board/qemu/riscv64-virt/readme.txt index 9f6e35c86..e878330de 100644 --- a/buildroot/board/qemu/riscv64-virt/readme.txt +++ b/buildroot/board/qemu/riscv64-virt/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-riscv64 -M virt -kernel output/images/bbl -append "root=/dev/vda ro console=ttyS0" -drive file=output/images/rootfs.ext2,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 -netdev user,id=net0 -device virtio-net-device,netdev=net0 -nographic + qemu-system-riscv64 -M virt -kernel output/images/bbl -append "rootwait root=/dev/vda ro console=ttyS0" -drive file=output/images/rootfs.ext2,format=raw,id=hd0 -device virtio-blk-device,drive=hd0 -netdev user,id=net0 -device virtio-net-device,netdev=net0 -nographic The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/sh4-r2d/readme.txt b/buildroot/board/qemu/sh4-r2d/readme.txt index d22af73ae..dd80953b9 100644 --- a/buildroot/board/qemu/sh4-r2d/readme.txt +++ b/buildroot/board/qemu/sh4-r2d/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-sh4 -M r2d -kernel output/images/zImage -drive file=output/images/rootfs.ext2,if=ide,format=raw -append "root=/dev/sda console=ttySC1,115200 noiotrap" -serial null -serial stdio -net nic,model=rtl8139 -net user + qemu-system-sh4 -M r2d -kernel output/images/zImage -drive file=output/images/rootfs.ext2,if=ide,format=raw -append "rootwait root=/dev/sda console=ttySC1,115200 noiotrap" -serial null -serial stdio -net nic,model=rtl8139 -net user The login prompt will appear in the terminal that started Qemu. The graphical window is the framebuffer. diff --git a/buildroot/board/qemu/sh4eb-r2d/readme.txt b/buildroot/board/qemu/sh4eb-r2d/readme.txt index daf515ab2..e71a9bce9 100644 --- a/buildroot/board/qemu/sh4eb-r2d/readme.txt +++ b/buildroot/board/qemu/sh4eb-r2d/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-sh4eb -M r2d -kernel output/images/zImage -drive file=output/images/rootfs.ext2,if=ide,format=raw -append "root=/dev/sda console=ttySC1,115200 noiotrap" -serial null -serial stdio -net nic,model=rtl8139 -net user + qemu-system-sh4eb -M r2d -kernel output/images/zImage -drive file=output/images/rootfs.ext2,if=ide,format=raw -append "rootwait root=/dev/sda console=ttySC1,115200 noiotrap" -serial null -serial stdio -net nic,model=rtl8139 -net user The login prompt will appear in the terminal that started Qemu. The graphical window is the framebuffer. diff --git a/buildroot/board/qemu/sparc-ss10/readme.txt b/buildroot/board/qemu/sparc-ss10/readme.txt index df6a75a3f..33833c2d3 100644 --- a/buildroot/board/qemu/sparc-ss10/readme.txt +++ b/buildroot/board/qemu/sparc-ss10/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-sparc -M SS-10 -kernel output/images/zImage -drive file=output/images/rootfs.ext2,format=raw -append "root=/dev/sda console=ttyS0,115200" -serial stdio -net nic,model=lance -net user + qemu-system-sparc -M SS-10 -kernel output/images/zImage -drive file=output/images/rootfs.ext2,format=raw -append "rootwait root=/dev/sda console=ttyS0,115200" -serial stdio -net nic,model=lance -net user The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/sparc64-sun4u/readme.txt b/buildroot/board/qemu/sparc64-sun4u/readme.txt index 24d5bbaff..f2e6e81a8 100644 --- a/buildroot/board/qemu/sparc64-sun4u/readme.txt +++ b/buildroot/board/qemu/sparc64-sun4u/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-sparc64 -M sun4u -kernel output/images/vmlinux -append "root=/dev/sda console=ttyS0,115200" -serial stdio -drive file=output/images/rootfs.ext2,format=raw -net nic,model=e1000 -net user + qemu-system-sparc64 -M sun4u -kernel output/images/vmlinux -append "rootwait root=/dev/sda console=ttyS0,115200" -serial stdio -drive file=output/images/rootfs.ext2,format=raw -net nic,model=e1000 -net user The login prompt will appear in the terminal that started Qemu. diff --git a/buildroot/board/qemu/x86/readme.txt b/buildroot/board/qemu/x86/readme.txt index c5e687734..42fc2439d 100644 --- a/buildroot/board/qemu/x86/readme.txt +++ b/buildroot/board/qemu/x86/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-i386 -M pc -kernel output/images/bzImage -drive file=output/images/rootfs.ext2,if=virtio,format=raw -append "root=/dev/vda" -net nic,model=virtio -net user + qemu-system-i386 -M pc -kernel output/images/bzImage -drive file=output/images/rootfs.ext2,if=virtio,format=raw -append "rootwait root=/dev/vda" -net nic,model=virtio -net user Optionally add -smp N to emulate a SMP system with N CPUs. diff --git a/buildroot/board/qemu/x86_64/readme.txt b/buildroot/board/qemu/x86_64/readme.txt index 425e34b12..4a1c0c0ff 100644 --- a/buildroot/board/qemu/x86_64/readme.txt +++ b/buildroot/board/qemu/x86_64/readme.txt @@ -1,6 +1,6 @@ Run the emulation with: - qemu-system-x86_64 -M pc -kernel output/images/bzImage -drive file=output/images/rootfs.ext2,if=virtio,format=raw -append "root=/dev/vda" -net nic,model=virtio -net user + qemu-system-x86_64 -M pc -kernel output/images/bzImage -drive file=output/images/rootfs.ext2,if=virtio,format=raw -append "rootwait root=/dev/vda" -net nic,model=virtio -net user Optionally add -smp N to emulate a SMP system with N CPUs. diff --git a/buildroot/boot/arm-trusted-firmware/arm-trusted-firmware.mk b/buildroot/boot/arm-trusted-firmware/arm-trusted-firmware.mk index 8ca3864dd..464e4d95e 100644 --- a/buildroot/boot/arm-trusted-firmware/arm-trusted-firmware.mk +++ b/buildroot/boot/arm-trusted-firmware/arm-trusted-firmware.mk @@ -5,8 +5,6 @@ ################################################################################ ARM_TRUSTED_FIRMWARE_VERSION = $(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_VERSION)) -ARM_TRUSTED_FIRMWARE_LICENSE = BSD-3-Clause -ARM_TRUSTED_FIRMWARE_LICENSE_FILES = license.rst ifeq ($(ARM_TRUSTED_FIRMWARE_VERSION),custom) # Handle custom ATF tarballs as specified by the configuration @@ -19,6 +17,10 @@ ARM_TRUSTED_FIRMWARE_SITE_METHOD = git else # Handle stable official ATF versions ARM_TRUSTED_FIRMWARE_SITE = $(call github,ARM-software,arm-trusted-firmware,$(ARM_TRUSTED_FIRMWARE_VERSION)) +# The licensing of custom or from-git versions is unknown. +# This is valid only for the official v1.4. +ARM_TRUSTED_FIRMWARE_LICENSE = BSD-3-Clause +ARM_TRUSTED_FIRMWARE_LICENSE_FILES = license.rst endif ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE)$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_LATEST_VERSION),y) diff --git a/buildroot/boot/barebox/barebox.mk b/buildroot/boot/barebox/barebox.mk index 9e8a9f67b..52178d89c 100644 --- a/buildroot/boot/barebox/barebox.mk +++ b/buildroot/boot/barebox/barebox.mk @@ -76,6 +76,10 @@ $(1)_KCONFIG_FRAGMENT_FILES = $$(call qstrip,$$(BR2_TARGET_$(1)_CONFIG_FRAGMENT_ $(1)_KCONFIG_EDITORS = menuconfig xconfig gconfig nconfig $(1)_KCONFIG_OPTS = $$($(1)_MAKE_FLAGS) +$(1)_KCONFIG_DEPENDENCIES = \ + $(BR2_BISON_HOST_DEPENDENCY) \ + $(BR2_FLEX_HOST_DEPENDENCY) + ifeq ($$(BR2_TARGET_$(1)_BAREBOXENV),y) define $(1)_BUILD_BAREBOXENV_CMDS $$(TARGET_CC) $$(TARGET_CFLAGS) $$(TARGET_LDFLAGS) -o $$(@D)/bareboxenv \ diff --git a/buildroot/configs/aarch64_efi_defconfig b/buildroot/configs/aarch64_efi_defconfig index e87193218..2aab6e969 100644 --- a/buildroot/configs/aarch64_efi_defconfig +++ b/buildroot/configs/aarch64_efi_defconfig @@ -13,7 +13,7 @@ BR2_PACKAGE_HOST_GENIMAGE=y # Bootloader BR2_TARGET_GRUB2=y -BR2_TARGET_GRUB2_AARCH64_EFI=y +BR2_TARGET_GRUB2_ARM64_EFI=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y diff --git a/buildroot/configs/beaglebone_defconfig b/buildroot/configs/beaglebone_defconfig index b4f152fd6..fbb259f57 100644 --- a/buildroot/configs/beaglebone_defconfig +++ b/buildroot/configs/beaglebone_defconfig @@ -2,7 +2,6 @@ BR2_arm=y BR2_cortex_a8=y BR2_GLOBAL_PATCH_DIR="board/beaglebone/patches" BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_14=y -BR2_TARGET_GENERIC_GETTY_PORT="ttyO0" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/beaglebone/post-image.sh" BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_GIT=y diff --git a/buildroot/docs/manual/adding-packages-cargo.txt b/buildroot/docs/manual/adding-packages-cargo.txt index b7fc09acf..b6029e1ee 100644 --- a/buildroot/docs/manual/adding-packages-cargo.txt +++ b/buildroot/docs/manual/adding-packages-cargo.txt @@ -17,7 +17,7 @@ The +Config.in+ file of Cargo-based package 'foo' should contain: --------------------------- 01: config BR2_PACKAGE_FOO 02: bool "foo" -03: depends on BR2_PACKAGE_HOST_RUSTC_ARCH_SUPPORTS +03: depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS 04: select BR2_PACKAGE_HOST_CARGO 05: help 06: This is a comment that explains what foo is. diff --git a/buildroot/docs/manual/adding-packages-python.txt b/buildroot/docs/manual/adding-packages-python.txt index 15137cfd6..74e2e78b2 100644 --- a/buildroot/docs/manual/adding-packages-python.txt +++ b/buildroot/docs/manual/adding-packages-python.txt @@ -67,9 +67,13 @@ Python build system, but are not Python modules, can freely choose their name (existing examples in Buildroot are +scons+ and +supervisor+). -In their +Config.in+ file, they should depend on +BR2_PACKAGE_PYTHON+ -so that when Buildroot will enable Python 3 usage for modules, we will -be able to enable Python modules progressively on Python 3. +Packages that are only compatible with one version of Python (as in: +Python 2 or Python 3) should depend on that version explicitely in +their +Config.in+ file (+BR2_PACKAGE_PYTHON+ for Python 2, ++BR2_PACKAGE_PYTHON3+ for Python 3). Packages that are compatible +with both versions should not explicitely depend on them in their ++Config.in+ file, since that condition is already expressed for the +whole "External python modules" menu. The main macro of the Python package infrastructure is +python-package+. It is similar to the +generic-package+ macro. It is diff --git a/buildroot/docs/manual/common-usage.txt b/buildroot/docs/manual/common-usage.txt index e3d7578c8..a36301afd 100644 --- a/buildroot/docs/manual/common-usage.txt +++ b/buildroot/docs/manual/common-usage.txt @@ -310,8 +310,8 @@ installed (+python-matplotlib+ on most distributions), and also the +argparse+ module if you're using a Python version older than 2.7 (+python-argparse+ on most distributions). -Just like for the duration graph, a +BR2_GRAPH_OUT+ environment is -supported to adjust the output file format. See xref:graph-depends[] +Just like for the duration graph, a +BR2_GRAPH_OUT+ environment variable +is supported to adjust the output file format. See xref:graph-depends[] for details about this environment variable. .Note diff --git a/buildroot/docs/manual/configure.txt b/buildroot/docs/manual/configure.txt index 008813c9b..c9eef567f 100644 --- a/buildroot/docs/manual/configure.txt +++ b/buildroot/docs/manual/configure.txt @@ -206,9 +206,9 @@ Buildroot or crosstool-NG. If you want to generate a custom toolchain for your project, that can be used as an external toolchain in Buildroot, our recommendation is -definitely to build it with http://crosstool-ng.org[crosstool-NG]. We -recommend to build the toolchain separately from Buildroot, and then -_import_ it in Buildroot using the external toolchain backend. +to build it either with Buildroot itself (see +xref:build-toolchain-with-buildroot[]) or with +http://crosstool-ng.org[crosstool-NG]. Advantages of this backend: @@ -223,7 +223,53 @@ Drawbacks of this backend: * If your pre-built external toolchain has a bug, may be hard to get a fix from the toolchain vendor, unless you build your external - toolchain by yourself using Crosstool-NG. + toolchain by yourself using Buildroot or Crosstool-NG. + +[[build-toolchain-with-buildroot]] +==== Build an external toolchain with Buildroot + +The Buildroot internal toolchain option can be used to create an +external toolchain. Here are a series of steps to build an internal +toolchain and package it up for reuse by Buildroot itself (or other +projects). + +Create a new Buildroot configuration, with the following details: + +* Select the appropriate *Target options* for your target CPU + architecture + +* In the *Toolchain* menu, keep the default of *Buildroot toolchain* + for *Toolchain type*, and configure your toolchain as desired + +* In the *System configuration* menu, select *None* as the *Init + system* and *none* as */bin/sh* + +* In the *Target packages* menu, disable *BusyBox* + +* In the *Filesystem images* menu, disable *tar the root filesystem* + +Then, we can trigger the build, and also ask Buildroot to generate a +SDK. This will conveniently generate for us a tarball which contains +our toolchain: + +----- +make sdk +----- + +This produces the SDK tarball in +$(O)/images+, with a name similar to ++arm-buildroot-linux-uclibcgnueabi_sdk-buildroot.tar.gz+. Save this +tarball, as it is now the toolchain that you can re-use as an external +toolchain in other Buildroot projects. + +In those other Buildroot projects, in the *Toolchain* menu: + +* Set *Toolchain type* to *External toolchain* + +* Set *Toolchain* to *Custom toolchain* + +* Set *Toolchain origin* to *Toolchain to be downloaded and installed* + +* Set *Toolchain URL* to +file:///path/to/your/sdk/tarball.tar.gz+ ===== External toolchain wrapper diff --git a/buildroot/docs/manual/contribute.txt b/buildroot/docs/manual/contribute.txt index 5530ce154..f339ca50b 100644 --- a/buildroot/docs/manual/contribute.txt +++ b/buildroot/docs/manual/contribute.txt @@ -73,7 +73,7 @@ basically two things that can be done: In the commit message of a patch fixing an autobuild failure, add a reference to the build result directory, as follows: --------------------- -Fixes http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069 +Fixes: http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069 --------------------- === Reviewing and testing patches @@ -402,7 +402,7 @@ the problem is complex, it is OK to add more paragraphs. All paragraphs should be wrapped at 72 characters. A paragraph that explains the root cause of the problem. Again, more -than on paragraph is OK. +than one paragraph is OK. Finally, one or more paragraphs that explain how the problem is solved. Don't hesitate to explain complex solutions in detail. diff --git a/buildroot/docs/manual/manual.html b/buildroot/docs/manual/manual.html index bc5aa774d..615893952 100644 --- a/buildroot/docs/manual/manual.html +++ b/buildroot/docs/manual/manual.html @@ -1,8 +1,8 @@ -The Buildroot user manual

The Buildroot user manual

Table of Contents

I. Getting started
1. About Buildroot
2. System requirements
2.1. Mandatory packages
2.2. Optional packages
3. Getting Buildroot
4. Buildroot quick start
5. Community resources
II. User guide
6. Buildroot configuration
6.1. Cross-compilation toolchain
6.2. /dev management
6.3. init system
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
12.1. Complying with open source licenses
12.2. Complying with the Buildroot license
13. Beyond Buildroot
13.1. Boot the generated images
13.2. Chroot
III. Developer guide
14. How Buildroot works
15. Coding style
15.1. Config.in file
15.2. The .mk file
15.3. The documentation
15.4. Support scripts
16. Adding support for a particular board
17. Adding new packages to Buildroot
17.1. Package directory
17.2. Config files
17.3. The .mk file
17.4. The .hash file
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 Meson-based packages
17.16. Integration of Cargo-based packages
17.17. Infrastructure for Go packages
17.18. Infrastructure for packages building kernel modules
17.19. Infrastructure for asciidoc documents
17.20. Infrastructure specific to the Linux kernel package
17.21. Hooks available in the various build steps
17.22. Gettext integration and interaction with packages
17.23. Tips and tricks
17.24. Conclusion
18. Patching a package
18.1. Providing patches
18.2. How patches are applied
18.3. Format and licensing of the package patches
18.4. Integrating patches found on the Web
19. Download infrastructure
20. Debugging Buildroot
21. Contributing to Buildroot
21.1. Reproducing, analyzing and fixing bugs
21.2. Analyzing and fixing autobuild failures
21.3. Reviewing and testing patches
21.4. Work on items from the TODO list
21.5. Submitting patches
21.6. Reporting issues/bugs or getting help
22. DEVELOPERS file and get-developers
IV. Appendix
23. Makedev syntax documentation
24. Makeusers syntax documentation
25. Migrating from older Buildroot versions
25.1. Migrating to 2016.11
25.2. Migrating to 2017.08

List of Examples

17.1. Config script: divine package
17.2. Config script: imagemagick package:

Buildroot 2019.02.3 manual generated on 2019-06-07 -07:39:11 UTC from git revision 3e8b918b87

The Buildroot manual is written by the Buildroot developers. +The Buildroot user manual

The Buildroot user manual

Table of Contents

I. Getting started
1. About Buildroot
2. System requirements
2.1. Mandatory packages
2.2. Optional packages
3. Getting Buildroot
4. Buildroot quick start
5. Community resources
II. User guide
6. Buildroot configuration
6.1. Cross-compilation toolchain
6.2. /dev management
6.3. init system
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
12.1. Complying with open source licenses
12.2. Complying with the Buildroot license
13. Beyond Buildroot
13.1. Boot the generated images
13.2. Chroot
III. Developer guide
14. How Buildroot works
15. Coding style
15.1. Config.in file
15.2. The .mk file
15.3. The documentation
15.4. Support scripts
16. Adding support for a particular board
17. Adding new packages to Buildroot
17.1. Package directory
17.2. Config files
17.3. The .mk file
17.4. The .hash file
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 Meson-based packages
17.16. Integration of Cargo-based packages
17.17. Infrastructure for Go packages
17.18. Infrastructure for packages building kernel modules
17.19. Infrastructure for asciidoc documents
17.20. Infrastructure specific to the Linux kernel package
17.21. Hooks available in the various build steps
17.22. Gettext integration and interaction with packages
17.23. Tips and tricks
17.24. Conclusion
18. Patching a package
18.1. Providing patches
18.2. How patches are applied
18.3. Format and licensing of the package patches
18.4. Integrating patches found on the Web
19. Download infrastructure
20. Debugging Buildroot
21. Contributing to Buildroot
21.1. Reproducing, analyzing and fixing bugs
21.2. Analyzing and fixing autobuild failures
21.3. Reviewing and testing patches
21.4. Work on items from the TODO list
21.5. Submitting patches
21.6. Reporting issues/bugs or getting help
22. DEVELOPERS file and get-developers
IV. Appendix
23. Makedev syntax documentation
24. Makeusers syntax documentation
25. Migrating from older Buildroot versions
25.1. Migrating to 2016.11
25.2. Migrating to 2017.08

List of Examples

17.1. Config script: divine package
17.2. Config script: imagemagick package:

Buildroot 2019.02.8 manual generated on 2019-12-07 +19:24:18 UTC from git revision aaa1437b11

The Buildroot manual is written by the Buildroot developers. It is licensed under the GNU General Public License, version 2. Refer to the -COPYING +COPYING file in the Buildroot sources for the full text of this license.

Copyright © 2004-2019 The Buildroot developers

logo.png

Part I. Getting started

Chapter 1. About Buildroot

Buildroot is a tool that simplifies and automates the process of building a complete Linux system for an embedded system, using cross-compilation.

In order to achieve this, Buildroot is able to generate a @@ -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.


[1] BSP: Board Support Package

[2] SDK: Software Development Kit

Chapter 2. System requirements

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.


[1] BSP: Board Support Package

[2] SDK: Software Development Kit

Chapter 2. System requirements

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 @@ -142,7 +142,6 @@ utility (including the interface), so you may need to install "development" packages for relevant libraries used by the configuration utilities. Refer to Chapter 2, System requirements for more details, specifically the optional requirements -Section 2.2, “Optional packages” to get the dependencies of your favorite interface.

For each menu entry in the configuration tool, you can find associated help that describes the purpose of the entry. Refer to Chapter 6, Buildroot configuration for details on some specific configuration aspects.

Once everything is configured, the configuration tool generates a @@ -174,15 +173,21 @@ This directory contains several subdirectories:

  • -staging/ which contains a hierarchy similar to a root filesystem - hierarchy. This directory contains the headers and libraries of the - cross-compilation toolchain and all the userspace packages selected - for the target. However, this directory is not intended to be - the root filesystem for the target: it contains a lot of development - files, unstripped binaries and libraries that make it far too big - for an embedded system. These development files are used to compile - libraries and applications for the target that depend on other - libraries. +host/ contains both the tools built for the host, and the sysroot + of the target toolchain. The former is an installation of tools + compiled for the host that are needed for the proper execution of + Buildroot, including the cross-compilation toolchain. The latter + is a hierarchy similar to a root filesystem hierarchy. It contains + the headers and libraries of all user-space packages that provide + and install libraries used by other packages. However, this + directory is not intended to be the root filesystem for the target: + it contains a lot of development files, unstripped binaries and + libraries that make it far too big for an embedded system. These + development files are used to compile libraries and applications for + the target that depend on other libraries. +
  • +staging/ is a symlink to the target toolchain sysroot inside + host/, which exists for backwards compatibility.
  • target/ which contains almost the complete root filesystem for the target: everything needed is present except the device files in @@ -197,10 +202,6 @@ This directory contains several subdirectories:

    • -host/ contains the installation of tools compiled for the host - that are needed for the proper execution of Buildroot, including the - cross-compilation toolchain.

    These commands, make menuconfig|nconfig|gconfig|xconfig and make, are the basic ones that allow to easily and quickly generate images fitting your needs, with all the features and applications you enabled.

    More details about the "make" command usage are given in @@ -272,7 +273,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 @@ -398,9 +399,9 @@ build environment. So even if you are building a system for a x86 or x86_64 target, you have to generate a cross-compilation toolchain with Buildroot or crosstool-NG.

    If you want to generate a custom toolchain for your project, that can be used as an external toolchain in Buildroot, our recommendation is -definitely to build it with crosstool-NG. We -recommend to build the toolchain separately from Buildroot, and then -import it in Buildroot using the external toolchain backend.

    Advantages of this backend:

    • +to build it either with Buildroot itself (see +Section 6.1.3, “Build an external toolchain with Buildroot”) or with +crosstool-NG.

      Advantages of this backend:

      • Allows to use well-known and well-tested cross-compilation toolchains.
      • @@ -410,7 +411,36 @@ Avoids the build time of the cross-compilation toolchain, which is

      Drawbacks of this backend:

      • If your pre-built external toolchain has a bug, may be hard to get a fix from the toolchain vendor, unless you build your external - toolchain by yourself using Crosstool-NG. + toolchain by yourself using Buildroot or Crosstool-NG. +

    6.1.3. Build an external toolchain with Buildroot

    The Buildroot internal toolchain option can be used to create an +external toolchain. Here are a series of steps to build an internal +toolchain and package it up for reuse by Buildroot itself (or other +projects).

    Create a new Buildroot configuration, with the following details:

    • +Select the appropriate Target options for your target CPU + architecture +
    • +In the Toolchain menu, keep the default of Buildroot toolchain + for Toolchain type, and configure your toolchain as desired +
    • +In the System configuration menu, select None as the Init + system and none as /bin/sh +
    • +In the Target packages menu, disable BusyBox +
    • +In the Filesystem images menu, disable tar the root filesystem +

    Then, we can trigger the build, and also ask Buildroot to generate a +SDK. This will conveniently generate for us a tarball which contains +our toolchain:

    make sdk

    This produces the SDK tarball in $(O)/images, with a name similar to +arm-buildroot-linux-uclibcgnueabi_sdk-buildroot.tar.gz. Save this +tarball, as it is now the toolchain that you can re-use as an external +toolchain in other Buildroot projects.

    In those other Buildroot projects, in the Toolchain menu:

    • +Set Toolchain type to External toolchain +
    • +Set Toolchain to Custom toolchain +
    • +Set Toolchain origin to Toolchain to be downloaded and installed +
    • +Set Toolchain URL to file:///path/to/your/sdk/tarball.tar.gz

    External toolchain wrapper

    When using an external toolchain, Buildroot generates a wrapper program, that transparently passes the appropriate options (according to the configuration) to the external toolchain programs. In case you need to @@ -547,7 +577,7 @@ The third solution is systemd. http://www.freedesktop.org/wiki/Software/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)

Chapter 7. Configuration of other components

Before attempting to modify any of the components below, make sure you have already configured Buildroot itself, and have enabled the @@ -715,14 +745,16 @@ depending on the availability of another package.

The easiest way to rebui its build directory in output/build. Buildroot will then re-extract, re-configure, re-compile and re-install this package from scratch. You can ask buildroot to do this with the make <package>-dirclean command.

On the other hand, if you only want to restart the build process of a -package from its compilation step, you can run make -<package>-rebuild, followed by make or make <package>. It will -restart the compilation and installation of the package, but not from -scratch: it basically re-executes make and make install -inside the package, so it will only rebuild files that changed.

If you want to restart the build process of a package from its -configuration step, you can run make <package>-reconfigure, followed -by make or make <package>. It will restart the configuration, -compilation and installation of the package.

Internally, Buildroot creates so-called stamp files to keep track of +package from its compilation step, you can run make <package>-rebuild. It +will restart the compilation and installation of the package, but not from +scratch: it basically re-executes make and make install inside the package, +so it will only rebuild files that changed.

If you want to restart the build process of a package from its configuration +step, you can run make <package>-reconfigure. It will restart the +configuration, compilation and installation of the package.

While <package>-rebuild implies <package>-reinstall and +<package>-reconfigure implies <package>-rebuild, these targets as well +as <package> only act on the said package, and do not trigger re-creating +the root filesystem image. If re-creating the root filesystem in necessary, +one should in addition run make or make all.

Internally, Buildroot creates so-called stamp files to keep track of which build steps have been completed for each package. They are stored in the package build directory, output/build/<package>-<version>/ and are named @@ -900,8 +932,8 @@ the different packages.

To generate these data after a build, run:

This graph-size target requires the Python Matplotlib library to be
 installed (python-matplotlib on most distributions), and also the
 argparse module if you’re using a Python version older than 2.7
-(python-argparse on most distributions).
Just like for the duration graph, a BR2_GRAPH_OUT environment is
-supported to adjust the output file format. See Section 8.8, “Graphing the dependencies between packages”
+(python-argparse on most distributions).
Just like for the duration graph, a BR2_GRAPH_OUT environment variable
+is supported to adjust the output file format. See Section 8.8, “Graphing the dependencies between packages”
 for details about this environment variable.
Note. The collected filesystem size data is only meaningful after a complete
 clean rebuild. Be sure to run make clean all before using make
 graph-size.
To compare the root filesystem size of two different Buildroot compilations,
@@ -1025,8 +1057,7 @@ package
graph-depends
Generate a dependency graph of the package, in the
 context of the current Buildroot configuration. See
-this section
-Section 8.8, “Graphing the dependencies between packages” for more details about dependency
+this section for more details about dependency
 graphs.
graph-rdepends
Generate a graph of this package reverse
   dependencies (i.e the packages that depend on it, directly or
   indirectly)
dirclean
Remove the whole package build directory
reinstall
Re-run the install commands
rebuild
Re-run the compilation commands - this only makes
@@ -1093,7 +1124,11 @@ a local WebKit source tree:
WEBKITGTK_OVERRIDE_SRCDIR = /
 WEBKITGTK_OVERRIDE_SRCDIR_RSYNC_EXCLUSIONS = \
         --exclude JSTests --exclude ManualTests --exclude PerformanceTests \
         --exclude WebDriverTests --exclude WebKitBuild --exclude WebKitLibraries \
-        --exclude WebKit.xcworkspace --exclude Websites --exclude Examples
Chapter 9. Project-specific customization
Typical actions you may need to perform for a given project are:
  • 
+        --exclude WebKit.xcworkspace --exclude Websites --exclude Examples
    By default, Buildroot skips syncing of VCS artifacts (e.g., the .git and
+.svn directories). Some packages prefer to have these VCS directories
+available during build, for example for automatically determining a precise
+commit reference for version information. To undo this built-in filtering at a
+cost of a slower speed, add these directories back:
    LINUX_OVERRIDE_SRCDIR_RSYNC_EXCLUSIONS = --include .git
Chapter 9. Project-specific customization
Typical actions you may need to perform for a given project are:
  • 
 configuring Buildroot (including build options and toolchain,
   bootloader, kernel, package and filesystem image type selection)
 
  • 
@@ -1548,8 +1583,7 @@ such changes from there unless you use an explicit fakeroot from the
 post-build script.
    Instead, Buildroot provides support for so-called permission tables.
 To use this feature, set config option BR2_ROOTFS_DEVICE_TABLE to a
 space-separated list of permission tables, regular text files following
-the makedev syntax
-Chapter 23, Makedev syntax documentation.
    If you are using a static device table (i.e. not using devtmpfs,
+the makedev syntax.
    If you are using a static device table (i.e. not using devtmpfs,
 mdev, or (e)udev) then you can add device nodes using the same
 syntax, in so-called device tables. To use this feature, set config
 option BR2_ROOTFS_STATIC_DEVICE_TABLE to a space-separated list of
@@ -1561,8 +1595,7 @@ related to a specific application, you should set variables
 To cover this requirement, Buildroot provides support for so-called
 users tables. To use this feature, set config option
 BR2_ROOTFS_USERS_TABLES to a space-separated list of users tables,
-regular text files following the makeusers syntax
-Chapter 24, Makeusers syntax documentation.
    As shown in Section 9.1, “Recommended directory structure”, the recommended location for
+regular text files following the makeusers syntax.
    As shown in Section 9.1, “Recommended directory structure”, the recommended location for
 such files is board/<company>/<boardname>/.
    It should be noted that if the custom users are related to a specific
 application, you should set variable FOO_USERS in the package’s .mk
 file instead (see Section 17.5.2, “generic-package reference”).
9.7. Customization after the images have been created
While post-build scripts (Section 9.5, “Customizing the generated target filesystem”) are run before
@@ -2332,8 +2365,7 @@ preferred.
Note that such dependencies will ensure that the dependency opt
 is also enabled, but not necessarily built before your package. To do
 so, the dependency also needs to be expressed in the .mk file of the
 package.
Further formatting details: see the
-coding style
-Section 15.1, “Config.in file”.
17.2.4. Dependencies on target and toolchain options
Many packages depend on certain options of the toolchain: the choice of
+coding style.
17.2.4. Dependencies on target and toolchain options
Many packages depend on certain options of the toolchain: the choice of
 C library, C++ support, thread support, RPC support, wchar support,
 or dynamic library support. Some packages can only be built on certain
 target architectures, or if an MMU is available in the processor.
These dependencies have to be expressed with the appropriate depends
@@ -2483,46 +2515,35 @@ different way, using different infrastructures:
Further formatting details: see the writing
-rules
-Section 15.2, “The .mk file”.
17.4. The .hash file
When possible, you must add a third file, named libfoo.hash, that
+rules.
17.4. The .hash file
When possible, you must add a third file, named libfoo.hash, that
 contains the hashes of the downloaded files for the libfoo
 package. The only reason for not adding a .hash file is when hash
 checking is not possible due to how the package is downloaded.
When a package has a version selection choice, then the hash file may be
@@ -2679,7 +2700,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-config

On line 14, we specify the list of dependencies this package relies
@@ -2766,8 +2787,7 @@ because two builds can never be perfectly simultaneous, and because
   itself use a different mechanism: all files of the form
   *.patch present in the package directory inside
   Buildroot will be applied to the package after extraction (see
-  patching a package
-Chapter 18, Patching a package). Finally, patches listed in
+  patching a package). Finally, patches listed in
   the LIBFOO_PATCH variable are applied before the patches stored
   in the Buildroot package directory.
 
  • 
@@ -3385,16 +3405,19 @@ built.
    • python-<something> in Buildroot. Other packages that use the
 Python build system, but are not Python modules, can freely choose
 their name (existing examples in Buildroot are scons and
-supervisor).
    In their Config.in file, they should depend on BR2_PACKAGE_PYTHON
-so that when Buildroot will enable Python 3 usage for modules, we will
-be able to enable Python modules progressively on Python 3.
    The main macro of the Python package infrastructure is
+supervisor).
    Packages that are only compatible with one version of Python (as in:
+Python 2 or Python 3) should depend on that version explicitely in
+their Config.in file (BR2_PACKAGE_PYTHON for Python 2,
+BR2_PACKAGE_PYTHON3 for Python 3).  Packages that are compatible
+with both versions should not explicitely depend on them in their
+Config.in file, since that condition is already expressed for the
+whole "External python modules" menu.
    The main macro of the Python package infrastructure is
 python-package. It is similar to the generic-package macro. It is
 also possible to create Python host packages with the
 host-python-package macro.
    Just like the generic infrastructure, the Python infrastructure works
 by defining a number of variables before calling the python-package
 or host-python-package macros.
    All the package metadata information variables that exist in the
-generic package infrastructure
-Section 17.5.2, “generic-package reference” also
+generic package infrastructure also
 exist in the Python infrastructure: PYTHON_FOO_VERSION,
 PYTHON_FOO_SOURCE, PYTHON_FOO_PATCH, PYTHON_FOO_SITE,
 PYTHON_FOO_SUBDIR, PYTHON_FOO_DEPENDENCIES, PYTHON_FOO_LICENSE,
@@ -3974,7 +3997,7 @@ user to build programs or libraries written in Rust, but it also downloads and
 manages their dependencies, to ensure repeatable builds. Cargo packages are
 called "crates".
    17.16.1. Cargo-based package’s Config.in file
    The Config.in file of Cargo-based package foo should contain:
    01: config BR2_PACKAGE_FOO
 02:     bool "foo"
-03:     depends on BR2_PACKAGE_HOST_RUSTC_ARCH_SUPPORTS
+03:     depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
 04:     select BR2_PACKAGE_HOST_CARGO
 05:     help
 06:       This is a comment that explains what foo is.
@@ -4017,8 +4040,7 @@ package. Let’s start with an example:
    01: #############
 34:
 35: $(eval $(generic-package))
    The Makefile starts with the definition of the standard variables for package
 declaration (lines 7 to 11).
    As seen in line 35, it is based on the
-generic-package infrastructure
-Section 17.5.1, “generic-package tutorial”. So, it defines
+generic-package infrastructure. So, it defines
 the variables required by this particular infrastructure, where Cargo is
 invoked:
    • 
 FOO_BUILD_CMDS: Cargo is invoked to perform the build. The options required
@@ -4064,8 +4086,7 @@ automatically add a dependency on host-go to such p
 golang-package. It is similar to the generic-package macro. Only
 target packages are supported with golang-package.
      Just like the generic infrastructure, the Go infrastructure works
 by defining a number of variables before calling the golang-package.
      All the package metadata information variables that exist in the
-generic package infrastructure
-Section 17.5.2, “generic-package reference” also
+generic package infrastructure also
 exist in the Go infrastructure: FOO_VERSION, FOO_SOURCE,
 FOO_PATCH, FOO_SITE, FOO_SUBDIR, FOO_DEPENDENCIES,
 FOO_LICENSE, FOO_LICENSE_FILES, FOO_INSTALL_STAGING, etc.
      Note that it is not necessary to add host-go in the
@@ -4139,8 +4160,7 @@ builds a kernel module, and no other component:
      01: #####
 remote URI where to find the package source, licensing information.
      On line 13, we invoke the kernel-module helper infrastructure, that
 generates all the appropriate Makefile rules and variables to build
 that kernel module.
      Finally, on line 14, we invoke the
-generic-package infrastructure
-Section 17.5.1, “generic-package tutorial”.
      The dependency on linux is automatically added, so it is not needed to
+generic-package infrastructure.
      The dependency on linux is automatically added, so it is not needed to
 specify it in FOO_DEPENDENCIES.
      What you may have noticed is that, unlike other package infrastructures,
 we explicitly invoke a second infrastructure. This allows a package to
 build a kernel module, but also, if needed, use any one of other package
@@ -4225,8 +4245,7 @@ text
 
    Although Buildroot only contains one document written in AsciiDoc, there
 is, as for packages, an infrastructure for rendering documents using the
 AsciiDoc syntax.
    Also as for packages, the AsciiDoc infrastructure is available from a
-br2-external tree
-Section 9.2, “Keeping customizations outside of Buildroot”. This allows documentation for
+br2-external tree. This allows documentation for
 a br2-external tree to match the Buildroot documentation, as it will be
 rendered to the same formats and use the same layout and theme.
    17.19.1. asciidoc-document tutorial
    Whereas package infrastructures are suffixed with -package, the document
 infrastructures are suffixed with -document. So, the AsciiDoc infrastructure
@@ -4349,8 +4368,7 @@ Linux tools.
    On line 9, we specify the list of dependencies this tool reli
 dependencies are added to the Linux package dependencies list only when the
 foo tool is selected.
    The rest of the Makefile, lines 11-25 defines what should be done at the
 different steps of the Linux tool build process like for a
-generic package
-Section 17.5.1, “generic-package tutorial”. They will actually be
+generic package. They will actually be
 used only when the foo tool is selected. The only supported commands are
 _BUILD_CMDS, _INSTALL_STAGING_CMDS and _INSTALL_TARGET_CMDS.
    Note. One must not call $(eval $(generic-package)) or any other
 package infrastructure! Linux tools are not packages by themselves,
@@ -4391,8 +4409,7 @@ the Linux kernel tree; this is specific to the linux extension and can
 use the variables defined by the foo package, like: $(FOO_DIR) or
 $(FOO_VERSION)… as well as all the Linux variables, like:
 $(LINUX_VERSION) or $(LINUX_VERSION_PROBED), $(KERNEL_ARCH)…
-See the definition of those kernel variables
-Section 17.18.2, “kernel-module reference”.
    17.21. Hooks available in the various build steps
    The generic infrastructure (and as a result also the derived autotools
+See the definition of those kernel variables.
    17.21. Hooks available in the various build steps
    The generic infrastructure (and as a result also the derived autotools
 and cmake infrastructures) allow packages to specify hooks.
 These define further actions to perform after existing steps.
 Most hooks aren’t really useful for generic packages, since the .mk
@@ -4816,7 +4833,7 @@ Send the fix to the Buildroot mailing list (see
     can be removed.
     In the commit message of a patch fixing an autobuild failure, add a
     reference to the build result directory, as follows:
-
    Fixes http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069
    21.3. Reviewing and testing patches
    With the amount of patches sent to the mailing list each day, the
+
    Fixes: http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069
    21.3. Reviewing and testing patches
    With the amount of patches sent to the mailing list each day, the
 maintainer has a very hard job to judge which patches are ready to apply
 and which ones aren’t. Contributors can greatly help here by reviewing
 and testing these patches.
    In the review process, do not hesitate to respond to patch submissions
@@ -4961,7 +4978,6 @@ options that no longer exist or are no longer needed.
    If you are intereste
 further changes in the packages you added or modified, please add
 yourself to the DEVELOPERS file. This should be done in the same patch
 creating or modifying the package. See the DEVELOPERS file
-Chapter 22, DEVELOPERS file and get-developers
 for more information.
    Buildroot provides a handy tool to check for common coding style
 mistakes on files you created or modified, called check-package (see
 Section 17.23.2, “How to check the coding style” for more information).
    21.5.2. Preparing a patch series
    Starting from the changes committed in your local git view, rebase
@@ -4988,7 +5004,7 @@ large number of commits in the series;
 
  • 
 deep impact of the changes in the rest of the project;
 
  • 
-RFC [4];
+RFC [4];
 
  • 
 whenever you feel it will help presenting your work, your choices,
   the review process, etc.
@@ -5012,7 +5028,7 @@ the problem is complex, it is OK to add more paragraphs. All paragraphs
 should be wrapped at 72 characters.
 
 A paragraph that explains the root cause of the problem. Again, more
-than on paragraph is OK.
+than one paragraph is OK.
 
 Finally, one or more paragraphs that explain how the problem is solved.
 Don't hesitate to explain complex solutions in detail.
@@ -5043,13 +5059,10 @@ can be found under the "Message Id" tag on
 patchwork.  The advantage of
 in-reply-to is that patchwork will automatically mark the previous
 version of the patch as superseded.
    • 21.6. Reporting issues/bugs or getting help
    Before reporting any issue, please check in
-the mailing list archive
-Chapter 5, Community resources whether someone has
+the mailing list archive whether someone has
 already reported and/or fixed a similar problem.
    However you choose to report bugs or get help, either by
-opening a bug in the bug tracker
-Chapter 5, Community resources or by
-sending a mail to the mailing list
-Chapter 5, Community resources, there are
+opening a bug in the bug tracker or by
+sending a mail to the mailing list, there are
 a number of details to provide in order to help people reproduce and
 find a solution to the issue.
    Try to think as if you were trying to help someone else; in
 that case, what would you need?
    Here is a short list of details to provide in such case:
    • 
@@ -5070,7 +5083,7 @@ pastebin service. Note that not all available pastebin services will
 preserve Unix-style line terminators when downloading raw pastes.
 Following pastebin services are known to work correctly:
 - https://gist.github.com/
-- http://code.bulix.org/

    [4] RFC: (Request for comments) change proposal
    Chapter 22. DEVELOPERS file and get-developers
    The main Buildroot directory contains a file named DEVELOPERS that
+- http://code.bulix.org/

    [4] RFC: (Request for comments) change proposal
    Chapter 22. DEVELOPERS file and get-developers
    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-developers tool allows to: