- Feb 05, 2013
-
-
Gustavo Zacarias authored
Fixes CVE-2013-0169, CVE-2012-2686 and CVE-2013-0166. Signed-off-by:
Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk>
-
Thomas Petazzoni authored
We already had backported patches for the Blackfin and AArch64 support, and now we would have needed to also backport the Xtensa support and the Microblaze support. This starts to get crazy. Let's switch to using a Git version from Github, until libffi finally releases a new stable version. In order to achieve this, we also need to: * autoreconf the package, so that a libffi.pc file gets generated * manually install the libffi.pc file, because it doesn't get installed by libffi Makefile, for some reason * remove the part of the target post install hook that was messing with libffi.pc, since it was modifying the one in STAGING_DIR (which is odd for a target post install hook), and the libffi.pc file is anyway not installed to the target anymore. Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
-
Chris Zankel authored
[Thomas Petazzoni: rename patch to not have the package version in the patch file name, adjust the commit title.] Signed-off-by:
Chris Zankel <chris@zankel.net> Signed-off-by:
-
Thomas Petazzoni authored
As we are going to add an Xtensa related patch that needs to be applied *after* the AArch64 patch, let's first add a number to each util-linux patch file name, so that we know they will be applied in the right order. Signed-off-by:
-
Arnout Vandecappelle authored
The external toolchain wrapper sets sysroot etc. to an absolute path. By changing this to a relative path, it is possible to move the host directory to a different location and still have a working build system. This only works for a downloaded external toolchain. For a pre-installed external toolchain, it is possible to move the host directory to a different location, but not the external toolchain directory (it does work if the external toolchain directory lies within the host directory). For an internal or crosstool-ng toolchain, there is no wrapper so updating the sysroot path should be done in a different way. See http://lists.busybox.net/pipermail/buildroot/2012-February/050371.html for information about others things to do to make the host directory relocatable. Signed-off-by:
Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Acked-by:
Samuel Martin <s.martin49@gmail.com> Signed-off-by:
-
Gustavo Zacarias authored
[Peter: remove the unneeded BR2_USE_WCHAR dependency] Signed-off-by:
-
Gustavo Zacarias authored
Signed-off-by:
-
Gustavo Zacarias authored
Fixes CVE-2013-0213 Signed-off-by:
-
Peter Korsgaard authored
Thanks to WIll Newton to noticing. Signed-off-by: -
Peter Korsgaard authored
This reverts commit f1b86cef While the fix makes gnutls build without wchar, it doesn't actually work as there's no rpl_wctomb implementation so the .so ends up with an undefined reference to wctomb: ./host/usr/bin/arm-linux-nm -D staging/usr/lib/libgnutls.so.28|grep wctomb U wctomb Causing linker errors for packages trying to use it: CCLD msmtp host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/libgnutls.so: undefined reference to `wctomb' collect2: ld returned 1 exit status Signed-off-by:
-
Peter Korsgaard authored
Signed-off-by: -
Gustavo Zacarias authored
Fixes CVE-2012-5958, CVE-2012-5959, CVE-2012-5960, CVE-2012-5961, CVE-2012-5962, CVE-2012-5963, CVE-2012-5964 and CVE-2012-5965. Signed-off-by:
-
Peter Korsgaard authored
This reverts commit 6b307de4 (version part). Fixes http://autobuild.buildroot.org/results/46828cef48bc1267583ba8174c0e8ee993fac865 As discussed on the list, let's revert this for the 2013.02 release and then bring it up wiith gawk upstream / try to fix for 2013.05+ Signed-off-by:
-
Peter Korsgaard authored
Fixes http://autobuild.buildroot.org/results/cbc74e2fb5eaefac1fe17ada1dc46a5c906cc1c9 Also propagate BR2_USE_MMU to lvm2's reverse dependencies. Signed-off-by:
-
Peter Korsgaard authored
Fixes http://autobuild.buildroot.org/results/c0bfc03389382235782474b278ca4afd1d283d60 The included (LGPL) license file is called COPYING. Signed-off-by:
-
- Feb 04, 2013
-
-
Yann E. MORIN authored
Signed-off-by:
"Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by:
-
Yann E. MORIN authored
Signed-off-by:
-
Carsten Schoenert authored
gdb 7.4.1 fails with the following error gdb-7.4.1/gdb/linux-nat.h:79:18: error: field 'siginfo' has incomplete type because gdb use 'struct siginfo' instead of 'struct siginfo_t'. Crosstool-NG allready use the patches to prevent this error so use this patches for buildroot too. see also http://permalink.gmane.org/gmane.comp.gcc.cross-compiling/15305 Fixes http://autobuild.buildroot.net/results/b894a5cecd9c5e0a1a751ebbff90a14aea1803da/build-end.log Signed-off-by:
Carsten Schoenert <c.schoenert@gmail.com> Signed-off-by:
-
Gustavo Zacarias authored
Signed-off-by:
-
Baruch Siach authored
Signed-off-by:
Baruch Siach <baruch@tkos.co.il> Signed-off-by:
-
Stefan Fröberg authored
This patch will add <pkg>_CONFIG_FIXUP variable to buildroot infra. It's purpose is to inform buildroot that the package in question contains some $(STAGING_DIR)/usr/bin/*-config files and that we want to automatically fix prefixes of such files. It is often the case that many packages call these files during their configuration step to determine 3rd party library package locations and any flags needed to link against them. For example: Some package might try to check the existense and linking flags of NSPR package by calling $(STAGING_DIR)/usr/bin/nspr-config --prefix. Without this fix. NSPR would return /usr/ as it's prefix which is wrong when cross-compiling. Correct would be $(STAGING_DIR)/usr. All packages that have <pkg>_INSTALL_STAGING = YES defined and also install some config file(s) into $(STAGING_DIR)/usr/bin must hereafter also define <pkg>_CONFIG_FIXUP with the correspondig filename(s). For example: DIVINE_CONFIG_FIXUP = divine-config or for multiple files: IMAGEMAGICK_CONFIG_FIXUP = Magick-config Wand-config Signed-off-by:
Stefan Fröberg <stefan.froberg@petroprogram.com> Signed-off-by:
-
Thomas Petazzoni authored
This commit fixes the exact same problem than 21a0c11a, but for the gdbserver build. The problem is that when you use the Crosstool-NG toolchain backend, gawk gets built as a dependency of Crosstool-NG. So the gdb configure scripts detects it, and assumes it is in the PATH (because the gdb configure step gets run with TARGET_MAKE_ENV). But then, the build fails, because it tries to run gawk, but gawk isn't in the PATH, because we forget to use this TARGET_MAKE_ENV variable when building gdbserver. Fixes http://autobuild.buildroot.org/results/d0173de533b5e2fffed2eff7327a502ed2d787cd/build-end.log Signed-off-by:
-
Thomas Petazzoni authored
tvheadend requires an atomic_add operation. Either you have a gcc >= 4.3 toolchain and it uses the gcc intrinsics, or it has special code for x86, x86-64, PPC and ARM. So in the context of Buildroot, the only really problematic architecture is avr32, which uses gcc 4.2. Fixes http://autobuild.buildroot.org/results/f015b1888d739c383aca61609059aa7675a4da7d/build-end.log Signed-off-by:
-
Thomas Petazzoni authored
Signed-off-by:
-
Gustavo Zacarias authored
Signed-off-by:
-
Gustavo Zacarias authored
Signed-off-by:
-
Gustavo Zacarias authored
It's moved from wireless.kernel.org to generic kernel.org Signed-off-by:
-
Gustavo Zacarias authored
Signed-off-by:
-
Gustavo Zacarias authored
Signed-off-by:
-
Thomas Petazzoni authored
We have a patch that allows neard to build even on toolchain using old kernel headers that lack the nfc.h header. However, after the bump to neard 0.9, this patch was not updated to take into account the two new plugins that neard has added. Fixes http://autobuild.buildroot.org/results/5eeb6f62cc0e654a536b6614dc51e8af4e301bb6/build-end.log Signed-off-by:
-
Peter Korsgaard authored
Signed-off-by: -
Thomas Petazzoni authored
Fixes http://autobuild.buildroot.org/results/1fb89ab412935ab02494b269a367b283cf9618c1/build-end.log Signed-off-by:
-
Thomas Petazzoni authored
Add a patch to fix a parallel build issue caused by a header file being generated too late. Fixes: http://autobuild.buildroot.org/results/2324974d4818b2657a7df4beee33fc4713d6116f/build-end.log Signed-off-by:
-
Thomas Petazzoni authored
Signed-off-by:
-
- Feb 03, 2013
-
-
Thomas Petazzoni authored
heirloom-mailx uses fork(), so we can't use it as is on !mmu platforms. Fixes: http://autobuild.buildroot.org/results/c5a8e3a4cbc1e1de985fe3c724b711027865abe7/build-end.log Signed-off-by:
-
Peter Korsgaard authored
Signed-off-by: -
Marek Belisko authored
[Peter: fix dependencies, comment] Signed-off-by:
Marek Belisko <marek.belisko@open-nandra.com> Signed-off-by:
-
Marek Belisko authored
[Peter: make mutual exclusive with dmsetup-only, drop special install / make] Signed-off-by:
-
- Feb 02, 2013
-
-
Marek Belisko authored
Without this change if some package which have dependency on device mapper and use pkgconfig to check version always fail to find library because devmapper.pc file wasn't installed. Signed-off-by:
-
Thomas Petazzoni authored
Signed-off-by:
-
