- May 04, 2015
-
-
Peter Korsgaard authored
Fixes: http://autobuild.buildroot.net/results/f2a/f2a43b62aa2a720c538fc60c80c78c8ed5b04dea/ Signed-off-by:
Peter Korsgaard <peter@korsgaard.com>
-
Peter Korsgaard authored
Otherwise we can end up using host includes/libraries if the build host has directfb-config. Fixes: http://autobuild.buildroot.net/results/361/3612b54b0bbc2a55ba6f0febb7be32595b523d96/ Signed-off-by:
-
Peter Korsgaard authored
Like we do for the internal musl backend. We still see a large number of build failures with musl, so warn users about it. Signed-off-by: -
Maxime Hadjinlian authored
We can't take hashes from GitHub, unless the tarball has been uploaded by the maintainer, otherwise it is generated and may change over time, which renders hash files useless. [Peter: slightly reword] Signed-off-by:
Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Signed-off-by:
Yann E. MORIN <yann.morin.1998@free.fr> Cc: Samuel Martin <s.martin49@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by:
Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by:
-
Yann E. MORIN authored
We accept an md5 hash, but only if coming from upstream, and if also accompanied with a stronger hash. Signed-off-by:
-
Arnout Vandecappelle authored
The .la fixup handling looks for paths starting with /usr and assumes that they are missing the installation prefix (i.e. $(STAGING_DIR)). It already handles the cases that $(STAGING_DIR) itself and $(BASE_DIR) are under /usr, but it does not yet handle the case that a pre-installed external toolchain is under /usr (and tracks that fact in some .la file). For instance, if you use buildroot to generate a toolchain with HOST_DIR=/usr/local/some_path, this problem will occur. Fix this in the same way as $(STAGING_DIR) and $(BASE_DIR), but in addition check that TOOLCHAIN_EXTERNAL_INSTALL_DIR is non-empty. For internal toolchains, it is empty and the sed expression would fail. Signed-off-by:
Carlos Soto <csotoalonso@gmail.com> Cc: Carlos Soto <csotoalonso@gmail.com> Reviewed-by:
-
Gustavo Zacarias authored
Fixes: GNUTLS-SA-2015-2 - Fix for MD5 downgrade in TLS 1.2 signatures. Signed-off-by:
Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by:
-
Peter Korsgaard authored
barebox: unbreak custom patch handling after 0eba4759 (packages: apply custom patches using *.patch instead of <pkg>-*.patch) The commit accidently dropped the continuation character (\), breaking the logic. Signed-off-by:
-
Fabio Porcedda authored
Signed-off-by:
Fabio Porcedda <fabio.porcedda@gmail.com> Signed-off-by:
-
Peter Korsgaard authored
And list major additions in 2015.05. Signed-off-by:
-
- May 03, 2015
-
-
Peter Korsgaard authored
Fixes: http://autobuild.buildroot.net/results/b27/b27c4b0822494fb393a5e28b8febd063222bd83f/ http://autobuild.buildroot.net/results/9db/9db2cc9fe6ddfda5663251872fdba00998020fce/ http://autobuild.buildroot.net/results/465/465328d0aa6b5f4b36903e2a4bc41d4ddd343db8/ Signed-off-by:
-
Thomas Petazzoni authored
libfreeimage fails to build on ARC, due to compiler issues: Error: invalid register number `63' This should probably be fixed at the compiler level. It also fails to build on Blackfin, due to numerous libfreeimage issues: 1/ Missing LL suffixes in Source/OpenEXR/IlmImf/ImfFastHuf.cpp. This can be fixed by backporting upstream OpenEXR commit https://github.com/openexr/openexr/commit/57ecf581d053f5cacf2e8fc3c024490e0bbe536f.patch. 2/ Invalid characters in libraw_x3f.cpp. This can be fixed by applying dos2unix on the file. 3/ Usage of too long constants in an unsigned long in dcraw_common.cpp, in code like "id == 0x4434303430" where id is an "unsigned long" i.e 32 bits on 32 bits platform. Due to (3) being apparently unsolved upstream, and causing a build error on Blackfin, we disable libfreeimage on this architecture. However, this code seems so broken that making libfreeimage as entirely broken would maybe be a better option. Fixes: http://autobuild.buildroot.org/results/b33/b3372581c82786cc0a87f8cc2e78f047cc079255/ (ARC issue) http://autobuild.buildroot.org/results/f3b/f3bd6be448cffed3caae7850233168e6d0f6a5bd/ (Blackfin issue) Signed-off-by:Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
-
Thomas Petazzoni authored
Add a patch to fix an x86 build problem caused by invalid register usage when -fPIC is used. Fixes: http://autobuild.buildroot.org/results/fe7/fe72243a84a91b68ef3138847294674b36f16c58/ Signed-off-by:
-
Thomas Petazzoni authored
gdbserver does not build on Blackfin FLAT (undefined reference to `_td_thr_tlsbase') and while it builds on Blackfin FDPIC, it's pretty unlikely that it is going to work properly with the cross-gdb provided by the Analog Devices toolchain: the Analog Devices toolchain provides a 6.6 cross-gdb, while we use gdb 7.8.2 for gdbserver. Therefore, let's simply disable gdb completely for Blackfin. Fixes: http://autobuild.buildroot.org/results/2e5/2e5310d0e869f036ec70b978c62c7bd9d3d2bd70/ Signed-off-by:
-
Bernd Kuhls authored
Also add project URL to Config.in Signed-off-by:
Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by:
-
John Keeping authored
By default libcurl uses the C library's DNS resolver which is synchronous, even if an application is using libcurl's non-blocking mode of operation. Configure libcurl to use c-ares if it is selected so that it can resolve addresses asynchronously if required. [Peter: explicitly disable c-ares support if not enabled] Signed-off-by:
John Keeping <john@keeping.me.uk> Signed-off-by:
-
Romain Naour authored
According to Thomas's remark [1], (e)glibc toolchains provide it's own argp.h version. Also, it appears that argp.h from glibc is more up to date should be preferred to argp-standalone one. [1] http://lists.busybox.net/pipermail/buildroot/2015-May/127511.html Signed-off-by:
Romain Naour <romain.naour@openwide.fr> Signed-off-by:
-
Thomas Petazzoni authored
In static linking scenarios, poppler doesn't find libtiff because it doesn't use pkg-config, so it doesn't know which additional libraries it should link with to test the availability of libtiff. We help poppler in this work by passing a LIBTIFF_LIBS variable, resulting for a pkg-config invocation. Also, since poppler uses pkg-config, we make this dependency explicit in this patch, even though it was already carried by the fontconfig dependency. Fixes: http://autobuild.buildroot.org/results/be7/be78957dd852233c81bd364ddf664564ce8f0208/ Signed-off-by:
-
Thomas Petazzoni authored
When configuring poppler, a shell error occurs: ./configure: line 19741: test: x: unary operator expected This is due to an invalid configure test, which is fixed by a newly added patch. We patch the configure script directly because poppler doesn't autoreconf properly. A patch on configure.ac has been submitted upstream so that hopefully we can drop our patch in a future release of poppler. Signed-off-by:
-
Thomas Petazzoni authored
This commit adds a patch to fix a missing <stdarg.h> include for va_list. Fixes: http://autobuild.buildroot.org/results/9c8/9c828b1da8983577f93bdfae5275fc5122ae874f/ Signed-off-by:
-
Waldemar Brodkorb authored
The Linux kernel does force compile with -m4-nofpu, which is only available when building a multilib toolchain. The interesting part here is, that buildroot use --disable-multilib for gcc configure, but enables --with-multilib-list=m4,m4-nofpu in the default configuration for Qemu targeting r2d emulation. This results in a toolchain, which can be used for the kernel and for userland without creating a multilib toolchain with different kinds of libgcc version. In the multilib case there would be subdirectories created (!m4 and m4-nofpu). As buildroot uses a short version of toolchain creation, a multilib enabled gcc build fails when creating libgcc. So the best solution is to just keep multilib disabled, but always add --with-multilib-list when sh4/sh4eb/sh4a/sh4aeb is choosen. Tested with sh4/sh4a toolchain build and qemu defconfig with gcc 4.8.x/4.9.x (with and without C++ enabled), uClibc and glibc. Disable sh4a/sh4aeb for uClibc, as it does not implemented, yet. Signed-off-by:
Waldemar Brodkorb <wbx@openadk.org> Signed-off-by:
-
-
Thomas Petazzoni authored
If those flags are not explicitly passed, the libecore configure script will include -I/usr/X11R6/include and -L/usr/X11R6/lib in the compile flags, which are obviously unsafe for cross-compilation. The fix is similar to "package/efl/libevas: x-includes and x-libraries must be set for cross-compiling" done by Romain Naour on libecore. Signed-off-by: -
Romain Naour authored
evas_engine_software_xlib_cflags and evas_engine_software_xlib_libs contains unsafe libraries paths if x-include and x-libraries are not set in libevas.mk. config.log: evas_engine_software_xlib_cflags='-I/usr/X11R6/include' evas_engine_software_xlib_libs='-L/usr/X11R6/lib -lX11 -lXext' Fixes: http://autobuild.buildroot.net/results/e5f/e5fb1e62cb634b20233751b4ea3b0630de70e9e0/ Signed-off-by:
-
Marcin Bis authored
cc-tool provides support for Texas Instruments CC Debugger Signed-off-by:
Marcin Bis <marcin@bis.org.pl> Signed-off-by:
-
- May 02, 2015
-
-
-
Floris Bos authored
Set date.timezone in php.ini to match time zone settings. Prevents a warning being logged about it not being set each time a PHP date/time method is used. Signed-off-by:
Floris Bos <bos@je-eigen-domein.nl> Reviewed-by:
-
Floris Bos authored
Remove low-level settings from config.txt like arm_freq and sdram_freq. The defaults should be good for most and differ by Pi model. E.g. the Pi 2 runs at 900 Mhz by default, setting arm_freq=700 like we had previously would underclock it. Add short description in comments to options. Mention initramfs option. Remove obsolete options from cmdline.txt Signed-off-by:
-
Bernd Kuhls authored
strerror_l is not implemented by uClibc. Fixes http://autobuild.buildroot.net/results/ae3/ae31f4585d2c2f850473c446f1ccfba7699c711b/ http://autobuild.buildroot.net/results/504/504cf78a08315e2fc6eaeb9a29ae791972753830/ http://autobuild.buildroot.net/results/092/09280c5d63da9b8b58916c32e6040a98f7ff0ee8/ http://autobuild.buildroot.net/results/da6/da62d97ea060ce03db94f59a91d84a235d03e8f0/ http://autobuild.buildroot.net/results/7a4/7a40f66b3be8cd71a27df04415c4851cd4426cc3/ Signed-off-by:
-
Angelo Compagnucci authored
This patch: * bumps mono version to 4.0.1. * Removes no more needed patches included upstream * Removes profile switches no more present in configure [Thomas: - add Config.in.legacy handling for the removed options. - remove the select that ensured at least one of the .Net runtime version was enabled.] Signed-off-by:Angelo Compagnucci <angelo.compagnucci@gmail.com> Signed-off-by:
-
Angelo Compagnucci authored
This bump is required for proper compiling mono 4.0.1. Signed-off-by:
-
Yann E. MORIN authored
This one is a bit tricky, as the version can come from the linux-headers package, so we must also account for that. We currently have no hash file for linux, but better do the change now, which allows us to later add a hash file. Signed-off-by:
-
Yann E. MORIN authored
Now that custom versions are properly excluded from the list, we can add a hash for the version we package. Signed-off-by:
-
Yann E. MORIN authored
We can safely reference XENOMAI_SOURCE, even though it is defined later, because BR_NO_CHECK_HASH_FOR is a recursively-expanded variable, so its content is only evaluated when the variable is referenced. Signed-off-by:
-
Yann E. MORIN authored
Signed-off-by:
-
Yann E. MORIN authored
As we recently did for U-Boot, disable checking hashes for custom versions of barebox. Note that we currently have no hash file for barebox, but avoiding the check will already be in place when we do add it. Signed-off-by:
-
Yann E. MORIN authored
For custom tarballs, it's quite obvious we can not check hashes. For custom versions, that's not so obvious. One might think we could have hashes for all the official releases, but that's not possible: if the user uses a released version of Buildroot (say 2015.05) much later in the future, and wants to use the then-released 2038.02 U-Boot. It now seems pretty obvious that Buildroot 2015.02 can't know the hash for U-Boot 2038.02. So, disable checking the hash for custom tarballs and custom versions. Signed-off-by:
-
Yann E. MORIN authored
Currently, assigning to BR_NO_CHECK_HASH_FOR but referencing variable assigned to later, fails. Here's a failing test-case, which is the reduced test-case of how we handle BR_NO_CHECK_HASH_FOR for now (warning added for test-case): export BR_NO_CHECK_HASH_FOR BR_NO_CHECK_HASH_FOR += $(XENOMAI_SOURCE) XENOMAI_VERSION = 2.6.4 XENOMAI_SOURCE = xenomai-$(XENOMAI_VERSION).tar.bz2 $(warning BR_NO_CHECK_HASH_FOR='$(BR_NO_CHECK_HASH_FOR)') all: Run it with simply make: $ make BR_NO_CHECK_HASH_FOR=' ' Now, change the first line to read: export BR_NO_CHECK_HASH_FOR = And we now get: $ make BR_NO_CHECK_HASH_FOR=' xenomai-2.6.4.tar.bz2' This new behaviour will be needed later for Xenomai, which handles the version string in an unusual way, so we can exclude its custom versions. Signed-off-by: -
Romain Naour authored
argp-standalone provide libargp.a and argp.h which are never used in libpthsem. Signed-off-by:
-
Peter Korsgaard authored
HOST_CONFIGURE_OPTS is a superset of HOST_MAKE_ENV, so there is no need to pass them both. Also use HOST_CONFIGURE_OPTS for the install step for consistency, and finally, add host-pkgconf to _DEPENDENCIES as it is explicitly used (currently gets pulled in by host-libusb though). Signed-off-by:
-
