- Sep 01, 2016
-
-
Peter Korsgaard authored
Signed-off-by:Peter Korsgaard <peter@korsgaard.com>
-
- Aug 31, 2016
-
-
Peter Korsgaard authored
Signed-off-by: -
Peter Korsgaard authored
Signed-off-by: -
Jörg Krause authored
This series includes two patches to fix static linking with libshout. The first patch fixes two typos resulting in an uninterpretable library propagation and is mainly needed for the follow-up patch. The second patch makes sure that `@SHOUT_REQUIRES@` and therefore `Requires.private` includes ssl as `Requires.private` defines a list of private packages required by this package but not exposed to applications. Note that autoreconf is enabled as the first patch touches configure.ac. Fixes: http://autobuild.buildroot.net/results/b82/b82408fccbf816575125dcc1a1de7260f66f62e8/ http://autobuild.buildroot.net/results/360/3605750023267e4cd35d98451bd283f9e70a6106/ http://autobuild.buildroot.net/results/03b/03b98b313dd6ed2909607cdc0c4f6fb87be3ccfe/ http://autobuild.buildroot.net/results/70b/70ba47e04d1fc0d2379bf1ac7aab4c52d6193001/ [Peter: fix libssl .pc reference, fix typo] Signed-off-by:
Jörg Krause <joerg.krause@embedded.rocks> Signed-off-by:
-
Jörg Krause authored
LuaJIT does not have support for MIPS Release 6 [1]. If LuaJIT is invoked with the option `-b -a mips` to save the bytecode for the MIPS architecture it generates object files with the MIPS32 Release 1 instruction set. GCC added support for MIPS32R6 in version 5. However, object files for MIPS32R1 cannot be linked with object for MIPS32R6. That's why building the package luvi fails for MIPS32R6, where object files created with GCC are linked with object files created with LuaJIT with the following linker error: ``` linking mips:isa32 module with previous mips:isa32r6 modules ``` Disable LuaJIT for MIPS32 and MIPS64 R6 to fix the build issue with the luvi package. Fixes: http://autobuild.buildroot.net/results/e01/e017671c33314e5bf2d7fc4920f6c0e64a132383/ http://autobuild.buildroot.net/results/35f/35f558453c45a27367e80e9b8cbe3bd2dccbfd54/ http://autobuild.buildroot.net/results/8e0/8e001112b1678f9fb1c198c84184cd6f5fc3d004/ [1] http://www.freelists.org/post/luajit/Support-for-MIPS32r6,1 Signed-off-by:
-
Thomas Petazzoni authored
As reported in bug #8206, the mplayer configure script fails to detect the availability of X11 header/library if the X.org development packages are not installed on the build machine. This is due to the logic used by the mplayer configure script, which looks like this: for I in $(echo $extra_cflags | sed s/-I//g) /usr/include ; do if test -f "$I/X11/Xlib.h" ; then _x11_headers="yes" So, in other words, it: 1/ Parses the --extra-cflags option, and finds the -I options in there. 2/ Looks in /usr/include Since $(STAGING_DIR)/usr/include is in the compiler built-in search path for headers, we currently don't explicitly pass it in --extra-cflags, so mplayer only looks in /usr/include. If you have X11 headers there thanks to being installed on your build machine, everything works fine (the rest of the build logic really uses the headers and libraries of the cross-compiler). But if you don't have X11 headers in /usr/include, the configure scripts assumes X11 is not available. Since fixing the hand-written configure script of mplayer, hosted in a Subversion repository, is beyond sanity, we simply work around this problem by passing the appropriate -I$(STAGING_DIR)/usr/include option in --extra-cflags. Before this patch, during the configure script: Checking for X11 headers presence ... no (check if the dev(el) packages are installed) Checking for X11 ... no (check if the dev(el) packages are installed) And then, the mplayer binary: 0x00000001 (NEEDED) Shared library: [librt.so.0] 0x00000001 (NEEDED) Shared library: [libz.so.1] 0x00000001 (NEEDED) Shared library: [libpthread.so.0] 0x00000001 (NEEDED) Shared library: [libdl.so.0] 0x00000001 (NEEDED) Shared library: [libm.so.0] 0x00000001 (NEEDED) Shared library: [libc.so.0] With this patch, during the configure script: Checking for X11 headers presence ... yes Checking for X11 ... yes And then, the mplayer binary: 0x00000001 (NEEDED) Shared library: [librt.so.0] 0x00000001 (NEEDED) Shared library: [libz.so.1] 0x00000001 (NEEDED) Shared library: [libpthread.so.0] 0x00000001 (NEEDED) Shared library: [libdl.so.0] 0x00000001 (NEEDED) Shared library: [libm.so.0] 0x00000001 (NEEDED) Shared library: [libXext.so.6] 0x00000001 (NEEDED) Shared library: [libX11.so.6] 0x00000001 (NEEDED) Shared library: [libXinerama.so.1] 0x00000001 (NEEDED) Shared library: [libXxf86vm.so.1] 0x00000001 (NEEDED) Shared library: [libc.so.0] Fixes bug #8206 Signed-off-by:Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
-
Zakharov Vlad authored
As described at: 4520524b this commit continues a series of updates of ARC tools. This time we're updating tools to arc-2016.09-eng010. This engenering build contains different fixes done to TLS and PIE features. Appropriate custom patches are removed as they have been added to eng010. We still keep GDB as it is of arc-2016.03 release because there're some issues we'd like to resolve before releasing it to wider audience. So again note this is next engineering builds of arc-2016.09 series and it might have all kinds of breakages, please don't use it for production builds. Signed-off-by:
Vlad Zakharov <vzakhar@synopsys.com> Signed-off-by:
-
- Aug 30, 2016
-
-
Peter Korsgaard authored
Signed-off-by:
-
- Aug 29, 2016
-
-
Masahiro Yamada authored
The recent U-Boot adopts Kconfig for its configuration system. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by:
Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by:
-
Thomas Petazzoni authored
This commit adds a simple patch to the libaio build system that allows it to be used on static-only configurations. It is probably easier to fix this than to propagate the !BR2_STATIC_LIBS dependency. Fixes: http://autobuild.buildroot.net/results/8c86402bd14a0af1b82e6e07c06531a856dd37c6/ Signed-off-by:
Romain Naour <romain.naour@gmail.com> Tested-by:
-
Thomas Petazzoni authored
GMane is dead (at least its web interface), so it's no longer really useful to reference it. Signed-off-by:
-
Peter Korsgaard authored
Fixes: http://autobuild.buildroot.org/results/349/349bc8668614b0f2c970ff33f25216e708ecdb46/ http://autobuild.buildroot.org/results/264/26486e88211d01ee49ad786e9a27a67b849ad1ab/ Older toolchains contain an issue with the linker script causing failures when linking tftpd: tftpd.c:(.text.startup+0x5c): warning: Unable to reach (null) (at 0x00000000) from the global pointer (at 0x00011a80) because the offset (-72320) is out of the allowed range, -32678 to 32767. This is a known issue which has been fixed from 6.x, so disallow on older toolchains: https://www.altera.com/support/support-resources/knowledge-base/solutions/rd02132012_291.html Signed-off-by:
-
Bernd Kuhls authored
After fixing the usual sys/cdefs.h and _P stuff the build still fails because Openswan makes use of GLOB_ functions /home/bernd/buildroot/br4/output/build/openswan-2.6.48/lib/libipsecconf/parser.l:200:29: error: ‘GLOB_BRACE’ undeclared (first use in this function) globresult = glob(try, GLOB_BRACE, NULL, &globbuf); ^ /home/bernd/buildroot/br4/output/build/openswan-2.6.48/lib/libipsecconf/parser.l:200:29: note: each undeclared identifier is reported only once for each function it appears in /home/bernd/buildroot/br4/output/build/openswan-2.6.48/lib/libipsecconf/parser.l:207:41: error: ‘GLOB_NOMAGIC’ undeclared (first use in this function) globresult = glob(try, GLOB_BRACE|GLOB_NOMAGIC, NULL, &globbuf); https://github.com/xelerance/Openswan/blob/master/lib/libipsecconf/parser.l#L200 https://github.com/xelerance/Openswan/blob/master/lib/libipsecconf/parser.l#L207 [...] ^ which musl does not support: http://www.openwall.com/lists/musl/2013/09/16/1 Fixes http://autobuild.buildroot.net/results/70d/70da34c1528b51e92e9e60788f83733d70b33353/ Signed-off-by:Bernd Kuhls <bernd.kuhls@t-online.de> Acked-by:
"Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by:
-
Paul Cercueil authored
IIOD uses accept4, which is not yet available on Blackfin. Fixes: http://autobuild.buildroot.net/results/b75/b7552c9325ffcc7f1cb6e114b82648f3280fded6/ [Peter: hide other toolchain comment on bfin] Signed-off-by:
Paul Cercueil <paul.cercueil@analog.com> Signed-off-by:
-
Fabrice Fontaine authored
Fixes: http://autobuild.buildroot.net/results/928be69f90476e6b04be3a1afd3b74112bcac0a0 As mentioned in sha2/README, by default, tinydtls uses u_intXX_t data types for 8 bit, 32 bit, and 64 bit unsigned integer type definitions. To use uintXX_t data types as defined by recent ANSI C standards and as included in the inttypes.h header file, SHA2_USE_INTTYPES_H has to be define at compile time. [Peter: reword/simplify] Signed-off-by:
Fabrice Fontaine <fabrice.fontaine@orange.com> Signed-off-by:
-
Gustavo Zacarias authored
Signed-off-by:
Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by:
-
Paul Cercueil authored
When compiling with a toolchain targetted at ucLinux, libserialport's configure.ac would fail at detecting the target operating system. As a result, the Linux-specific files were not compiled in that particular case. While this commit does not fix any autobuider failure for this package, it fixes autobuilder failures for other packages, for instance: http://autobuild.buildroot.net/results/69e/69e43bc171e554cf10f2ad526cebf5e0e524538a/ Signed-off-by:
-
Yann E. MORIN authored
Currently, we forcibly tell neon's configure where to look for libexpat. This means that neon does not search for it, and consequently forgets to add -lexpat as its Libs.Private in its .pc file. As thus, a static link against neon forgets to pull in -lexpat (it works for a dynamic link because libneon has a NEEDED on libexpat). The reason for specifying the explicit path in this case is lost to history; neon's configure can correctly find libexpat nowadays. Fixes: http://autobuild.buildroot.org/results/884/884746351fc47f4ad19fb3fda7c5e0ee85fcff15/ http://autobuild.buildroot.org/results/0c5/0c584522c26640e29980150a87a5b5d8c02e5f8b/ Signed-off-by: -
Yann E. MORIN authored
Like in cbe01f67, 38249d56, 97fe953b, fix C++11 compliance regarding narrowing types. Fixes: http://autobuild.buildroot.org/results/081/0811531872f69f9febbdc482dfbdd7fb5c35d1c8/ http://autobuild.buildroot.org/results/90c/90c9cb4ffe705b8c91f4fb602e33e2ba9bcdee77/ and a few others... [Peter: use signed char for src[], fix dos/unix new lines] Signed-off-by:
-
Yann E. MORIN authored
sconeserver wants to use dlopen(), unconditionally: it does not try to detect it, and it can't work without it (the code is not conditional). Fixes: http://autobuild.buildroot.org/results/e92/e929799366e6f574c7b08d8635b18623afd3e3e1/ [Peter: drop uClibc dependency, adjust commit message] Reported-by:Matthew Weber <matt@thewebers.ws> Signed-off-by:
-
- Aug 28, 2016
-
-
Yann E. MORIN authored
sconeserver uses pkg-config macros and uses autoreconf, so it unconditionally needs host-pkgconf. [Peter: drop host-pkgconf from sub options, update description] Reported-by:
-
Thomas Petazzoni authored
The android-tools code is somewhat ugly, and defines its own u64 typedef becore including kernel headers. Unfortunately, there are specific cases where that doesn't work properly. The android-tools code defines u64 as "unsigned long long", which is now correct in the kernel. However, it used to be a time where u64 was defined as "unsigned long" on a few 64 bits architecture (at least PowerPC64 and MIPS64). The kernel headers have introduced a __SANE_USERSPACE_TYPES__ macro that userspace can define in order to get the "sane" definition, i.e "unsigned long long" for u64. Unfortunately, this __SANE_USERSPACE_TYPES__ mechanism only appeared in 3.10 on PowerPC64, and in 3.16 on MIPS64. Since android-tools is not using the autotools, and there's no easy way to test types with the C pre-processor, we simply add some more Config.in dependencies. They are a bit convoluted, but that's what the dependency really is. In our autobuilders, this issue was only showing up with an old MIPS64 toolchain that uses 3.9 kernel headers. Also, since the problem is limited to the "fastboot" tool, the dependency is only added for fastboot. Both adb and adbd build fine with this toolchain. Fixes: http://autobuild.buildroot.net/results/ce45c995bd6abda6487ae3a11b4f45a7b9b3f8eb/ Signed-off-by:
-
Thomas Petazzoni authored
This commit adds a patch to the libamcodec in order to fix the build with musl, which was failing due to missing <stdint.h> includes. Fixes: http://autobuild.buildroot.net/results/1f3b0d483603fb69765c15c7189ff975b72d09c3/ Signed-off-by:
-
Thomas Petazzoni authored
Since the bump to libiio 0.7, the systemd service file that used to be in debian/iiod.service no longer exists. The entire debian/ directory has been removed from the upstream project: https://github.com/analogdevicesinc/libiio/commit/5d49f58982b0c15545bc70724304fbc580e6523c Due to this, the installation of this service file fails, and causes build failures. To address this, we simply remove the installation of the systemd service file. Fixes: http://autobuild.buildroot.net/results/ce2fc81466abd9619aa104c96234d1455de3480d/ Signed-off-by:
-
Gustavo Zacarias authored
Fixes: CVE-2016-4590 - mishandles about: URLs, which allows remote attackers to bypass the Same Origin Policy via a crafted web site. CVE-2016-4591 - mishandles the location variable, which allows remote attackers to access the local filesystem via unspecified vectors. CVE-2016-4622 - allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, a different vulnerability than CVE-2016-4589, CVE-2016-4623, and CVE-2016-4624. CVE-2016-4624 - allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, a different vulnerability than CVE-2016-4589, CVE-2016-4622, and CVE-2016-4623. Signed-off-by:
-
Bernd Kuhls authored
Fixes http://autobuild.buildroot.net/results/c45/c45530f34bf2074bd204c485615124df928f246c/ Signed-off-by:
-
- Aug 27, 2016
-
-
Waldemar Brodkorb authored
The default Blackfin processor in Buildroot isn't supported by gcc 6.1.0, so use bf532 as default. Disable any bf6xx processors for internal toolchain users. Signed-off-by:
Waldemar Brodkorb <wbx@openadk.org> Signed-off-by:
-
Rahul Bedarkar authored
With glibc 2.16, we get following build error when building jack2: [193/247] cxx: tests/iodelay.cpp -> build/tests/iodelay.cpp.4.o ../tests/iodelay.cpp:171:43: error: 'UINT32_MAX' was not declared in this scope ../tests/iodelay.cpp:171:55: error: 'UINT32_MAX' was not declared in this scope ../tests/iodelay.cpp:172:44: error: 'UINT32_MAX' was not declared in this scope ../tests/iodelay.cpp:172:56: error: 'UINT32_MAX' was not declared in this scope In glibc 2.17 or older version, Header <stdint.h> defines these macros for C++ only if explicitly requested by defining __STDC_LIMIT_MACROS. We can't use <cstdint> since it requires C++11 standard. Fixes: http://autobuild.buildroot.net/results/369ce208ffea43dad75ba0a13469159b341e3bf5/ Signed-off-by:
Rahul Bedarkar <rahul.bedarkar@imgtec.com> Signed-off-by:
-
Noé Rubinstein authored
The trousers code uses getpwent_r, which is not available in musl. Detect the availability of getpwent_r in the trousers build system, and use it conditionally. This broke the build of tpm-tools because linking with libtspi.so failed. Fixes: http://autobuild.buildroot.net/results/830fc20c68a0653afa5567edffc2ededc4e45cc6 Runtime-tested by running tpm_version in a chroot and verifying that it creates a "user.data" file with both the Buildroot-provided CodeSourcery and Musl toolchains on x86_64. Signed-off-by:
Noé Rubinstein <nrubinstein@aldebaran.com> Signed-off-by:
-
Jörg Krause authored
This was not noticed until now because: 1/ The older Blackfin toolchain doesn't have libatomic, so it didn't provide the atomic operations that protobuf needs, so protobuf was never built. 2/ The ARM Cortex-M toolchain is static-only, and protobuf requires dynamic library support. So it's only with the new Blackfin toolchain, which is based on gcc 6.x (and therefore provides libatomic) and is FDPIC-based (and therefore has dynamic library support) that this problem appeared. Since protobuf already has a BR2_PACKAGE_PROTOBUF_ARCH_SUPPORTS option, we use it to add the BR2_USE_MMU dependency (which is architecture related), which avoids the need to propagate the dependency. Fixes: http://autobuild.buildroot.net/results/2c1/2c151e84d7854a810465dc16869023e0ada2d586/ Signed-off-by: -
Arnout Vandecappelle authored
Fixing one issue exposed a second one. Signed-off-by:
Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by:
-
Waldemar Brodkorb authored
The fallback code path didn't work correctly, so fix it. Fixes: http://autobuild.buildroot.net/results/3122287ddea1e316a64ccf0d0dc9415bfefebb49/ Reported-by:
-
Arnout Vandecappelle authored
The LTO support in the kmsxx package uses the host gcc-ar and gcc-ranlib instead of the ones from the cross-toolchain. Add a patch that tries to find the right one based on CMAKE_C_COMPILER. Fixes: http://autobuild.buildroot.net/results/16a/16a38a4277dd1152a5955d62cb92f85447791ef3 Possibly also fixes: http://autobuild.buildroot.net/results/f3c/f3c48da3a9706cd366c0e0a96c3cd0ff959f2a78 (it fails later, possibly because an incompatible host ar) Signed-off-by:
-
Arnout Vandecappelle authored
Grab the patch from Debian. Signed-off-by:
-
-
Thomas Petazzoni authored
The pixman ARM optimized code assumes that ARM instructions are available. Unfortunately, the configure.ac checks do not detect that the platform is Thumb-only for Cortex-M builds, so it enables the ARM optimizations, leading to failures like: error: /home/test/autobuild/run/instance-3/output/host/usr/arm-buildroot-uclinux-uclibcgnueabi/sysroot/usr/lib/libpixman-1.a(pixman-arm-simd-asm-scaled.o): Conflicting CPU architectures 13/1 When building programs linked with pixman on Thumb-only architectures. This is due to the fact that some object files in libpixman-1.a are built for the ARM instruction set. To resolve this, we give better hints to the pixman configure script about which ARM optimizations to use: the ARM SIMD optimizations need at least a CPU that supports ARM instructions, and obviously the ARM NEON optimizations need NEON support. Fixes: http://autobuild.buildroot.net/results/54bee2ce382fcd067965d30f758f9d15514478d9/ Signed-off-by:
-
- Aug 26, 2016
-
-
Peter Korsgaard authored
Fixes a number of buffer overflows / use-after-free issues: http://git.imagemagick.org/repos/ImageMagick/blob/master/ChangeLog * Prevent buffer overflow in BMP & SGI coders (bug report from pwchen&rayzhong of tencent). * Prevent buffer overflow and other problems in SIXEL, PDB, MAP, TIFF and CALS coders (bug report from Donghai Zhu). * Prevent buffer overflow (bug report from Max Thrane). * Prevent memory use after free (reference https://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=30245 ). Signed-off-by:
-
Peter Korsgaard authored
As pointed out in bug #9161, we don't always have an inittab file (if systemd or no init is used), so the post build script should only try to tweak it if present. Signed-off-by:
-
Peter Korsgaard authored
As pointed out in bug #9161, we don't always have an inittab file (if systemd or no init is used), so the post build script should only try to tweak it if present. Signed-off-by:
-
Zakharov Vlad authored
The patch solves one of the ARC internal compiler issues. Fixes: http://autobuild.buildroot.net/results/1c4493c6a18b7a93a0368420c8f79032f9330891/ http://autobuild.buildroot.net/results/51071b790866b0c7083de3a94ad2a427009096af/ http://autobuild.buildroot.net/results/09e037c628ca2a27d8eb832dd070f50ec7ebb72a/ Signed-off-by:
-
