aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* arch: remove BR2_ARCH_HAS_ATOMICS optionGravatar Thomas Petazzoni2016-02-0614-45/+0
| | | | | | | | Now that BR2_ARCH_HAS_ATOMICS is no longer used anywhere, we can remove it from arch/Config.in*, as well as from the documentation. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* msgpack: rework BR2_ARCH_HAS_ATOMICS dependencyGravatar Thomas Petazzoni2016-02-062-4/+4
| | | | | | | | | | | | The msgpack source code indeed checks for the 4 bytes __sync built-in, so this commit switches the package from a BR2_ARCH_HAS_ATOMICS dependency to a BR2_TOOLCHAIN_HAS_SYNC_4 dependency. python-msgpack, a reverse dependency of msgpack, is changed in the same way. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* thrift: remove BR2_ARCH_HAS_ATOMICS dependencyGravatar Thomas Petazzoni2016-02-061-2/+0
| | | | | | | | | | | | | | | | | | | | thrift builds perfectly fine on SPARC, which doesn't implement any of the __sync built-ins, so we can get rid of the BR2_ARCH_HAS_ATOMICS dependency. The dependency on atomic operations originated in commit 1aaa14d84f1c920423ed0286b78f64a2b4b2b575 ("thrift: disable for ARC"), but there was no reference to any autobuilder failure. Our testing with an ARC toolchain that doesn't have atomics shows that thrift builds just fine, and code inspection also shows no usage of __sync_*() built-ins. At the time of the commit, the thrift version was 0.9.1, which also did not contain any __sync_*() call. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> [yann.morin.1998@free.fr: build-tested on an ARC toolchain without atomics, with CPU 770D] Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* squid: rework atomic handlingGravatar Thomas Petazzoni2016-02-061-6/+4
| | | | | | | | | | | | | | | | | | | | | squid can use the __sync built-ins when available, but uses an AC_TRY_RUN autoconf tests to check their availability, which isn't compatible with cross-compilation. Due to this, squid.mk is already hinting the configure script about this by passing squid_cv_gnu_atomics=yes/no depending on the availability of atomic operations. So far, squid.mk was assuming that BR2_ARCH_HAS_ATOMICS && BR2_ARCH_IS_64 was needed, since 8 bytes __sync built-ins are used. However, this was a bit too restrictive, since certain 32 bits architectures (ARM, x86) do provide 8 bytes __sync built-ins. So, instead of using BR2_ARCH_HAS_ATOMICS, we now rely on BR2_TOOLCHAIN_HAS_SYNC_4 and BR2_TOOLCHAIN_HAS_SYNC_8, since both 4 bytes and 8 bytes __sync built-ins are tested by the autoconf test. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* cairo, harfbuzz: rework atomic dependenciesGravatar Thomas Petazzoni2016-02-0634-59/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit handles the reverse dependency tree of cairo in terms of atomic dependencies. There are two main changes: - cairo in fact no longer needs atomic operations. It can perfectly build without any __sync built-in, as was tested using an ARC toolchain without atomics, and a SPARC toolchain. Optionally, Cairo can use the __atomic builtins provided by gcc >= 4.7, so support for this is added as well. Thanks to this change, the BR2_ARCH_HAS_ATOMICS dependency is removed from cairo and all its reverse dependencies. - harfbuzz does require the __sync built-in for 4 bytes integers, so we add a dependency on BR2_TOOLCHAIN_HAS_SYNC_4 to harfbuzz and all its reverse dependency, the main one being the pango package. Due to this, the vast majority of gtk-related packages are moved to a dependency on BR2_ARCH_HAS_ATOMICS (which used to be due to cairo) to a dependency on BR2_TOOLCHAIN_HAS_SYNC_4 (due to pango -> harfbuzz). In detail: - cairo Remove BR2_ARCH_HAS_ATOMICS dependency, link against -latomic when gcc >= 4.8 in order to use the __atomic functions. - harfbuzz Add dependency on BR2_TOOLCHAIN_HAS_SYNC_4 - cairomm, gst-plugins-good, gst1-plugins-good, libgdiplus, libsvg-cairo, weston Remove BR2_ARCH_HAS_ATOMICS dependency (since cairo no longer needs atomics) - enlightenment, cwiid, gst-plugins-bad, gst-plugins-base, gst1-plugins-bad, gst1-plugins-base, gtkmm3, libevas-generic-loaders, libfm, libgail, libgtk2, libgtk3, librsvg, openbox, opencv, opencv3, pango, pangomm, pcmanfm, pinentry, rrdtool, webkit, webkitgtk24, xscreensaver Switch from a BR2_ARCH_HAS_ATOMICS dependency to a BR2_TOOLCHAIN_HAS_SYNC_4 (they depend on pango, harfbuzz, gtk, or some other related package) - directfb Remove BR2_ARCH_ATOMICS dependency of the BR2_PACKAGE_DIRECTFB_SVG (since cairo can build without atomics), but add a BR2_TOOLCHAIN_HAS_SYNC_4 dependency on BR2_PACKAGE_DIRECTFB itself since it does use __sync built-ins. This replaces the !BR2_sparc dependency. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* gauche: disable on SPARC(64), remove atomics dependencyGravatar Thomas Petazzoni2016-02-061-4/+1
| | | | | | | | | | | | | | | | | | | | | | gauche does not build on sparc64, it fails with: No rule to make target 'sparc_mach_dep.lo', needed by 'libgc.la' On Sparc, it first fails with the usual "membar" assembler issue which comes from gauche's internal version of libatomic_ops. However, even passing -DAO_NO_SPARC_V9 like we do for libatomic_ops is not sufficient, as we fall into the same build problem as on sparc64. Consequently, this commit disables the gauche package on the sparc and sparc64 architectures. Since it uses its own libatomic_ops copy, and libatomic_ops does not have any dependency on atomic built-ins, we also remove the BR2_ARCH_HAS_ATOMICS dependency. It was originally added to prevent gauche from being built on sparc, but this will no longer happen. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* libtorrent: use the proper BR2_TOOLCHAIN_HAS_SYNC_x symbolsGravatar Thomas Petazzoni2016-02-062-4/+4
| | | | | | | | | | | | | libtorrent uses 1 bytes and 4 bytes __sync built-ins, so let's use the appropriate BR2_TOOLCHAIN_HAS_SYNC_x symbols instead of BR2_ARCH_HAS_ATOMICS. The rtorrent package, which is a reverse dependency of libtorrent, gets fixed as well. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> [yann.morin.1998@free.fr: build-tested on an ARC toolchain without atomics, with CPU 770D] Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* jack2: use the proper BR2_TOOLCHAIN_HAS_SYNC_x symbolGravatar Thomas Petazzoni2016-02-062-3/+4
| | | | | | | | Move away from BR2_ARCH_HAS_ATOMICS and use BR2_TOOLCHAIN_HAS_SYNC_4 instead for the jack2 package and its reverse dependency. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* apache, apr: fix atomic handlingGravatar Thomas Petazzoni2016-02-062-4/+15
| | | | | | | | | | | | | | | | Since the apache package was introduced, --enable-nonportable-atomics=yes was passed when BR2_ARCH_HAS_ATOMICS. However, Apache doesn't take this option: it only passes it down when building the APR library. But since we're building APR separately, this statement had no effect. So this commit removes the useless code from the Apache package, and instead adds the appropriate logic to the apr package, using the new BR2_TOOLCHAIN_HAS_SYNC_x symbols rather than BR2_ARCH_HAS_ATOMICS. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
* pulseaudio: remove BR2_ARCH_HAS_ATOMICS dependencyGravatar Thomas Petazzoni2016-02-067-10/+6
| | | | | | | | | | | | | | | | | | | | | pulseaudio is able to either use the atomic __sync builtins from the compiler, or to rely on libatomic_ops for atomic operations. However, since it anyway selects json-c which requires the __sync built-ins, it means using libatomic_ops is useless: even if you use libatomic_ops for pulseaudio, you'd still get a link error in pulseaudio due to the missing __sync built-in for the json-c library. Also, since pulseaudio now inherits the BR2_TOOLCHAIN_HAS_SYNC_4 from json-c, which matches the __sync built-in from pulseaudio, this commit: - Drops the BR2_ARCH_HAS_ATOMICS dependency - Forces pulseaudio to not detect libatomic_ops - Propagates the removal of BR2_ARCH_HAS_ATOMICS dependency to pulseaudio's reverse dependencies. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* json-c: needs __sync_val_compare_and_swap_4Gravatar Thomas Petazzoni2016-02-0610-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While json-c itself builds fine on platforms that don't provide the __sync atomic built-ins, it does use them. json-c doesn't fail to build because only a library is built, so such function calls are left unresolved. But as soon as it gets used in another package linked in a program, linking will fail due to the missing __sync_val_compare_and_swap_4() function. To fix this, we make json-c depend on BR2_TOOLCHAIN_HAS_SYNC_4, and propagate to the reverse dependencies: - json-c - fastd - pulseaudio - efl - espeak - gst-plugins-good - gst1-plugins-good - mpd - rsyslog - ubus Note that pulseaudio already had a BR2_ARCH_HAS_ATOMICS dependency, which we are keeping for the moment, and will clean-up in a subsequent commit. This commit will also fix packages that could optionally use json-c, and therefore fixes build failures like: http://autobuild.buildroot.org/results/4fe/4feaa9089ee9a183c5086b791bea35c0156945af/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
* docs/manual: document usage of BR2_TOOLCHAIN_HAS_SYNC_xGravatar Thomas Petazzoni2016-02-061-0/+14
| | | | | | | | | | This commit updates the documentation to detail when and how to use the BR2_TOOLCHAIN_HAS_SYNC_x dependency. Note that we chose to not add a comment about this dependency, because it is mainly tied to architecture capabilities (except in very specific cases, which would be way too complicated to explain in a Config.in comment). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* toolchain: add BR2_TOOLCHAIN_HAS_{SYNC_x, ATOMIC} hidden booleansGravatar Thomas Petazzoni2016-02-061-0/+79
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, Buildroot provides one BR2_ARCH_HAS_ATOMICS boolean option to indicate whether the architecture supports atomic operations or not. However, the reality of atomic operations support is much more complicated and requires more than one option to be expressed properly. There are in fact two types of atomic built-ins provided by gcc: (1) The __sync_*() family of functions, which have been in gcc for a long time (probably gcc 4.1). They are available in variants operating on 1-byte, 2-byte, 4-byte and 8-byte integers. Some architectures implement a number of variants, some do not implement any, some implement all of them. They are now considered "legacy" by the gcc developers but are nonetheless still being used by a significant number of userspace libraries and applications. https://gcc.gnu.org/onlinedocs/gcc/_005f_005fsync-Builtins.html (2) The __atomic_*() family of functions, which have been introduced in gcc 4.7. They have been introduced in order to support C++11 atomic operations. In gcc 4.8, they are available on all architectures, either built-in or in the libatomic library part of the gcc runtime (in which case the application needs to be linked with -latomic). In gcc 4.7, the __atomic_*() intrinsics are only supported on certain architectures, since libatomic did not exist at the time. For (1), a single BR2_ARCH_HAS_ATOMICS is not sufficient, because depending on the architecture, some variants may or may not be available. Setting BR2_ARCH_HAS_ATOMICS to false as soon as one of the variant is missing would cause a large number of packages to become unavailable, even if they in fact use only more common variants available on a large number of architectures. For this reason, we've chosen to introduce four new Config.in options: - BR2_TOOLCHAIN_HAS_SYNC_1 - BR2_TOOLCHAIN_HAS_SYNC_2 - BR2_TOOLCHAIN_HAS_SYNC_3 - BR2_TOOLCHAIN_HAS_SYNC_4 Which indicate whether the toolchain support 1-byte, 2-byte, 4-byte and 8-byte __sync_*() built-ins respectively. For (2), we introduce a BR2_TOOLCHAIN_HAS_ATOMIC, which indicates if the __atomic_*() built-ins are available. Note that it is up to the package to link with -latomic when gcc is >= 4.8. Since __atomic_*() intrinsics for all sizes are supported starting We conducted a fairly large analysis about various architectures supported by Buildroot, as well as with a number of different toolchains, to check which combinations support which variant. To do, we linked the following program with various toolchains: int main(void) { uint8_t a; uint16_t b; uint32_t c; uint64_t d; __sync_fetch_and_add(&a, 3); __sync_fetch_and_add(&b, 3); __sync_fetch_and_add(&c, 3); __sync_fetch_and_add(&d, 3); __sync_val_compare_and_swap(&a, 1, 2); __sync_val_compare_and_swap(&b, 1, 2); __sync_val_compare_and_swap(&c, 1, 2); __sync_val_compare_and_swap(&d, 1, 2); __atomic_add_fetch(&a, 3, __ATOMIC_RELAXED); __atomic_add_fetch(&b, 3, __ATOMIC_RELAXED); __atomic_add_fetch(&c, 3, __ATOMIC_RELAXED); __atomic_add_fetch(&d, 3, __ATOMIC_RELAXED); __atomic_compare_exchange_n(&a, &a, 2, 1, __ATOMIC_RELAXED, __ATOMIC_RELAXED); __atomic_compare_exchange_n(&b, &b, 2, 1, __ATOMIC_RELAXED, __ATOMIC_RELAXED); __atomic_compare_exchange_n(&c, &c, 2, 1, __ATOMIC_RELAXED, __ATOMIC_RELAXED); __atomic_compare_exchange_n(&d, &d, 2, 1, __ATOMIC_RELAXED, __ATOMIC_RELAXED); return 0; } And looked at which symbols were unresolved. For the __atomic_*() ones, we tested with and without -latomic to see which variants are built-in, which variants require libatomic. This testing effort has led to the following results: __sync __atomic gcc 1 2 4 8 1 2 4 8 ARC Y Y Y - Y Y Y L 4.8 [with BR2_ARC_ATOMIC_EXT] ARC - - - - L L L L 4.8 [without BR2_ARC_ATOMIC_EXT] ARM Y Y Y X Y Y Y Y 4.8, 4.7 ARM Y Y Y - 4.5 AArch64 Y Y Y Y Y Y Y Y 4.9, 5.1 Bfin - - Y - 4.3 i386 (i386) - - - - L L L L 4.9 i386 (i486..) Y Y Y - L L L L 4.9 [i486, c3, winchip2, winchip-c6] i386 (> i586) Y Y Y Y L L L L 4.9 Microblaze - - Y - L L Y L 4.9 MIPS Y Y Y - Y Y Y L 4.9 MIPS64 Y Y Y Y Y Y Y Y 4.9 NIOS 2 Y Y Y - Y Y Y L 4.9, 5.2 PowerPC Y Y Y - Y Y Y L 4.9 SuperH Y Y Y - Y Y Y L 4.9 SPARC - - - - L L L L 4.9 SPARC64 Y Y Y Y Y Y Y Y 4.9 x86_64 Y Y Y Y Y Y Y Y 4.7, 4.9 Xtensa Y Y Y - Y Y Y Y 4.9 Notes: * __atomic built-ins appeared in gcc 4.7, so for toolchais older than that, the __atomic column is empty. * Y means 'supported built-in' * L means 'supported via linking to libatomic' (only for __atomic functions) * X indicates a very special case for 8 bytes __sync built-ins on ARM. On ARMv7, there is no problem, starting from gcc 4.7, the __sync built-in for 8 bytes integers is implemented, fully in userspace. For cores < ARMv7, doing a 8 bytes atomic operation requires help from the kernel. Unfortunately, the libgcc code implementing this uses the __write() function to display an error, and this function is internal to glibc. Therefore, if you're using glibc everything is fine, but if you're using uClibc or musl, you cannot link an application that uses 8 bytes __sync operations. This has been fixed as part of gcc PR68095, merged in the gcc 5 branch but not yet part of any gcc release. * - means not supported This commit only introduces the new options. Follow-up commits will progressively change the packages using BR2_ARCH_HAS_ATOMICS to use the appropriate BR2_TOOLCHAIN_HAS_SYNC_x or BR2_TOOLCHAIN_HAS_ATOMIC until the point where BR2_ARCH_HAS_ATOMICS can be removed. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* icu: libatomic is only available starting from gcc 4.8Gravatar Thomas Petazzoni2016-02-061-3/+3
| | | | | | | | Fixes: http://autobuild.buildroot.org/results/51b060bbdecdcaac89f764026693bf711e7145d5/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* defconfigs: all use the headers from the kernelGravatar Yann E. MORIN2016-02-0698-257/+118
| | | | | | | | | | | | | | | | | | | | | | | | For most defconfigs, it was trivial to deduce the kernel version, by just reading the version string, which could be: - a standard upstream version string vX.Y.Z - a non-standard version string, but still containg the standard X.Y.Z Those for which it was not so trivial were those hosted on git tree. Since most were already using a custom linux-headers version, it could be easily deduced from that. It was confirmed by browsing said git trees and check the version there. There are a few cases were there was a mismatch: - microzed: uses a 3.18 kernel, but 3.8 headers; fixed. - xilinx_zc706: uses a 3.14 kernel, but 3.8 headers; fixed. - zedboard: uses a 3.18 kernel, but 3.8 headers; fixed. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* linux: drop the option to use the same version as that of the headersGravatar Yann E. MORIN2016-02-063-16/+10
| | | | | | | | | | | | | | It is no longer meaningful, now that we have the option to use the kernel version for the linux headers, as it is more logical and more versatile. Add it to legacy. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* defconfigs: use the new headers-version-same-as-kernel-version optionGravatar Yann E. MORIN2016-02-063-12/+17
| | | | | | | | | | | | | | Now that we can say that the linux headers version should match that of the kernel to be built, we inverse the logic in our defconfigs, as it is more sensible that way. And also because we'll get rid of the former, converse kernel-same-as-headers option. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* bind: fix intermittent build issues with high BR2_JLEVELGravatar Jan Heylen2016-02-061-0/+2
| | | | | | | | | | | | | | | | | | | | | | Build sometimes breaks with: libtool: link: `unix/os.lo' is not a valid libtool object make[3]: *** [rndc-confgen] Error 1 make[3]: *** Waiting for unfinished jobs.... make[4]: Leaving directory `/scratch/peko/build/bind-9.6-ESV-R4/bin/rndc/unix' So disable parallel builds. This patch was removed with commit c36b5d89c5616f7ca0a7295cbb5c231606beb71e by Gustavo Zacarias <gustavo@zacarias.com.ar> but the problem still occurs, so disabling parallel builds again. Fixes: http://autobuild.buildroot.org/results/220/2201f04170ea8ef0961e907efce07c041a57c229/ Signed-off-by: Jan Heylen <heyleke@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* libbsd: upgrade to v0.8.2 and expand architecture supportGravatar Carlos Santos2016-02-053-6/+4
| | | | | | | | | | | | | | | | | | | | When libbsd still supported uClibc as a C library, we added the architecture exclusions because uClibc's a.out.h includes linux/a.out.h. The latter only exists for the specified architectures. However, glibc doesn't include linux/a.out.h, it instead has its own implementation and it adds a flag to indicate if a.out is supported on this architecture or not. Since libbsd currently only supports glibc-based toolchains, the architecture exclusions are no longer valid. On microblaze, the build still fails, but this time because of ELF support. libbsd explicitly handles architectures and microblaze is not one of them (see local-elf.h). Signed-off-by: Carlos Santos <casantos@datacom.ind.br> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package/php: security bump version to 5.6.18Gravatar Bernd Kuhls2016-02-052-2/+2
| | | | | | | Changelog: http://www.php.net/ChangeLog-5.php#5.6.18 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* xdotool: needs MMU supportGravatar Erico Nunes2016-02-051-0/+1
| | | | | | | | | Fixes: http://autobuild.buildroot.net/results/d750919a0d5cfb624937c72253651a431212e238 Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package/mraa: bump version to 0.9.1Gravatar Bernd Kuhls2016-02-053-111/+1
| | | | | | | | | Removed patches applied upstream: https://github.com/intel-iot-devkit/mraa/commit/86a0e10c037e5c069c48012f169f9e8e2587a0ef https://github.com/intel-iot-devkit/mraa/commit/a87a104efeb83d4e762992e5be3b8908e6d2bf40 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* python-psutil: bump to 3.4.2Gravatar Yegor Yefremov2016-02-052-4/+4
| | | | | Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package/rsyslog: fix musl builGravatar Bernd Kuhls2016-02-051-0/+30
| | | | | | | | | | | | The build error was not yet being found by the autobuilders: omfile.c: In function ‘prepareFile’: omfile.c:580:3: error: implicit declaration of function ‘open’ [-Werror=implicit-function-declaration] fd = open((char*) newFileName, O_WRONLY|O_APPEND|O_CREAT|O_NOCTTY|O_CLOEXEC, ^ Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package/lirc-tools: not available on muslGravatar Bernd Kuhls2016-02-051-2/+4
| | | | | | | | | | | | | | | | GLOB_BRACE is not supported by the musl libc: http://www.openwall.com/lists/musl/2013/09/16/1 Upstream correctly rejected the hack proposed by me: http://patchwork.ozlabs.org/patch/576188/ http://sourceforge.net/p/lirc/tickets/174/#b087 Fixes http://autobuild.buildroot.net/results/603/603c4426c47220808305a416f3d60fec2d8c02a3/ http://autobuild.buildroot.net/results/c08/c08abddeb5f0d0d1adec63ab4390562e3cfe1087/ Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package/sconeserver: location support needs host-pkgconfGravatar Bernd Kuhls2016-02-051-1/+1
| | | | | | | Patch suggested by Arnout: http://patchwork.ozlabs.org/patch/576212/ Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* python-setuptools: enable Python 3.x supportGravatar Yegor Yefremov2016-02-051-2/+4
| | | | | | | Add missing XML dependency. Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* uclibc: add a upstream patch to fix vlc runtime issuesGravatar Waldemar Brodkorb2016-02-051-0/+54
| | | | | | | IDN related declaration without implementation is a bad idea. Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* uclibc: fix MIPS builds with disabled threadsGravatar Waldemar Brodkorb2016-02-051-0/+59
| | | | | | | | | | | There was a regression found while building for MIPS with disabled threads. Upstream patch fixed it. Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* toolchain: bump ARC toolchain components to arc-2015.12Gravatar Lada Trimasova2016-02-0514-7/+7
| | | | | | | | | | | | | | | | | | | This change introduces newer ARC toolchain in Buildroot. That new arc-2015.12 release doesn't bring any significant changes but mostly is focused on fixes and minor improvements here and there. Most noticeable changes are: * GCC: Source update to v4.8.5 * GDB: Updated to upstream 7.10 release. You may find more info on fixes and improvements in that release at: https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2015.12 Signed-off-by: Lada Trimasova <ltrimas@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* grep: bump to version 2.23Gravatar Gustavo Zacarias2016-02-052-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* network-manager: bump to version 1.0.10Gravatar Petr Vorel2016-02-052-3/+3
| | | | | Signed-off-by: Petr Vorel <petr.vorel@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* dbus-glib: bump version to 0.106Gravatar Petr Vorel2016-02-052-2/+2
| | | | | Signed-off-by: Petr Vorel <petr.vorel@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* protobuf: introduce BR2_PACKAGE_PROTOBUF_ARCH_SUPPORTSGravatar Thomas Petazzoni2016-02-043-14/+17
| | | | | | | | | | | | | | | | | The architecture dependencies of protobuf are going to change, and they are already duplicated between protobuf, ola and mosh. In order to factorize the expression of those dependencies, this commit introduces BR2_PACKAGE_PROTOBUF_ARCH_SUPPORTS. Note that we include in this hidden Config.in option both the target architecture dependency and the host architecture dependency. Finally, this commit also fixes a real mistake in the mosh Config.in file, where the condition on the architecture dependency for the Config.in comment was inverted: we only want to show the Config.in comment when we are on supported architectures. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* python-cffi: bump to 1.5.0Gravatar Yegor Yefremov2016-02-042-4/+4
| | | | | Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* board: add support for ARM Juno r0 and r1 Development BoardsGravatar Joao Pinto2016-02-043-0/+285
| | | | | | | | | The Juno ARM Development Platform (ADP) is a software development platform for ARMv8-A, it includes the Juno Versatile Express board and an ARMv8-A reference software port available through Linaro. Signed-off-by: Joao Pinto <jpinto@synopsys.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* support/misc: Adding Vagrant file for provisioningGravatar Angelo Compagnucci2016-02-042-0/+74
| | | | | | | | | | | This patch adds a Vagrant file to buildroot. With this file you can provision a complete buildroot developing environment in minutes on all major platforms (Linux/Mac/Windows). [Peter: bump to 2GB RAM, hardcode Buildroot release, add unzip, drop website update and tweak manual text as suggested by Yann] Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* toolchain/external: newer Linaro toolchains do not provide source codeGravatar Yann E. MORIN2016-02-031-3/+3
| | | | | | | | | | | | | | | | Currently, we have a pattern-matching that automatically derives the the source tarball filename from the binary tarball filename. However, the latest Linaro toolchains no longer follow that scheme (and do not even readily provide the sources...). Remove the generic pattern-matching, and explicitly set the source tarball name for those toolchains that do have a source tarball readily available. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Romain Naour <romain.naour@openwide.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* toolchain: copy_toolchain_lib_root: rename LIBSPATH to LIBPATHSGravatar Thomas De Schampheleire2016-02-031-3/+3
| | | | | | | | | | | | | | | | LIBSPATH is populated based on a find with a pattern that can look like: libfoo*.so and thus the output of the find will contain all file paths that match this pattern. Unfortunately, the name LIBSPATH suggests that only one entry is returned, rather than possibly multiple. As this code is quite complex, use the more accurate name LIBPATHS iso LIBSPATH. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* qt5: bump version to 5.5.1Gravatar Peter Seiderer2016-02-0324-243/+41
| | | | | | | | | | | | | | | | | | Reduce hash lists to strongest only (sha256). Remove upstream committed patches (qt5base): - 0004-no-gold-linker-for-host-build.patch (see [1], [2]) - 0007-big_endian-fix_destformat.patch (see [3]) - 0008-QtGui-force-image-dir-in-include_path.patch (see [4], [5]) [1] https://bugreports.qt.io/browse/QTBUG-46125 [2] https://codereview.qt-project.org/#/c/113563/ [3] https://codereview.qt-project.org/#/c/120654/ [4] https://bugreports.qt.io/browse/QTBUG-47400 [5] https://codereview.qt-project.org/#/c/122145/ Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* binutils: fix .loc processing in xtensa gasGravatar Max Filippov2016-02-033-0/+245
| | | | | | | | Fixes: http://autobuild.buildroot.net/results/bff7436a800eeea92c0c92bd2846b0f2b31947fd/ Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* gnutls: bump to version 3.4.9Gravatar Gustavo Zacarias2016-02-032-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* python-pyparted: new packageGravatar Yegor Yefremov2016-02-034-0/+29
| | | | | Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* python-smbus-cffi: new packageGravatar Yegor Yefremov2016-02-034-0/+29
| | | | | | | | [Thomas: - fix license, it's GPLv2, not GPLv2+.] Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* python-cffi: add host variantGravatar Yegor Yefremov2016-02-031-0/+12
| | | | | | | | | | | | | Host variant is needed to cross-compile CFFI based C library wrappers. Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> [Thomas: - add dependency on host-pkgconf for the host package variant. - add various environment variables needed to make pkg-config behave properly when building host-python-cffi. Otherwise, pkg-config returns values that are appropriate to build things for the target, and the build fails.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* python-pycparser: new packageGravatar Yegor Yefremov2016-02-032-0/+17
| | | | | | | | pycparser requires C preprocessor in order to parse C related files, hence available only as host package. Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* libffi: fix headers location for host-libffiGravatar Yegor Yefremov2016-02-031-4/+8
| | | | | | | | | | | | There is a special hook for target-libffi, that moves headers from /usr/lib/libffi-version/include to /usr/include. This patch adds the same procedure for host-libffi. Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> [Thomas: - factorize code between the staging headers cleanup and the host headers cleanup.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* libffi: fix staging headers cleanupGravatar Thomas Petazzoni2016-02-031-1/+1
| | | | | | | | | | | The LIBFFI_MOVE_STAGING_HEADERS function is responsible for moving around libffi headers to a standard location. Once this is done, it removes the no longer used directory, but does so in $(TARGET_DIR) and not $(STAGING_DIR). This directory is already cleaned up in $(TARGET_DIR) in the LIBFFI_REMOVE_TARGET_HEADERS post-install target hook. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* python-netaddr: new packageGravatar Mauro Condarelli2016-02-024-0/+24
| | | | | | | | | | Signed-off-by: Mauro Condarelli <mc5686@mclink.it> Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com> [Thomas: - remove excessive empty new line at the end of Config.in - specify BSD-3c as the license, since it's the variant being used, and it's more specific than just BSD.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* python-mistune: new packageGravatar Mauro Condarelli2016-02-024-0/+25
| | | | | | | | | | | | | | | Signed-off-by: Mauro Condarelli <mc5686@mclink.it> Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com> [Thomas: - rename the .mk file to carry the proper name - rewrap Config.in help text to use the proper length and avoid a trailing space - remove excessive empty new line at the end of Config.in - specify BSD-3c as the license, since it's the variant being used, and it's more specific than just BSD.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>