summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* libupnpp: remove AUTORECONFFabrice Fontaine2019-01-201-2/+0
| | | | | | | | Commit 9b551dacf74445d58aaefef349e2817e009c9d5d removed patch on configure.ac so remove uneeded LIBUPNPP_AUTORECONF Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* libupnpp: fix libupnp dependencyFabrice Fontaine2019-01-201-1/+2
| | | | | | | | | | | Commit 9b551dacf74445d58aaefef349e2817e009c9d5d added support for libupnp18 but without updating LIBUPNPP_DEPENDENCIES Fixes: - http://autobuild.buildroot.org/results/aa734318b9ad318d25e772585c8794429cc0f489 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* odhcp6c: fix build with gcc 8Fabrice Fontaine2019-01-191-0/+28
| | | | | | | | | | Retrieve and backport upstream patch to fix build with gcc 8 Fixes: - http://autobuild.buildroot.org/results/1c6f0d1f2fcd3474af81b3851d875f834a3a0a4f Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/upmpdcli: bump to version 1.4.0Jörg Krause2019-01-192-5/+5
| | | | | | | | | | upmpdcli switched license from GPL-2.0+ to LGPL-2.1+, therefore update the hash file for the license file "COPYING". Note, that upmpdcli depends on libupnpp 0.17.0. Signed-off-by: Jörg Krause <joerg.krause@embedded.rocks> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/libupnpp: bump to version 0.17.0Jörg Krause2019-01-194-40/+4
| | | | | | | | | | libupnpp 0.17.0 adds compatibility for libupnp 1.8. Therefore, we prefer selecting libupnp 1.8 and falling back to libupnp 1.6. Drop patch 0001, which has been merged upstream. Signed-off-by: Jörg Krause <joerg.krause@embedded.rocks> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* python-txtorcon: bump to version 19.0.0Asaf Kahlon2019-01-192-4/+4
| | | | | Signed-off-by: Asaf Kahlon <asafka7@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* python-logbook: bump to version 1.4.3Asaf Kahlon2019-01-192-4/+4
| | | | | Signed-off-by: Asaf Kahlon <asafka7@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* python-bcrypt: bump to version 3.1.6Asaf Kahlon2019-01-192-4/+4
| | | | | Signed-off-by: Asaf Kahlon <asafka7@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* libuv: bump to version 1.25.0Asaf Kahlon2019-01-192-2/+2
| | | | | Signed-off-by: Asaf Kahlon <asafka7@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* unixodbc: needs dynamic libraryFabrice Fontaine2019-01-193-0/+12
| | | | | | | | | Fixes: - http://autobuild.buildroot.org/results/1036ee061ce7f7747d5514c61866da60bcfae769 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [Peter: propagate to PHP_EXT_PDO_UNIXODBC as well] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* php: security bump to 7.3.1Adam Duskett2019-01-192-2/+2
| | | | | | | | | | | | Fixes the following security issue: - CVE-2018-19935: Allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via an empty string in the message argument to the imap_mail function. https://www.cvedetails.com/cve/CVE-2018-19935/ Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* php: switch to pcre2Fabrice Fontaine2019-01-191-2/+2
| | | | | | | | | | | | | | | | php moved from pcre to pcre2 since bump to version 7.3 and http://github.com/php/php-src/commit/a5bc5aed71f7a15f14f33bb31b8e17bf5f327e2d This fixes a build failure: without this change, if BR2_PACKAGE_PCRE is set, external pcre support in php is (wrongly) enabled with --with-pcre-regex but because pcre2 was not found, php fallbacks on built-in pcre2 without the "SLJIT_SINGLE_THREADED hack" Fixes: - http://autobuild.buildroot.org/results/40ef339019203d2cc49d388e222cf17c3ca37944 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Revert "package/php: fix building pcre extension"Fabrice Fontaine2019-01-191-1/+1
| | | | | | | | | | | | | | This reverts commit 745f884e41b5f350296e8448f5fc31d20f67a077. This was the wrong fix: issue is that php moves from pcre to pcre2 since version 7.3.0 and http://github.com/php/php-src/commit/a5bc5aed71f7a15f14f33bb31b8e17bf5f327e2d This patch will always disable external pcre2 support and raise a build failure when toolchaine does not have pthread Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* python-cython: bump to version 0.29.3Asaf Kahlon2019-01-192-4/+4
| | | | | Signed-off-by: Asaf Kahlon <asafka7@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* python-crossbar: bump to version 19.1.2Asaf Kahlon2019-01-192-4/+4
| | | | | Signed-off-by: Asaf Kahlon <asafka7@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* gnu-efi: fix build with gcc 4.8Fabrice Fontaine2019-01-191-0/+35
| | | | | | | | Fixes: - http://autobuild.buildroot.org/results/a0ca37b5ed27af445344e3ac49dc87bb17512c50 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* libgeotiff: bump to version 1.4.3Fabrice Fontaine2019-01-192-2/+2
| | | | | Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* tesseract-ocr: disable documentationFabrice Fontaine2019-01-191-0/+1
| | | | | | | | | Fixes: - http://autobuild.buildroot.org/results/a608e9bfb2b0161c45ae490e2866d96763593723 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Acked-by: Gilles Talis <gilles.talis@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/syslog-ng: fix startup with systemdCarlos Santos2019-01-192-0/+18
| | | | | | | | | | | | By default syslog-ng installs a .service that requires a config file at /etc/default, so provide one with the default values. It's also necessary to enable the service by means of a symlink created at /etc/systemd/system/multi-user.target.wants. Signed-off-by: Carlos Santos <casantos@datacom.com.br> Reviewed-by: Chris Packham <judge.packham@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/pango: add upstream security fix for CVE-2018-15120Peter Korsgaard2019-01-191-0/+38
| | | | | | | | | | | libpango in Pango 1.40.8 through 1.42.3, as used in hexchat and other products, allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via crafted text with invalid Unicode sequences. https://nvd.nist.gov/vuln/detail/CVE-2018-15120 Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/libsndfile: add upstream post-1.0.28 security fixesPeter Korsgaard2019-01-193-0/+171
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes the following security vulnerabilities: CVE-2017-14634: In libsndfile 1.0.28, a divide-by-zero error exists in the function double64_init() in double64.c, which may lead to DoS when playing a crafted audio file CVE-2017-17456: The function d2alaw_array() in alaw.c of libsndfile 1.0.29pre1 may lead to a remote DoS attack (SEGV on unknown address 0x000000000000), a different vulnerability than CVE-2017-14245 CVE-2017-17457: The function d2ulaw_array() in ulaw.c of libsndfile 1.0.29pre1 may lead to a remote DoS attack (SEGV on unknown address 0x000000000000), a different vulnerability than CVE-2017-14246 CVE-2018-13139: A stack-based buffer overflow in psf_memset in common.c in libsndfile 1.0.28 allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted audio file. The vulnerability can be triggered by the executable sndfile-deinterleave CVE-2018-19661: An issue was discovered in libsndfile 1.0.28. There is a buffer over-read in the function i2ulaw_array in ulaw.c that will lead to a denial of service CVE-2018-19662: An issue was discovered in libsndfile 1.0.28. There is a buffer over-read in the function i2alaw_array in alaw.c that will lead to a denial of service Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/asterisk: bump version to 16.1.1Peter Korsgaard2019-01-192-2/+2
| | | | | | | Fixes a regression introduced in 16.1.0: https://issues.asterisk.org/jira/browse/ASTERISK-28222 Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/wireshark: security bump to version 2.6.6Peter Korsgaard2019-01-192-3/+3
| | | | | | | | | | | | | | | | | | | Fixes the following security vulnerabilities: - wnpa-sec-2019-01 The 6LoWPAN dissector could crash. Bug 15217. CVE-2019-5716 https://www.wireshark.org/security/wnpa-sec-2019-01 - wnpa-sec-2019-02 The P_MUL dissector could crash. Bug 15337. CVE-2019-5717 https://www.wireshark.org/security/wnpa-sec-2019-02 - wnpa-sec-2019-03 The RTSE dissector and other dissectors could crash. Bug 15373. CVE-2019-5718 https://www.wireshark.org/security/wnpa-sec-2019-03 - wnpa-sec-2019-04 The ISAKMP dissector could crash. Bug 15374. CVE-2019-5719 https://www.wireshark.org/security/wnpa-sec-2019-04 Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* {linux, linux-headers}: bump 4.{4, 9, 14, 19, 20}.x seriesPeter Korsgaard2019-01-173-11/+11
| | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* libmad: needs autoreconfFabrice Fontaine2019-01-172-5/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | libmad uses a very old configure script. When the toolchain lacks C++ and the build machine lacks /lib/cpp, this old configure script fails because it can't find a C++ preprocessor that is valid: checking for arm-buildroot-linux-uclibcgnueabi-g++... no checking whether we are using the GNU C++ compiler... no checking whether no accepts -g... no checking dependency style of no... none checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. This is yet another case that was tentatively fixed by bd39d11d2e (core/infra: fix build on toolchain without C++), further amended by 4cd1ab15886 (core: alternate solution to disable C++). However, this only works on libtool scripts that are recent enough, and thus we need to autoreconf to get it. We also need to patch configure.ac so that it does not fail on the missing, GNU-specific files: NEWS, AUTHORS, and Changelog. Fixes: - http://autobuild.buildroot.org/results/6a6aa29295bd70679c3a22a149e79010fa20c1bf Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/openvmtools: bump version to 10.3.5Peter Korsgaard2019-01-176-54/+12
| | | | | | | | | | | | | | | | | | | | | | Fixes build against glibc 2.28: closes #11546 http://autobuild.buildroot.net/results/f2c/f2c73480b5a1060bb17ac260ef82c3e641fad085/ http://autobuild.buildroot.net/results/e21/e219b8bacb52bb661eb6663b82f549ed941f26fe/ Use released tarball rather than github helper. The tarball does not contain the open-vm-tools sub directory, so adjust the paths in the patches to match and drop OPENVMTOOLS_SUBDIR. Drop 0001-has_bsd_printf.patch: msgList.c has been removed upstream since: https://github.com/vmware/open-vm-tools/commit/dc81979e78e1b8f42639aeb7aaec69f7ea49eb79 Drop 0004-uclibc_secure_getenv.sh: uClibc-ng provides secure_getenv() since 1.0.22. Renumber remaining patches. Add hash for license file. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/cargo: pass appropriate library path to the linkerThomas Petazzoni2019-01-171-1/+1
| | | | | | | | | | | | | | | | When linking the host cargo binary, the linker should be told to find libraries in $(HOST_DIR)/lib, otherwise it will not work libraries such as libhttp_parser. This was found with per-package directory support, where the build failed with: = note: /usr/bin/ld: cannot find -lhttp_parser collect2: error: ld returned 1 exit status In order to fix this, instead of passing -L$(HOST_DIR)/lib during the build of Cargo, we make sure all flags in $(HOST_LDFLAGS) are passed. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/pkg-meson: support per-package directoriesPeter Seiderer2019-01-172-2/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, package/meson/meson.mk generates a single global cross-compilation.conf file, with the path to the compiler, cflags, ldflags, and various other details. This file is then used when building all meson-based packages. This causes two problems: - It is not compatible with per-package directories, because with per-package folders, we need to use a different compiler, and possibly CFLAGS/LDFLAGS for each package. - It is not possible to define per package CFLAGS. Indeed, when cross-compiling, meson doesn't support passing CFLAGS through the environment, only the CFLAGS from cross-compilation.conf are taken into account. For this reason, this commit: - Introduces a per-package cross-compilation.conf, which is generated by the pkg-meson infrastructure in the "configure" step right before calling meson. The file is generated in $(@D)/build/, and because it is generated within a given package "configure" step, the compiler path is the one of this package. - Keeps the global cross-compilation.conf in $(HOST_DIR)/etc/meson/, for the SDK use-case of Buildroot. Since we want the final and global values of the compiler path, CFLAGS and LDFLAGS, generating this global cross-compilation.conf is moved to a TARGET_FINALIZE_HOOKS. If we were keeping this as a HOST_MESON_POST_INSTALL_HOOKS, it would contain values specific to the host-meson package. For now, we don't yet support per-package CFLAGS/LDFLAGS, but having such per-package cross-compilation.conf is a necessary preparation to achieve this goal. This commit has been tested by building all Buildroot packages that use meson: json-glib, systemd, enlightenment, at-spi2-core, ncmpc, libmpdclient and ncmpc. Signed-off-by: Peter Seiderer <ps.report@gmx.net> [Thomas: - add extended commit log - in pkg-meson.mk, re-use variables defined in meson.mk to do the replacement of CFLAGS/LDFLAGS/CXXFLAGS - move the generation of the global cross-compilation.conf to a TARGET_FINALIZE_HOOKS - testing with per-package folders] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Tested-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Makefile: move definition of TARGET_DIR inside .config conditionThomas Petazzoni2019-01-171-3/+4
| | | | | | | | | | | | | | | | In a follow-up commit introducing per-package directory support, we will need to define TARGET_DIR in a different way depending on the value of a Config.in option. To make this possible, the definition of TARGET_DIR should be moved inside the BR2_HAVE_DOT_CONFIG condition. We have verified that $(TARGET_DIR) is only used within the BR2_HAVE_DOT_CONFIG condition. Outside of this condition, such as in the "clean" target, $(BASE_TARGET_DIR) is used. Suggested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* support/scripts/check-host-rpath: document existing functionsThomas Petazzoni2019-01-171-0/+12
| | | | | | | | | | | As suggested by Arnout Vandecappelle, let's document the elf_needs_rpath() and check_elf_has_rpath() functions, before we make them a bit more complicated with per-package directory support. Suggested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* zbar: bump to version b3b4e32b55f570372fc3af473e51f0a13ee57869Fabrice Fontaine2019-01-172-2/+3
| | | | | | | | | | | | - Add hash for license file - Fix build with kernel headers >= 4.4 with: https://git.linuxtv.org/zbar.git/commit/?id=b3b4e32b55f570372fc3af473e51f0a13ee57869 Fixes: - http://autobuild.buildroot.org/results/630204315eac6e2800bc13c1486a5a525bf9ab37 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* apr: fix runtime tests for cross compilePeter Seiderer2019-01-171-1/+6
| | | | | | | | | | | | | | | | | | | | | | - epoll supported since linux-2.5.44/glibc-2.3.2 (see [1]) - dup3 supported since linux-2.6.27/glibc-2.9 (see [2]) - SOCK_CLOEXEC supported on linux (see [3]) - accept4 suppported since linux-2.6.28/glibc-2.10 (see [4]) Fixes [5] apache runtime failure (#11576) [mpm_event:crit] [pid 173:tid 1996214272] (70023)This function has not been implemented on this platform: AH00495: Couldn't create a Thread Safe Pollset. Is it supported on your platform?Also check system or user limits! [:emerg] [pid 173:tid 1996214272] AH00017: Pre-configuration failed, exiting [1] http://man7.org/linux/man-pages/man7/epoll.7.html [2] https://linux.die.net/man/2/dup3 [4] https://linux.die.net/man/2/accept4 [5] https://bugs.busybox.net/show_bug.cgi?id=11576 Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* nettle: fix build with gcc 4.7Fabrice Fontaine2019-01-171-0/+71
| | | | | | | | Fixes: - http://autobuild.buildroot.org/results/69226d42e9a483aaff44fb3f468b4724415e71f6 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/wavemon: bump to version 0.9.0Jörg Krause2019-01-172-2/+2
| | | | | Signed-off-by: Jörg Krause <joerg.krause@embedded.rocks> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/gst1-plugins-bad: fix build with fdk-aac 2.0Peter Korsgaard2019-01-172-0/+81
| | | | | | | | | | | | | | Fixes: http://autobuild.buildroot.net/results/343/343249ab34ab77be3b8077f544b9d1e2d4852796/ http://autobuild.buildroot.net/results/edc/edca961f2c4d1946385ac86a756308caaf22d79d/ Fdk-aac 2.0 dropped some legacy APIs, breaking the build of the fdk-aac plugin. Add two upstream upstream patches to fix building against fdk-aac 2.0. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Reviewed-by: Ryan Barnett <ryan.barnett@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/llvm: set the path to llvm-configRomain Naour2019-01-171-0/+3
| | | | | | | | | | | | | | | | | | | | While building llvm for the target (x86_64), the build failed due to path poisoning (-I/usr/include/libxml2) while building NATIVE tools (i.e for the host). The llvm package tries to build a tool for the host with the cross-compiler which doesn't work when the paranoid toolchain wrapper (BR2_COMPILER_PARANOID_UNSAFE_PATH) is enabled. We know that llvm (target) needs llvm-tablegen and llvm-config built by host-llvm, but only LLVM_TABLEGEN is provided by llvm.mk. Adding LLVM_CONFIG_PATH=$(HOST_DIR)/bin/llvm-config for llvm (target) fixes the path poisoining issue since llvm doesn't build the NATIVE variant. Signed-off-by: Romain Naour <romain.naour@smile.fr> Cc: Valentin Korenblit <valentinkorenblit@gmail.com> Cc: Matthew Weber <matthew.weber@rockwellcollins.com> Tested-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/libva-utils: drop _SOURCE variable which has the default valueThomas Petazzoni2019-01-171-1/+0
| | | | | | | | | | | | | Since commit b0907949261ef5e8179c027c086903f30417dd66 ("package/libva-utils: bump to version 2.3.0"), the LIBVA_UTILS_SOURCE variable has the default value of the <pkg>_SOURCE variable, so check-package complains: package/libva-utils/libva-utils.mk:8: remove default value of _SOURCE variable (http://nightly.buildroot.org/#generic-package-reference) Let's fix this by dropping the now unneeded variable assignment. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* linux: use HOSTCC_NOCCACHE as kconfig HOSTCCThomas Petazzoni2019-01-161-7/+10
| | | | | | | | | | | | | | | | | | | linux is a bit different than other kconfig-package, because it has "toolchain" in KCONFIG_DEPENDENCIES. Thanks to this, host-ccache *is* ready by the time kconfig invocations are made, so we could use $(HOSTCC) as the host compiler for kconfig related operations. However, for consistency with other kconfig-package packages, we chose to use $(HOSTCC_NOCCACHE) as well. We cannot rely on the default value of HOSTCC passed by the kconfig-package infrastructure, because $(LINUX_MAKE_FLAGS) also contains a HOSTCC definition that would override the one passed by the kconfig-package infrastructure. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* boot/uboot: use HOSTCC_NOCCACHE as kconfig HOSTCCThomas Petazzoni2019-01-161-2/+3
| | | | | | | | | | | | | | | | | At kconfig time, dependencies are not built, and therefore host-ccache is not ready. Due to this, using $(HOSTCC) as the host compiler in KCONFIG_OPTS does not work: a "make uboot-menuconfig" invocation from a clean tree with ccache enabled fails. This commit fixes this by using $(HOSTCC_NOCCACHE). We cannot rely on the default value of HOSTCC passed by the kconfig-package infrastructure, because $(UBOOT_MAKE_OPTS) also contains a HOSTCC definition that would override the one passed by the kconfig-package infrastructure. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/pkg-kconfig: pass HOSTCC during kconfig stepsThomas Petazzoni2019-01-161-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The kconfig build logic uses the HOSTCC variable to find the host compiler. It makes sense to explicitly pass a value to this variable, pointing to the host compiler used by Buildroot. During the kconfig step, host-ccache is not ready (host-ccache is only a dependency to the configure step of packages), so we use $(HOSTCC_NOCCACHE). Packages currently using the kconfig-package fell into two categories: - Those not passing any HOSTCC value. For such packages, it was the default host compiler detected by the kconfig build logic that was used. ccache was therefore never used. With this commit, those packages will now be using the host compiler detected by Buildroot. Packages in this situation: at91bootstrap3, barebox, busybox, swupdate, uclibc, xvisor. - Those passing a HOSTCC value. Such packages were passing $(HOSTCC), which doesn't work as host-ccache will not be ready. This commit does not fix them, as they still override HOSTCC. It will be fixed in followup commits. Packages in this situation: uboot and linux. Note that linux was a bit special, because it has a KCONFIG_DEPENDENCIES on the toolchain package, so in fact host-ccache was ready. So practically speaking, this commit does not fix anything, as the two only problematic packages that use $(HOSTCC) are not fixed. However, it makes things more correct by explicitly telling kconfig which compiler to use. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* infra/pkg-cmake: use an obviously-invalid value for CMAKE_SYSTEM_VERSIONYann E. MORIN2019-01-162-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In 36568732e4, we expanded toolchain.cmake to also define the value for CMAKE_SYSTEM_VERSION, as the cmake documentation states that it must be manually defined when doing cross-compilation [0]: When the CMAKE_SYSTEM_NAME variable is set explicitly to enable cross compiling then the value of CMAKE_SYSTEM_VERSION must also be set explicitly to specify the target system version. However, the fix in 36568732e4 uses the version of the kernel headers, assuming that would be the oldest kernel we could run on. Yet, this is not the case, because glibc (for example) has fallbacks to support running on kernels older than the headers it was built against. The cmake official wiki [1] additionally states: * CMAKE_SYSTEM_VERSION : optional, version of your target system, not used very much. Folllowed a little bit below, by: * CMAKE_TOOLCHAIN_FILE : absolute or relative path to a cmake script which sets up all the toolchain related variables mentioned above For instance for crosscompiling from Linux to Embedded Linux on PowerPC this file could look like this: # this one is important SET(CMAKE_SYSTEM_NAME Linux) #this one not so much SET(CMAKE_SYSTEM_VERSION 1) [...] Furthermore, using the kernel headers version can be a bit misleading (as it really looks like is is the correct version to use when it is not), while it is obvious that 1 is not really the output of `uname -r` and thus is definitely not misleading. Finally, random searches [2] about CMAKE_SYSTEM_VERSION, mostly only turns up issues related with Windows, Mac-OS, and to a lesser extent, Android (where it is forcibly set to 1), with issues realted to running under just Linux (as opposed to Adnroid) mostly non-existent. Consequently, we revert to using the value that is suggested in the cmake WiKi, i.e. 1, and which is basically what we also used as a workaround in the azure-iot-sdk-c paclkage up until d300b1d3b1. A case were we will need to have a real kernel version, is if we one day have a cmake-based pacakge that builds and installs a kernel module [3], because it will need the _running_ kernel version to install it in /lib/modules/VERSION/, but in that case it will anyway most probably not be the headers version. [0] https://cmake.org/cmake/help/v3.8/variable/CMAKE_SYSTEM_VERSION.html [1] https://gitlab.kitware.com/cmake/community/wikis/doc/cmake/CrossCompiling [2] https://duckduckgo.com/?q=CMAKE_SYSTEM_VERSION [3] https://stackoverflow.com/questions/38205745/cmake-system-version-not-updated-for-new-kernel Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Samuel Martin <s.martin49@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* check-package: fix Python3 supportRicardo Martincoski2019-01-166-19/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This script currently uses "/usr/bin/env python" as shebang but it does not really support Python3. Instead of limiting the script to Python2, fix it to support both versions. So change all imports to absolute imports because Python3 follows PEP328 and dropped implicit relative imports. In order to avoid errors when decoding files with the default 'utf-8' codec, use errors="surrogateescape" when opening files, the docs for open() states: "This is useful for processing files in an unknown encoding.". This argument is not compatible with Python2 open() so import 'six' to use it only when running in Python3. As a consequence the file handler becomes explicit, so use it to close() the file after it got processed. This "surrogateescape" is a simple alternative to the complete solution of opening files with "rb" and changing all functions in the lib*.py files to use bytes objects instead of strings. The only case we can have non-ascii/non-utf-8 files being checked by the script are for patch files when the upstream file to be patched is not ascii or utf-8. There is currently one case in the tree: package/urg/0002-urg-gcc6-fix-narrowing-conversion.patch. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Tested-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/supertux: needs gcc >= 6Romain Naour2019-01-161-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The initial build issue [1] has been fixed upstream but the supertux fail to link with boost libraries when using gcc 5 (which use C++11 by default): libsupertux2_lib.a(main.cpp.o): In function `boost::system::error_category::std_category::equivalent(std::error_code const&, int) const': main.cpp:(.text._ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei[_ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei]+0x32): undefined reference to `boost::system::detail::generic_category_instance' main.cpp:(.text._ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei[_ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei]+0x47): undefined reference to `boost::system::detail::generic_category_instance' main.cpp:(.text._ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei[_ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei]+0x99): undefined reference to `boost::system::detail::generic_category_instance' libsupertux2_lib.a(main.cpp.o): In function `boost::system::error_category::std_category::equivalent(int, std::error_condition const&) const': main.cpp:(.text._ZNK5boost6system14error_category12std_category10equivalentEiRKSt15error_condition[_ZNK5boost6system14error_category12std_category10equivalentEiRKSt15error_condition]+0x33): undefined reference to `boost::system::detail::generic_category_instance' main.cpp:(.text._ZNK5boost6system14error_category12std_category10equivalentEiRKSt15error_condition[_ZNK5boost6system14error_category12std_category10equivalentEiRKSt15error_condition]+0x48): undefined reference to `boost::system::detail::generic_category_instance' collect2: error: ld returned 1 exit status This is a similar issue as the one reported by [2]. With gcc 5, boost libraries are compiled using C++11 but supertux2_lib.a is using C++14 standard. To fix the issue, boost libraries should be build using C++14 standard but we currently don't have an option to "force" the default C++ standard used by the compiler. So bump the minimum gcc version to gcc 6 since the C++14 is used by default. [1] https://github.com/SuperTux/supertux/issues/1014 [2] https://github.com/boostorg/system/issues/26 Fixes: http://autobuild.buildroot.net/results/5b4/5b452c155917d783b3d8167fde48c2c938a74b95 Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/libva-utils: bump to version 2.3.0James Hilliard2019-01-162-5/+11
| | | | | | | | Have to add a workaround since upstream didn't package this release properly. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/libva-intel-driver: bump to version 2.3.0James Hilliard2019-01-164-70/+74
| | | | | | | | Remove patch to fix build without stack-protector support which is upstream. Add backported patch to fix libva-intel-driver when using wayland. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/libva: backport Add pointer to struct wl_interface for driver to useJames Hilliard2019-01-161-0/+73
| | | | | | | This is needed by libva-intel-driver when using wayland. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/linux-firmware : Install binary blobs for e100 ethernet driverDavid Picard2019-01-163-0/+12
| | | | | | | | Add an option in the menuconfig submenu of linux-firmware package. Install the firmware binary files to the target directory if the option is selected. Signed-off-by: David Picard <dplamp@gmx.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/cryptsetup: bump to version 2.0.6Baruch Siach2019-01-162-2/+2
| | | | | | Cc: Martin Hicks <mort@bork.org> Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* gnutls: bump to version 3.6.5Fabrice Fontaine2019-01-162-22/+7
| | | | | | | | | | | | | | | | | | | | - libidn1 support removed since version 3.6.0 and https://github.com/gnutls/gnutls/commit/abe6a12b9766219163f99d7807a0b07fbe5f590c - libz support has been removed since version 3.6.0 and https://github.com/gnutls/gnutls/commit/1b3ece44acaa25c149659a6878d2be807a282f02 This bump also fix build issues of gnutls tests and applications such as ffmpeg or cups due to the fact that _idn2_punycode_* functions are not exposed anymore since libidn2 bump to version 2.1.0 and: https://github.com/libidn/libidn2/commit/1d1f2e5babe6032eb0fe4d451afee2e277b8419f Fixes: - http://autobuild.buildroot.org/results/f8c38ea6ebbb78269d620d19d760a0566f742640 - http://autobuild.buildroot.org/results/8dc5b4212b1d8d0bf5bd5e8a27eb02753dc678e4 - http://autobuild.buildroot.org/results/53f5bcd9010c841838f51d65427d9a97ef35e08c Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* nettle: bump to version 3.4.1Fabrice Fontaine2019-01-162-3/+3
| | | | | | | nettle 3.4.1 is a requirement for gnutls 3.6.5 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
OpenPOWER on IntegriCloud