summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* package/alsa-utils: use the new fftw-single packageGwenhael Goavec-Merou2019-02-061-1/+1
| | | | | | | Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/fftw: break fftw-double into a dedicated packageGwenhael Goavec-Merou2019-02-065-16/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fftw's library name depends on the precision option. Consequently, it's possible to install multiple flavor on the same target. This patch breaks fftw double precision into a new package and: - makes BR2_PACKAGE_FFTW_PRECISION_DOUBLE select BR2_PACKAGE_FFTW_DOUBLE to keep compatibility with packages that use BR2_PACKAGE_FFTW_PRECISION_DOUBLE. This option will be removed in a follow-up commit; - removes BR2_PACKAGE_FFTW_USE_SSE2 since it is only used for single and double precision. The corresponding options are directly handled in fftw-double package; - makes fftw depend on fftw-double when this package is enabled; - turns fftw itself into a generic-package instead of an autotools-package: it no longer builds anything and only allows to trigger the build of the appropriate fftw-* sub-packages, as a temporary compatibility mechanism. Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> [Yann/Thomas: - Use FFTW_DOUBLE_DL_SUBDIR to avoid downloading fftw multiple times - Minor reformatting tweaks in fftw-double.mk - Drop from fftw.mk FFTW_CONF_ENV/FFTW_CONF_OPTS which are no longer used - Make fftw a generic package so that its dependencies are built - Do not deprecate BR2_PACKAGE_FFTW_PRECISION_DOUBLE and instead make it select BR2_PACKAGE_FFTW_DOUBLE, so that packages using BR2_PACKAGE_FFTW_PRECISION_QUAD continue to work.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/fftw: break fftw-quad into a dedicated packageGwenhael Goavec-Merou2019-02-065-1/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fftw's library name depends on the precision option. Consequently, it's possible to install multiple flavor on the same target. This patch breaks fftw quad precision into a new package and: - makes BR2_PACKAGE_FFTW_PRECISION_QUAD select BR2_PACKAGE_FFTW_QUAD to keep compatibility with packages that use BR2_PACKAGE_FFTW_PRECISION_QUAD. This option will be removed in a follow-up commit; - makes fftw depend on fftw-quad when this package is enabled. Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> [Yann/Thomas: - Force --disable-quad in FFTW_CONF_OPTS, just for the sake of clarity (fftw is no longer going to build the quad variant) - Use FFTW_QUAD_DL_SUBDIR to avoid downloading fftw multiple times - Minor reformatting tweaks in fftw-quad.mk - Do not deprecate BR2_PACKAGE_FFTW_PRECISION_QUAD and instead make it select BR2_PACKAGE_FFTW_QUAD, so that packages using BR2_PACKAGE_FFTW_PRECISION_QUAD continue to work.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [Gwenhael/Yann]: - (BR2_i386 || BR2_x86_64) -> BR2_TOOLCHAIN_HAS_LIBQUADMATH Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/fftw: break fftw-long-double into a dedicated packageGwenhael Goavec-Merou2019-02-065-1/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | fftw's library name depends on the precision option. Consequently, it's possible to install multiple flavor on the same target. This patch breaks fftw long double precision into a new package and: - makes BR2_PACKAGE_FFTW_PRECISION_LONG_DOUBLE select BR2_PACKAGE_FFTW_LONG_DOUBLE to keep compatibility with packages that use BR2_PACKAGE_FFTW_PRECISION_LONG_DOUBLE. This option will be removed in a follow-up commit; - makes fftw depend on fftw-long-double when this package is enabled. Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> [Yann/Thomas: - Force --disable-long-double in FFTW_CONF_OPTS, just for the sake of clarity (fftw is no longer going to build the long double variant) - Use FFTW_LONG_DOUBLE_DL_SUBDIR to avoid downloading fftw multiple times - Minor reformatting tweaks in fftw-long-double.mk - Do not deprecate BR2_PACKAGE_FFTW_PRECISION_LONG_DOUBLE and instead make it select BR2_PACKAGE_FFTW_LONG_DOUBLE, so that packages using BR2_PACKAGE_FFTW_PRECISION_LONG_DOUBLE continue to work.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/fftw: break fftw-single into a dedicated packageGwenhael Goavec-Merou2019-02-065-15/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fftw's library name depends on the precision option. Consequently, it's possible to install multiple flavor on the same target. This patch breaks fftw single precision into a new package and: - makes BR2_PACKAGE_FFTW_PRECISION_SINGLE select BR2_PACKAGE_FFTW_SINGLE to keep compatibility with packages that use BR2_PACKAGE_FFTW_PRECISION_SINGLE. This option will be removed in a follow-up commit; - removes the BR2_PACKAGE_FFTW_USE_SSE and BR2_PACKAGE_FFTW_USE_NEON otpions since they are only used for single precision. The corresponding CPU-capability options are directly handled in the fftw-single package; - makes fftw depend on fftw-single when this package is enabled. Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> [Yann/Thomas: - Force --disable-single in FFTW_CONF_OPTS, just for the sake of clarity (fftw is no longer going to build the single variant) - Use FFTW_SINGLE_DL_SUBDIR to avoid downloading fftw multiple times - Minor reformatting tweaks in fftw-single.mk - Do not deprecate BR2_PACKAGE_FFTW_PRECISION_SINGLE and instead make it select BR2_PACKAGE_FFTW_SINGLE, so that packages using BR2_PACKAGE_FFTW_PRECISION_SINGLE continue to work.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/fftw: prepare for splitting into multiple packagesThomas Petazzoni2019-02-061-19/+21
| | | | | | | | | | | | In preparation for splitting into multiple packages, this commit changes the fftw.mk package to use FFTW_COMMON_CONF_OPTS, FFTW_COMMON_CONF_ENV and FFTW_COMMON_CFLAGS, which will be re-used by the soon-to-be-introduced per-precision packages. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* testing/tests/download: test git submodulesRicardo Martincoski2019-02-0640-0/+46
| | | | | | | | | | | | | Add two submodules as static repos, add a branch to the main static repo and check on the git refs test case the download of a git package: - repo with submodule but without support in the package; - repo with recursive submodules with support in the package. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@datacom.ind.br> Cc: Arnout Vandecappelle <arnout@mind.be> [Arnout: remove handling of inconsistent tarball hashes - that's an actual bug that should be fixed] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
* support/testing: add docker / docker-compose testsPeter Korsgaard2019-02-054-0/+178
| | | | | | | | | | | | | | Build for x86-64 as public containers in general are only available for x86-64. Docker needs a number of kernel options enabled, so use a custom kernel config based on the qemu one. Docker needs entropy at startup, so enable the virtio-rng-pci device to expose entropy to the guest. The default RAM amount (128M) is not enough to run docker / docker-compose, so bump to 512MB. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Reviewed-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* python-dateutil: bump to version 2.8.0Asaf Kahlon2019-02-052-4/+4
| | | | | Signed-off-by: Asaf Kahlon <asafka7@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/liquid-dsp: drop support for fftw-double and fftw-long-doubleThomas Petazzoni2019-02-051-10/+0
| | | | | | | | | | | | | | liquid-dsp has the following code: So, if it uses the external fftw library, it can only use the fftwf variant, i.e the fftw-single variant. Otherwise, it uses its internal FFT library. There is no way for liquid-dsp to use fftw-double or fftw-long-double. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/pugixml: force-enable 'long long' support to support gcc<4.8Thomas De Schampheleire2019-02-051-0/+6
| | | | | | | | Although pugixml will enable 'long long' support automatically if it detects C++11 (gcc 4.8+), we would like to support older gcc compilers too. Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* support/download/scp: fix download with scheme prefix 'scp://'Thomas De Schampheleire2019-02-051-0/+3
| | | | | | | | | | | | | | | | The scp download helper is broken when the server URL starts with 'scp://'. Such prefix is used in two situations: 1. to let FOO_SITE point to an scp location without explicitly having to set 'FOO_SITE_METHOD = scp' 2. when BR2_PRIMARY_SITE or BR2_BACKUP_SITE points to an scp location. In this case, there is no equivalent of 'SITE_METHOD'. Strip out the scheme prefix, similarly to how the 'file' download helper does it. That helper has the same cases as above. Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/tn5250: remove packagePeter Korsgaard2019-02-057-89/+6
| | | | | | | | | | | | | | The latest (0.17.4) tn5250 release is from 2008, doesn't build with openssl 1.1.x and was dropped from Debian in 2011 because nobody cared to maintain it: https://packages.qa.debian.org/t/tn5250.html Given all of that, it is unlikely to be used much, so remove it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/dovecot: security bump to version 2.3.4.1Peter Korsgaard2019-02-052-2/+2
| | | | | | | | | | | | | | | | | | | | | Fixes the following security issues: * CVE-2019-3814: If imap/pop3/managesieve/submission client has trusted certificate with missing username field (ssl_cert_username_field), under some configurations Dovecot mistakenly trusts the username provided via authentication instead of failing. * ssl_cert_username_field setting was ignored with external SMTP AUTH, because none of the MTAs (Postfix, Exim) currently send the cert_username field. This may have allowed users with trusted certificate to specify any username in the authentication. This bug didn't affect Dovecot's Submission service. For more details, see the announcement: https://www.dovecot.org/list/dovecot-news/2019-February/000394.html Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* utils/check-package: warn about overridden variablesRicardo Martincoski2019-02-053-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For the general case, appending values to variables is OK and also a good practice, like this: |PACKAGE_VAR = value1 |ifeq ... |PACKAGE_VAR += value2 or this, when the above is not possible: |PACKAGE_VAR = value1 |ifeq ... |PACKAGE_VAR := $(PACKAGE_VAR), value2 But this override is an error: |PACKAGE_VAR = value1 |PACKAGE_VAR = value2 as well this one: |ifeq ... |PACKAGE_VAR += value1 |endif |PACKAGE_VAR = value2 And this override is error-prone: |PACKAGE_VAR = value1 |ifeq ... |PACKAGE_VAR = value2 Create a check function to warn about overridden variables. Some variables are likely to have a default value that gets overridden in a conditional, so ignore them. The name of such variables end in _ARCH, _CPU, _SITE, _SOURCE or _VERSION. After ignoring these variable names, there are a few exceptions to this rule in the tree. For them use the comment that disables the check. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Cc: Simon Dawson <spdawson@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Tested-by: Titouan Christophe <titouan.christophe@railnova.eu> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/zbar: bump to version 57d601e82089f2f31de9e1683c3834f237421f5dFabrice Fontaine2019-02-052-2/+2
| | | | | | | | | | | | | | | | | | | | | | When building statically zbar, build fails on: configure: error: unable to find libv4l.so The following errors are raised in config.log: configure:19371: /home/buildroot/buildroot-test/instance-0/output/host/bin/arm-linux-gcc -o conftest -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g2 -static -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -static conftest.c -lv4l2 -lpthread >&5 /home/buildroot/buildroot-test/instance-0/output/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libv4l2.a(libv4l2_la-libv4l2.o): In function `v4l2_set_src_and_dest_format': /home/buildroot/buildroot-test/instance-0/output/build/libv4l-1.16.2/lib/libv4l2/libv4l2.c:952: undefined reference to `v4lconvert_supported_dst_format' To fix this error, bump to version 57d601e82089f2f31de9e1683c3834f237421f5d to replace AC_CHECK_LIB by PKG_CHECK_MODULES to find the correct library (-lv4lconvert but also -ljpeg, ...) Fixes: - http://autobuild.buildroot.org/results/acf39e4754508d7ee49e21f08ff0a1fcac4fb7cd Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/pound: Fix build with OpenSSL 1.1.xBernd Kuhls2019-02-053-1/+475
| | | | | | | | | | | | | | | The patches enable two new API configurations, one for OpenSSL 1.1.x and the other LibreSSL. A dependency is added to use the Buildroot host tool openssl to create headers (dh512.h). This resolves a host OS mismatch with openssl versions. (The Makefile does this generation as part of the initial build) Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Patrick Havelange <patrick.havelange@essensium.com> Signed-off-by: Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* support/testing: test_dropbear.py: drop ssh port forward to the hostPeter Korsgaard2019-02-051-1/+1
| | | | | | | It is not used and may conflict with other services running on port 2222 on the host machine. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* support/testing: test_dropbear.py: add test for ssh connection to localhostPeter Korsgaard2019-02-051-3/+5
| | | | | | Use sshpass to pass the password on the command line. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* support/testing: test_dropbear.py: use a constant for the passwordPeter Korsgaard2019-02-051-3/+4
| | | | | | | The password is used in multiple places, so add a constant for it instead of hardcoding it multiple times. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/ipmitool: add openssl 1.1.x compatibilityMatt Weber2019-02-055-0/+403
| | | | | | | | | | | Changes adapt the current codebase to use supported APIs now that openssl 1.1.x by default disables all deprecated items. Fixes http://autobuild.buildroot.net/results/97d/97dab568f1f3d342b6bfcb9f597ced4de6f1309e Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux: bump Linux CIP to version v4.4.171-cip30Angelo Compagnucci2019-02-052-3/+3
| | | | | | | | This patch bumps the Linux CIP version to v4.4.171-cip30 and updates the download url to the new official one. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/ibrdtnd: include cstringMatt Weber2019-02-051-0/+29
| | | | | | | | | | | | | | Failure output SecurityCertificateManager.lo SecurityCertificateManager.cpp: In static member function 'static void dtn::security::SecurityCertificateManager::validateSubject(X509*, const string&)': SecurityCertificateManager.cpp:208:53: error: 'memcmp' was not declared in this scope if(memcmp(utf8_eid, utf8_cert_name, utf8_eid_len) == 0){ Upstream https://github.com/ibrdtn/ibrdtn/commit/122fa8ed49f896abf6a389505f3d0b66d49d1e77 Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/ibrdtnd: add openssl 1.1.x compatibilityMatt Weber2019-02-051-0/+205
| | | | | | | | | | | Upstream https://github.com/ibrdtn/ibrdtn/pull/265 Fixes http://autobuild.buildroot.net/results/385/3852a414afacbe3c044b1e49be8ccf8c554c8565 Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/softether: bump to v4.28-9669-betaMatt Weber2019-02-054-19/+86
| | | | | | | | | | Source code is now compatible with OpenSSL 1.1.x. Fixes http://autobuild.buildroot.net/results/a6f/a6f1f326ce2525ee0f9d423f1b6d989a89e6b87e/build-end.log Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/tpm2-tss: bump version to 2.1.1Peter Korsgaard2019-02-052-2/+2
| | | | | | | Fixes a number of issues since 2.1.0: https://github.com/tpm2-software/tpm2-tss/releases/tag/2.1.1 Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/mender: fixing init script namingAngelo Compagnucci2019-02-051-2/+2
| | | | | | | | | | | Commit f88947c2fe2d (package/mender: adding systemv init file) added an init script, but the installation logic referred to S04mender instead of S42mender. Update the installation logic to match the file name. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> [Peter: expand commit message description] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/moarvm: resolve libtommath name collisionMatt Weber2019-02-051-0/+65
| | | | | | | | Fixes http://autobuild.buildroot.net/results/02f/02ff68698603ebdce5d13d3130a15b5a1ecc14d2/build-end.log Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Makefile: unexport 'PLATFORM' and 'OS' environment variablesThomas De Schampheleire2019-02-051-0/+2
| | | | | | | | | | | Some package builds may fail when environment variables are present with the same names as make variables in a package. This is a bigger problem for environment variables with generic names, like 'PLATFORM' and 'OS'. 'PLATFORM' is for example a problem for host-acl. Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/qpid-proton: openssl 1.1.x compatibilityMatt Weber2019-02-054-0/+251
| | | | | | | | | | | Updates are based on the original bug report upstream. https://issues.apache.org/jira/browse/PROTON-1326 Fixes http://autobuild.buildroot.net/results/f90/f9085f223cd54c70daf29b12e6c66edb416f7243/ Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/mender: adding a readme fileAngelo Compagnucci2019-02-051-0/+18
| | | | | | | | | This patch adds a readme file with basic instructions to get mender up and running on a production system. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Acked-by: <aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/mender: adding device_type fileAngelo Compagnucci2019-02-052-0/+4
| | | | | | | | | | | | In order to have the mender package working out of the box, the /etc/mender/device_type should be present and should contain a valid device_type value. This patch provides a default file that can be overridden easily from an overlay. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Acked-by: <aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/mender: adding artifact_info fileAngelo Compagnucci2019-02-052-0/+4
| | | | | | | | | | | | In order to have the mender package working out of the box, the /etc/mender/artifact_info should be present and should contain a valid artifact_name value. This patch provides a default file that can be overridden easily from an overlay. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Acked-by: <aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/mender: adding systemv init fileAngelo Compagnucci2019-02-052-0/+61
| | | | | | | | | | This patch adds a service file for the init system v. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Acked-by: <aduskett@gmail.com> Reviewed-by: Titouan Christophe <titouan.christophe@railnova.eu> [Peter: fix typo in stop()] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/mender: adding a writable locationAngelo Compagnucci2019-02-052-1/+13
| | | | | | | | | | | | Mender needs /var/lib/mender to be writable at the service start, the path is hardcoded and thus we cannot change it. This patch solves the problem using the same approach we have for dropbear. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: <aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/netsurf: fix buildPeter Korsgaard2019-02-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes: http://autobuild.buildroot.net/results/a5b/a5bd8969c398fc3101ffaec4aa715a827aec5770/ http://autobuild.buildroot.net/results/441/44112e8ad03f47125bbf4b231d800ebd5beef24b/ After commit 122089ad (package/netsurf: use TMP_PREFIX inside the build directory), the build fails with: COMPILE: src/stylesheet.c In file included from src/stylesheet.c:12:0: src/stylesheet.h:14:39: fatal error: libwapcaplet/libwapcaplet.h: No such file or directory #include <libwapcaplet/libwapcaplet.h> The reason is that netsurf installs its internal libraries to TMP_PREFIX during the build, and uses pkg-config to add the correct include/linker flags when building/linking the rest. Unfortunately this fails badly, as we prefix STAGING_DIR to the paths returned by pkg-config, causing gcc to fail to find the header / library files. This worked (by accident) when we pointed TMP_PREFIX to STAGING_DIR/usr, as STAGING_DIR/usr/include and STAGING_DIR/usr/lib are in the standard include/library search paths. Fix it by adding TMP_PREFIX/include and TMP_PREFIX/lib to the include/library search paths. We cannot easily add them to CFLAGS/LDFLAGS as the makefiles do not use override when appending to them, so instead pass both in CC (which is also used for linking). Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* testing/tests/download: test git branchRicardo Martincoski2019-02-0516-1/+65
| | | | | | | | | | | | | | | | | | Add a branch to the static repo and check on the git refs test case the download of a git package: - with a sha1 reachable by a branch name, but not pointed by it, as version. This is the most common use case for git refs in the tree; - with a partial sha1 of a commit reachable by a branch as version; - with a sha1 of the commit head of a branch as version; - with a partial sha1 of the commit head of a branch as version; Enforce the download always occurs by removing the BR2_DL_DIR used for the tarballs generated by the git download infra. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@datacom.ind.br> Cc: Arnout Vandecappelle <arnout@mind.be> Tested-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
* package/android-tools: Fix build with OpenSSL 1.1.xVadim Kochan2019-02-051-0/+47
| | | | | | | | | | | | | | | | Use patch from: https://github.com/lede-project/source/commit/f63f20fb93c7e67775cb01d97fc88b5b29452b81 which fixes compilation of adb with OpenSSL 1.1.x, and took only part for adb only. Fixes: http://autobuild.buildroot.net/results/66f/66f05eb9a56aa8526a1420334d68c7eda094e90e/ Signed-off-by: Vadim Kochan <vadim4j@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* docs/website/js/buildroot.js: fix unterminated statementsAdam Duskett2019-02-051-3/+3
| | | | | | | | | Some statements are missing their semicolons. Signed-off-by: Adam Duskett <Aduskett@gmail.com> Acked-by: <angelo@amarulasolutions.com> Tested-by: <angelo@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* docs/website/js/buildroot.js: fix possible type coercionAdam Duskett2019-02-051-3/+3
| | | | | | | | | | With javascript, when comparing variables, using === instead of == is preferred. Signed-off-by: Adam Duskett <Aduskett@gmail.com> Acked-by: <angelo@amarulasolutions.com> Tested-by: <angelo@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* docs/website/js/buildroot.js: switch var to letAdam Duskett2019-02-051-20/+20
| | | | | | | | | | In javascript, let is preferred for local, var is preferred for global. Change any local variables from "var" to "let" Signed-off-by: Adam Duskett <Aduskett@gmail.com> Acked-by: <angelo@amarulasolutions.com> Tested-by: <angelo@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/gnu-efi: fix build on armv5Fabrice Fontaine2019-02-051-0/+32
| | | | | | | | | | | Don't override the user-provided ARCH when cross-compiling otherwise ARCH won't be correct for armv5, aarch64 and x86_64 Fixes: - http://autobuild.buildroot.org/results/2dfc0e10da25a8382a43557420d7dc3444c02dbb Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/openmpi: bump to version 4.0.0Fabrice Fontaine2019-02-042-6/+7
| | | | | | | Add hash for licence file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* libopenssl: bump version to 1.1.1aPeter Seiderer2019-02-047-515/+147
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - use BR2_TOOLCHAIN_HAS_UCONTEXT This is used to set -DOPENSSL_NO_ASYNC if needed. - apply the CFLAGS correctly when compiling with -Os (bugfix). - use -latomic when needed This fixes the build for br-sparc-uclibc-2018.05 - don't use madvise() if no MMU Trying to do so results in undefined reference to madvise() as it is not available on uclibc without MMU. The original openssl code checks if a macro used in the madvise call is defined. The problem comes from the fact that the code in crypto/mem_sec.c also includes a kernel header defining the same macro unconditionally. Thus the check is always true in that case. Upstream: https://github.com/openssl/openssl/pull/8089 - don't compile test/fuzzers These binaries introduced with 1.1.x sometimes do not compile. This is the case with the br-arm-cortex-m4-full toolchain - don't build ocsp daemon if no MMU. Patch from Richard Levitte. - correctly enable cryptodev engine Thanks to Arnout Vandecappelle for spotting this. - remove all parallel build patches (openssl build-system changed) - rebased 0001-Dont-waste-time-building-manpages-if-we-re-not-going.patch to apply to Configurations/unix-Makefile.tmpl (Makefile template) - removed 0002-cryptodev-Fix-issue-with-signature-generation.patch (upstream applied) - rebased 0003-Reproducible-build-do-not-leak-compiler-path.patch to apply to crypto/build.info (Makefile template) - fix musl/uclibc build failure, use '-DOPENSSL_NO_ASYNC' - remove legacy enable-tlsext configure option - remove target/host libdir configure options, fixes openssl.pc installation path, fixes wget compile - change legacy INSTALL_PREFIX to DESTDIR - remove 'libraries gets installed read only, so strip fails' workaround (not needed anymore) - change engine directory from /usr/lib/engines to /usr/lib/engines-1.1 - change license file hash, no license change, only the following hint was removed: Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org. Signed-off-by: Peter Seiderer <ps.report@gmx.net> Tested-by: Ryan Coe <bluemrp9@gmail.com> Signed-off-by: Vadim Kochan <vadim4j@gmail.com> Signed-off-by: Patrick Havelange <patrick.havelange@essensium.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* toolchain: add variadic MI thunk support flagMax Filippov2019-02-042-0/+15
| | | | | | | | | | | | | | | | | | | | | | | GCC uses thunk functions to adjust the 'this' pointer when calling C++ member functions in classes derived with multiple inheritance. Generation of thunk functions requires support from the compiler back end. In the absence of that support target-independent code in the C++ front end is used to generate thunk functions, but it does not support vararg functions. Support for this feature is currently missing in or1k and xtensa toolchains. Add hidden option BR2_TOOLCHAIN_SUPPORTS_VARIADIC_MI_THUNK that indicates presence of this feature in the toolchain. Add dependency to packages that require this feature to be built. Fixes: http://autobuild.buildroot.net/results/c9e660c764edbd7cf0ae54ab0f0f412464721446/ http://autobuild.buildroot.net/results/9a3bf4b411c418ea78d59e35d23ba865dd453890/ Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/thrift: bump to 0.12.0, add support for openssl 1.1.xPatrick Havelange2019-02-048-183/+73
| | | | | | | | | | Switching to CMake as the autotools are not crosscompiler compatible. Removed the patches related to autotools as no longer used. Added patch to avoid linker issue. Added license hash. Signed-off-by: Patrick Havelange <patrick.havelange@essensium.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/ffmpeg: fix build with libfdk-aac 2.0.0Bernd Kuhls2019-02-043-0/+271
| | | | | | | | | | | Add upstream patches to fix http://autobuild.buildroot.net/results/909/9097a2b190f4032ff51eda531f4379a99da5181a/ after fdk-aac was bumped to 2.0.0: https://git.buildroot.net/buildroot/commit/package/fdk-aac?id=31ff32824a4f3d09351367c3418b5605f9c40521 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/scripts/setlocalversion: ignore user settings for MercurialThomas De Schampheleire2019-02-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | setlocalversion will use 'hg id' to determine whether or not the current revision is tagged. If there is no tag, the Mercurial revision is printed, otherwise nothing is printed. The problem is that the user may have custom configuration settings (in their ~/.hgrc file or similar) that changes the output of 'hg id' in a way that the script does not expect. In such cases, the Mercurial revision may not be printed or printed incorrectly. It is good practice to ignore the user environment when calling Mercurial commands from a well-defined script, by setting the environment variable HGRCPATH to the empty string. See also 'hg help environment'. In the particular case of Nokia, a custom extension adds dynamic tags in the repository, i.e. tags that are stored in a file external to the repository and only visible when the extension is active. These tags should not influence the behavior of setlocalversion as they are not official Buildroot tags, i.e. even if a revision is tagged, the Mercurial revision should still be printed. Note that this still does not solve the problem where an organization adds _real_ tags in their Buildroot repository. For example, there might be a moving tag 'last-validated' or tags indicating in which product release that Buildroot revision was used. In these cases, setlocalversion will still not behave as expected, i.e. show the Mercurial revision. Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/scripts/setlocalversion: fix detection of hg revision when _not_ on ↵Thomas De Schampheleire2019-02-041-1/+1
| | | | | | | | | | | | | | | | | | | | | branch 'default' When Buildroot is stored in a Mercurial repository on a branch other than 'default' ('master' in git terms), setlocalversion (used to populate /etc/os-release) will incorrectly think that this is a tagged version and will NOT print out the revision hash. This is due to the fact that the output of 'hg id' is assumed to be "<revision> <tags-if-any>" but when on a branch it actually is: "<revision> (<branch>) <tags-if-any>" To let setlocalversion receive the output it expects, explicitly ask 'hg id' to retrieve only the revision hash and any tags, ommitting any branch information. Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/rtmpdump: drop openssl supportPeter Korsgaard2019-02-041-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | Rtmpdump does not support openssl 1.1.x, has not seen any changes upstream since 2015, is only used with the gnutls backend in Debian and Fedora. There exists a 3rd party patch for openssl 1.1.x support: https://github.com/JudgeZarbi/RTMPDump-OpenSSL-1.1 But there is an open issue reported about a crash in the handshake code (which is modified by the patch): https://github.com/JudgeZarbi/RTMPDump-OpenSSL-1.1/issues/1 And the README for the repo states: I modified a few of the files in the librtmp directory to conform to the new getters and setters in OpenSSL 1.1.0. I don't claim to be a security expert, and neither have I had any experience with OpenSSL in a programming sense, so I'm not sure exactly if it's correct, but it compiles and seems to work for what I use it for. Which does not sound very reassuring, so instead drop the openssl support. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
OpenPOWER on IntegriCloud