- May 21, 2014
-
-
Peter Korsgaard authored
Signed-off-by:Peter Korsgaard <peter@korsgaard.com>
-
Baruch Siach authored
Add upstream patches fixing internal TLS validation of X.509 certificates. See http://lists.shmoo.com/pipermail/hostap/2014-May/030273.html for details. Signed-off-by:
Baruch Siach <baruch@tkos.co.il> Signed-off-by:
-
Maxime Hadjinlian authored
printf is POSIX-compliant, echo -e is not. Signed-off-by:
Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com> Signed-off-by:
-
Maxime Hadjinlian authored
printf is POSIX-compliant, echo -e is not. Signed-off-by:
-
Thomas Petazzoni authored
In commit cd32da8f ("toolchain-external: add Linaro ARM big endian toolchain") a mistake was made, probably due to a rebase conflict that was incorrectly solved: the call to the post install staging hook that creates the necessary symbolic links for a root filesystem based on Linaro 2014.02 to work was removed. This commit reinstates this call, which should fix the problem observed by Maxime Hadjinlian while using Linaro 2014.02. Reported-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by:
-
Thomas Petazzoni authored
When Python 3 is selected in Buildroot, the host/usr/bin/python symlink of the host Python interpreter points to python3. Packages that need to use the host Python 2 interpreter have to use python2. In commit 40218a16 ("nodejs: force python interpreter"), Samuel made some changes to the nodejs package to use python2. One part of the changes is to sed a .gyp file to replace the string 'python' by the path to python2. However, this operation is done *after* calling the configure script, so it has in fact no effect. Putting this sed before calling the configure script fixes the problem. However, there is a better solution: the nodejs build system has a mechanism of variables, and it already defines a python variable according to the environment variable PYTHON being passed. So this patch instead adds a new patch to nodejs to use this python variable. Fixes: http://autobuild.buildroot.org/results/aff/affd7300895ec400de50a33d51b4e94e15d63341/ Signed-off-by:
-
- May 20, 2014
-
-
Yann E. MORIN authored
Fixes: http://autobuild.buildroot.org/results/285/2851069d6964aa46d26b4aabe7d84e8c0c6c72ce http://autobuild.buildroot.net/results/9b7/9b7870354d70e27e42d3d9c1f131ab54706bf20e [...] Signed-off-by:"Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <jacmet@uclibc.org> Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Samuel Martin <s.martin49@gmail.com> Signed-off-by:
-
Yann E. MORIN authored
Signed-off-by:
-
Yann E. MORIN authored
Currently, it is possible that more than one provider of a virtual package is selected in the menuconfig. This leads to autobuild failures, and we do not protect the user from making a mistake in the configuration. The failure is then hard to troubleshoot in any case. We can't use kconfig constructs to prevent this, since kconfig does not tell how many options did a select on another option. This change introduces a new variable a provider *must* define to include all the virtual packages it is an implementation of. Then, when evaluating the package's rules, we check that the provider is indeed the declared one for each virtual package it claims to be an implementation of. This works by taking advantage that when more than one provider is selected, only one of them will 'win' in setting the _PROVIDES_FOO option. Thus any provider just has to check it is indeed the declared provider. If not, it means that one or more other provider is selected. This gives the opportunity to the user to change its configuration, and we can match the error message in the autobuilders to skip those failures (we can skip them instead of reporting them, since they are obviously configuration errors that should not happen in the first place.) [Note: kudos to Arnout for suggesting this actual implementation. :-)] Fixes: http://autobuild.buildroot.org/results/285/2851069d6964aa46d26b4aabe7d84e8c0c6c72ce http://autobuild.buildroot.net/results/9b7/9b7870354d70e27e42d3d9c1f131ab54706bf20e [...] Signed-off-by: -
Yann E. MORIN authored
Quoting Thomas on IRC: > sstrip is a piece of crap that we should exterminate > from the surface of the planet sstrip is now unmaintained, has a long history of generating butchered binaries in some cases, and does not gain that much space in the end. We'd like to obliviate sstrip from the strip options, anihilate the sstrip package, scorch any reference in fire, and cleanse our tree free of any remnants... But first, let's just deprecate it for now. Signed-off-by:
-
Thomas Petazzoni authored
Following the issues reported by Jerry <g4@novadsp.com>, it appears that there are a number of U-Boot configuration variables we are not checking properly, leaving users with weird behavior at build time. This commit extends the existing U-Boot checks to verify that when a custom version, custom tarball, or custom Git or Mercurial repositories are selected, the appropriate fields are not empty in the configuration. Signed-off-by:
-
Thomas Petazzoni authored
ipsec-tools currently fails to build for Blackfin due to GLOB_TILDE not being supported in Blackfin external toolchains. However, after fixing this problem (which will be fixed in later versions of the Blackfin external toolchains) allows to discover that ipsec-tools uses fork() anyway. Therefore, this patch simply marks ipsec-tools as not available on non-MMU systems. Consequently, it fixes: http://autobuild.buildroot.org/results/fc4/fc4ef4101a20e64eb52da56557d6996dd73b3d86/ Signed-off-by:
-
Peter Korsgaard authored
Correct a number of issues with matchbox-keyboard: - Missing dependencies on host-pkgconf and expat - Missing kconfig select on xlib_libXft - pango/cairo confusion, ensure cairo is built before if enabled - _CONF_OPT variable typo Fixes: http://autobuild.buildroot.net/results/473/47380d57e507ec395a1132dfd7b32d35459c1c7a// http://autobuild.buildroot.net/results/d9a/d9aa2b6ddce920ea45fbd7093addfc0ee6b94467// http://autobuild.buildroot.net/results/aad/aad393a81812df28cbc296f556de2acb4e6d114b// http://autobuild.buildroot.net/results/124/124b28336ed61822fa6d5d2591b4e70d83b8a213// and 17 other build errors, dating back to 2013-07-03 Reported-by:
Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by:
-
Thomas Petazzoni authored
Even though some Blackfin processors have PCI interfaces, the PCI support is not supported by the Linux kernel: it has been marked as broken since 2008. This means there's probably little interest for PCI on Blackfin, and consequently little interest about getting pciutils to build. Fixes http://autobuild.buildroot.net/results/a27/a27ce61967ef8f780887f7681c8b0edd91656be6/ Signed-off-by:
-
Thomas Petazzoni authored
samba produces particularly large binaries, and the relocations needed for it do not fit in the possible relocation mechanisms available on AVR32. Since samba is very unlikely to be used on AVR32, let's just disable it, as we've already done for samba4. Fixes: http://autobuild.buildroot.net/results/0142b1d5b8c3f20f1bff76ece646d901407f7490/ Signed-off-by:
-
- May 19, 2014
-
-
Bernd Kuhls authored
fixes http://autobuild.buildroot.net/results/27a/27a674c6a19a729fae5cc33de0360b2a061930c1/ This patch indeed fixes several problems based on the autobuilder-defconfig used. 1) Add missing dependencies when opengl is detected by webkit to satisfy autobuilder: checking which GPU acceleration backend to use... opengl checking for XCOMPOSITE... yes checking for XDAMAGE... no configure: error: Package requirements (xdamage) were not met: 2) ... but opengl should not have been detected with the used defconfig: $ grep MESA .config BR2_PACKAGE_MESA3D=y which will lead to a link error although webkit configure found all dependencies: /home/br2/output/host/opt/ext-toolchain/bin/../lib/gcc/mips-linux-gnu/4.7.3/../../../../mips-linux-gnu/bin/ld: cannot find -lGL 3) same is valid for glx, having GL/glx.h means nothing 4) add some configure options for gles/egl as well, just to make sure ;) Signed-off-by:
-
Thomas Petazzoni authored
For some reason, we were keeping gdb version 6.6a specially for Blackfin. However, it turns out that support for Blackfin was merged in gdb 7.4 (cross-gdb and gdbserver, not native gdb on the target). Therefore, we can simply remove the support for version 6.6a and use 7.5 as the default. Both 7.4 and 7.5 were built tested, including cross-gdb and gdbserver. The original reason to switch to 7.x is that 6.6a doesn't build for Blackfin FLAT, and while it builds for Blackfin FDPIC, it only builds libiberty.a and does not actually build a cross debugger. Fixes: http://autobuild.buildroot.org/results/b47/b47f85553336b7f63ee4ecdf8598374ce4a225a3/ Signed-off-by:
-
Thomas Petazzoni authored
The build of host-gdb 7.4 fails due to some texinfo issue. To avoid that, use the same trick as is used for the target variant of gdb: tell gdb that makeinfo is missing. Signed-off-by:
-
Frank Bergmann authored
The fallocate() function is replaced by fallocate64() while compiling with LARGE_FILE flags. Current nios2 toolchain is missing the fallocate64() function. Fixes: http://autobuild.buildroot.net/results/9cd/9cd30031a40f768f6090cfba44c880fb2406672b http://autobuild.buildroot.net/results/7da/7da32ca8178aa6bada06dfaea38e9e693fba0db2 http://autobuild.buildroot.net/results/0ef/0ef7358289bff2a5f9efda27115eddb379c1a0b9 [...] [Peter: reference BR2_LARGEFILE, add autobuilder refs as suggested by Yann] Signed-off-by:Frank Bergmann <frank@frajasalo.de> Acked-by:
-
Gustavo Zacarias authored
Signed-off-by:
Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by:
-
Gustavo Zacarias authored
There's a symbol conflict between regular (POSIX) link(2) and the BSD variant for builtin heimdal when libbsd is around and used. Fixes: http://autobuild.buildroot.net/results/657/65726ceccbc2d8fa24e178ea66cd44703768bc95/ Signed-off-by:
-
- May 18, 2014
-
-
Philippe Reynes authored
The file external.mk was included before fs/common.mk, so it was impossible to add rootfs targets using the BR2_EXTERNAL mechanism. This change moves the inclusion of fs/common.mk before external.mk to allow this. Signed-off-by:
Philippe Reynes <tremyfr@yahoo.fr> [ThomasDS: rebased, update commit message] Signed-off-by:
Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by:
-
Peter Korsgaard authored
Signed-off-by: -
Romain Naour authored
Makefile's target "install-magickincarchHEADERS" and "magick-install-data-local" install both the same file (magick-baseconfig.h) in the same time... The problem can be reproduced with: mkdir /tmp/bar /usr/bin/install -c -m 644 foo /tmp/bar & /usr/bin/install -c -m 644 foo /tmp/bar/foo /usr/bin/install: cannot create regular file '/tmp/bar/foo' : File exists So, remove one of them. Fixes: http://autobuild.buildroot.net/results/d34/d34077ce582866c50bbd90de10bbe593e39463f1/build-end.log Signed-off-by:
Romain Naour <romain.naour@openwide.fr> Signed-off-by:
-
Thomas Petazzoni authored
By design, building duma on Blackfin and other non-MMU platforms is quite useless: it uses page mappings to detect buffer overrun and use-after-free programming errors. Therefore, this commit simply marks duma as not available on non-MMU platforms. Fixes: http://autobuild.buildroot.org/results/951/9519d7abb45c6a789874ec6bb84418c31a98916b/ Signed-off-by:
-
Thomas Petazzoni authored
Fixes: http://autobuild.buildroot.org/results/9e0/9e079632a6c0556c96ec8ed7564286aa84044bf7/ http://autobuild.buildroot.org/results/401/401105b5e120176e78c2e5fcabe54ab0bde1bf40/ and more Signed-off-by:
-
Thomas Petazzoni authored
Fixes: http://autobuild.buildroot.org/results/af1/af1ca869dbc7a71aa4cc89373d605ca8f790fcc9/ [Peter: also adjust largefile comment dependency] Signed-off-by:
-
Thomas Petazzoni authored
Fixes: http://autobuild.buildroot.org/results/277/277038de62d6262576a63b213374a33357a8333b/ Signed-off-by:
-
- May 17, 2014
-
-
Peter Korsgaard authored
Signed-off-by: -
Yann E. MORIN authored
There will soon be new options to the graph-depends script, which we can only sanely pass via environment variables. Currently, we use such an environment variable to pass the maximum depth of the dependency graph; the name of that variable is explicit that it contains just the depth. However, there has been so far no release of Buildroot which would make use of that variable, so no user should have come to rely on it. Rename that variable so it is less specific, and more generic, so it can be used to pass more options to graph-depends. Signed-off-by:
-
Yann E. MORIN authored
We need to tell the duma Makefile what OS we're gonna run on, or it uses default values. It turns out the default values are the same as for OS=linux (and so this change should be a no-op), but it's just better to force it, and it avoids a warning during the build. Signed-off-by:
-
Thomas Petazzoni authored
Add a patch to libXpm to fix build on noMMU architectures. Fixes: http://autobuild.buildroot.org/results/c57/c571b0a9d9f36a445ea36a4bd609154f9a9bddd5/ Signed-off-by:
-
Thomas Petazzoni authored
Even though pulseaudio has some HAVE_FORK compile-time conditionals to avoid using fork(), those parts of pulseaudio are not using it. Since using pulseaudio on !MMU platforms is fairly unlikely, we simply disable it when no MMU is available, and propagate this dependency to the appropriate locations. Signed-off-by:
-
Thomas Petazzoni authored
fluxbox uses the fork() system call, not available on noMMU platforms. It's also fairly unlikely to have to use a full-blown X.org window manager on such platforms. Signed-off-by:
-
Thomas Petazzoni authored
php-imagick selects imagemagick, and imagemagick 'depends on BR2_USE_MMU', but this dependency was not propagated to php-imagick. This commit fixes that. Signed-off-by:
-
Thomas Petazzoni authored
zyre selects filemq, and filemq 'depends on BR2_USE_MMU', but this dependency was not propagated to zyre. This commit fixes that. Signed-off-by:
-
Bernd Kuhls authored
Fixes http://autobuild.buildroot.net/results/18c/18c554d148fc00f85690c1638976dd6d0d7ff219/ Signed-off-by:
-
Bernd Kuhls authored
Make sure OpenSSL is built before mysql. Signed-off-by:
-
Bernd Kuhls authored
Make sure zlib is built before mysql. Signed-off-by:
-
Thomas Petazzoni authored
Fixes: http://autobuild.buildroot.org/results/19d/19d93324caac8b4aad7abfe7b6c3d85612636368/ Signed-off-by:
-
