summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* toolchain-external: do not use BR2_GCC_TARGET_TUNE anymoreThomas Petazzoni2014-11-072-14/+3
| | | | | | | | Since the BR2_GCC_TARGET_TUNE value is always empty now, there is no longer a point in using it in the external toolchain logic. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* gcc: do not use BR2_GCC_TARGET_TUNE anymoreThomas Petazzoni2014-11-071-3/+0
| | | | | | | | | Since the BR2_GCC_TARGET_TUNE value is always empty now, there is no longer a point in using it in the gcc package. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* arch/m68k: get rid of BR2_GCC_TARGET_TUNEThomas Petazzoni2014-11-071-8/+0
| | | | | | | | | | On m68k, we are passing the exact same values of BR2_GCC_TARGET_ARCH and BR2_GCC_TARGET_TUNE, which is redundant. Therefore, this commit removes the usage of BR2_GCC_TARGET_TUNE on m68k. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* arch/powerpc: get rid of BR2_GCC_TARGET_TUNEThomas Petazzoni2014-11-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | According to the gcc documentation for PowerPC options: '-mtune=CPU_TYPE' Set the instruction scheduling parameters for machine type CPU_TYPE, but do not set the architecture type, register usage, or choice of mnemonics, as '-mcpu=CPU_TYPE' would. The same values for CPU_TYPE are used for '-mtune' as for '-mcpu'. If both are specified, the code generated will use the architecture, registers, and mnemonics set by '-mcpu', but the scheduling parameters set by '-mtune'. In the case of Buildroot where we only target a specific system, using -mtune therefore doesn't make much sense, and using -mcpu would be more appropriate. As a consequence, this patch makes PowerPC use BR2_GCC_TARGET_CPU instead of BR2_GCC_TARGET_TUNE. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* arch/sparc: get rid of BR2_GCC_TARGET_TUNEThomas Petazzoni2014-11-071-3/+1
| | | | | | | | | | | | | On SPARC, BR2_GCC_TARGET_TUNE was only used for one specific case, the BR2_sparc_v8. There is actually no reason to not use BR2_GCC_TARGET_CPU instead for this, as all values supported for -mtune are also supported for -mcpu. Therefore, the only BR2_GCC_TARGET_TUNE case is moved as a BR2_GCC_TARGET_CPU case. [Peter: fixup merge conflict after 'sparc: Add leon3 cpu type and remove sparc{s,h}fleon{,v8}] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* arch/x86: get rid of BR2_GCC_TARGET_TUNEThomas Petazzoni2014-11-071-31/+1
| | | | | | | | | | | | | | According to the gcc documentation, -march implies -mtune on x86, so defining both BR2_GCC_TARGET_ARCH and BR2_GCC_TARGET_TUNE is redundant. Therefore, this commit removes the definition of BR2_GCC_TARGET_TUNE on x86. However, while doing so, it adds one new case for BR2_GCC_TARGET_ARCH: using -march=generic when BR2_x86_generic is selected. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* ffmpeg: use arch and cpu instead of tuneThomas Petazzoni2014-11-071-1/+6
| | | | | | | | | | | | | | | | ffmpeg currently uses BR2_GCC_TARGET_TUNE as the --cpu option value. However, there are multiple architectures for which BR2_GCC_TARGET_TUNE is not used. After inspecting the ffmpeg configure script, we concluded that using the BR2_GCC_TARGET_CPU value if available, or the BR2_GCC_TARGET_ARCH value as a fallback was the appropriate behavior. This allows to remove the reference to BR2_GCC_TARGET_TUNE, which is one step towards the removal of this option. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* arch/arm: remove BR2_GCC_TARGET_ARCH definitions on ARMThomas Petazzoni2014-11-071-19/+0
| | | | | | | | | | | | | | | | | | | | | | | On ARM, we were defining both the CPU type and the architecture variant. However, depending on the version of gcc, a given combination of (CPU, architecture) may not be the same. Since the architecture variant is implied by the CPU type, given the former is not necessary, and we can simply specify the latter. >From the gcc documentation: This specifies the name of the target ARM processor. GCC uses this name to derive the name of the target ARM architecture (as if specified by -march) and the ARM processor type for which to tune for performance (as if specified by -mtune). Where this option is used in conjunction with -march or -mtune, those options take precedence over the appropriate part of this option. Note that we verified that for all BR2_GCC_TARGET_ARCH value that existed, a proper BR2_GCC_TARGET_CPU value is defined. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* arch/arm: do not distinguish revisions of ARM1136JF-SThomas Petazzoni2014-11-071-13/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 88cf3bb91792c9c04586e14f293d89a6e0c13e1d ("arch/Config.in.arm: Use armv6k for arm1136jf-s rev1"), Benoît Thébaudeau added separate options for the revision 0 and revision 1 of the ARM1136JF-S processor, so that different -march values could be used (armv6j for revision 0, armv6k for revision 1). However, this is preventing the removal of the BR2_GCC_TARGET_ARCH option, which we need to do to give only the CPU type to gcc, and let it decide the architecture variant that matches. This is because this story of revision 0 vs. revision 1 is the only case where -mcpu doesn't fully define the CPU. Moreover, a quick test with gcc shows that -march=armv6j -mcpu=arm1136jf-s is accepted, while -march=armv6k -mcpu=arm1136jf-s makes gcc complain: " warning: switch -mcpu=arm1136jf-s conflicts with -march=armv6k switch". In addition, gcc 5 will apparently no longer allow to pass all of --with-arch, --with-cpu and --with-tune, so we will anyway have to rely only on one of them. As a consequence, this commit basically reverts 88cf3bb91792c9c04586e14f293d89a6e0c13e1d and provides only one option for ARM1136JF-S. If the two revisions are really different, then they should be supported in upstream gcc with different -mcpu values. Note that the removal of the two options should not break existing full .config, since the hidden option BR2_arm1136jf_s becomes again a visible option to select the CPU. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Benoît Thébaudeau <benoit.thebaudeau@advansee.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* dhcpcd: do not pass --target optionThomas Petazzoni2014-11-071-1/+0
| | | | | | | | | | | | | | | | | | | | dhcpcd is using $(BR2_GCC_TARGET_ARCH) as the value of its --target option. However, depending on the architecture, this value might be empty. After inspecting the dhcpcd configure script, it turns out that in fact the --target option has the following semantic: --target=TARGET configure for building compilers for TARGET [HOST] So it is very much like the --target option of regular, autoconf-based, configure scripts. Since dhcpcd is not a compiler, passing --target is pointless. Moreover, as long as --os=linux is passed, passing --host or --target is completely ignored by the configure script. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* toolchain-external: use BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-061-8/+6
| | | | | | | | | | | | Refactor the toolchain-external Config.in file to use the BR2_ARM_CPU_ARM*. All of the changes are purely mechanical, except for the Arago ARMv5 toolchain: it had a 'depends on BR2_GCC_TARGET_ARCH != "armv5t"', but armv5t was not a possible value for BR2_GCC_TARGET_ARCH. Since the toolchain is ARMv5TE, the only ARM architectures we need to exclude are ARMv4 and ARMv4T. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* libnspr: use the BR2_ARM_CPU_ARMV7A optionThomas Petazzoni2014-11-061-1/+1
| | | | | | | | | | | The libnspr --enable-thumb2 option was only enabled on Cortex-A8 and Cortex-A9. This commit switches to using BR2_ARM_CPU_ARMV7A instead, which will allow using Thumb2 for this package even with the other Cortex-A cores. [Peter: use BR2_ARM_CPU_HAS_THUMB2 instead] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* x264: use the BR2_ARM_CPU_ARMV7A optionThomas Petazzoni2014-11-061-1/+1
| | | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* valgrind: use the BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-062-6/+5
| | | | | | | | | | | Instead of using the exhaustive list of Cortex-A ARM cores, use BR2_ARM_CPU_ARMV7A instead. We also fix a wrong comment that said the Valgrind package could only be selected for Cortex-A8 and Cortex-A9, which was true a long time ago, but was no longer true since it was also enabled for all the other Cortex-A platforms. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* webkit: use BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-061-2/+1
| | | | | | | | | The webkit package is not available on ARM < v5, so this commit switches to using the newly introduced BR2_ARM_CPU_ARM* options instead of per ARM core options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* vo-aacenc: use the BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-061-1/+1
| | | | | | | | | The vo-aacenc package has an option to enable ARMv5 optimizations. It was enabled based on per ARM core options, but now that we have per ARM architecture options, this commit switches to using them. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* speex: use BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-061-1/+1
| | | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* qt5: use the BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-061-1/+1
| | | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* nodejs: use BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-061-2/+2
| | | | | | | | | Adjust the nodejs Config.in dependencies to use the per ARM architecture BR2_ARM_CPU_ARM* options instead of the per ARM core options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* nettle: use the BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-061-1/+1
| | | | | | | | Adjust the nettle package to use the BR2_ARM_CPU_ARM* option to disable the usage of assembly code on ARMv4 and ARMv5. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* libplayer: use BR2_ARM_CPU_ARM* optionThomas Petazzoni2014-11-061-2/+1
| | | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* mplayer: also hide toolchain comment on ARMv4Peter Korsgaard2014-11-061-0/+1
| | | | | | Like we do for the other arch dependencies. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* mplayer: allow usage of ARMv6 optimizations on ARMv7 platformsPeter Korsgaard2014-11-061-1/+1
| | | | | | Similar to what we do for ffmpeg/gst-ffmpeg/gst1-libav. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* mplayer: use BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-062-4/+3
| | | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* gst1-libav: allow usage of ARMv6 optimizations on ARMv7 platformsThomas Petazzoni2014-11-061-1/+1
| | | | | | | | | | Contrary to the ffmpeg package, the gst1-libav package was only allowing ARMv6 optimizations on ARMv6 platforms. This commit also allows ARMv6 optimizations on ARMv7 platforms, like the ffmpeg package does. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* gst1-libav: use the new BR2_ARM_CPU_ARM* optionsThomas Petazzoni2014-11-061-2/+2
| | | | | | | | | Instead of using the Config.in options for each individual ARM core, use the newly introduced BR2_ARM_CPU_ARM* options, which exist per ARM architecture. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* webkit: Add --enable-dependency-tracking to the configure optionsVicente Olivert Riera2014-11-061-0/+1
| | | | | | | | | | | | | | | | | | | --disable-dependency-tracking was added globally to package/pkg-autotools.mk by this commit: http://git.buildroot.net/buildroot/commit/?id=3e37b0fc6cbbe2245e39fedb247a381fb4e0d992 This causes a failure in webkit because some source files are generated after the Makefile is created. To fix this, we add --enable-dependency-tracking to the configure options. Fixes: http://autobuild.buildroot.net/results/5beea967b02df202bca1d42afd6fa8c2c13383d5/ Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* linux-headers: bump 3.{12, 2}.x seriesGustavo Zacarias2014-11-061-2/+2
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* barebox: bump to version 2014.11.0Fabio Porcedda2014-11-061-2/+2
| | | | | | | Signed-off-by: Fabio Porcedda <fabio.porcedda@gmail.com> Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* stunnel: bump to version 5.07Gustavo Zacarias2014-11-062-4/+11
| | | | | | | | | | Also enable optional systemd support. [Peter: fixup announcement url in .hash as pointed out by Baruch] Signed-off-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: Peter Korsgaard <peter@korsgaard.com>
* libcurl: security bump to version 7.39.0Gustavo Zacarias2014-11-063-39/+2
| | | | | | | | | | | | | | Fixes: CVE-2014-3707 - libcurl's function curl_easy_duphandle() has a bug that can lead to libcurl eventually sending off sensitive data that was not intended for sending. Removed patch that was upstream and now in the release. Signed-off-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: Peter Korsgaard <peter@korsgaard.com>
* subversion: ensure --disable-debug doesn't mangle CFLAGSPeter Korsgaard2014-11-061-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | Fixes: http://autobuild.buildroot.net/results/fc6/fc69a19c66462585449f7c4dad174d45a84e4947/ http://autobuild.buildroot.net/results/e04/e0471f2a9087d547840a7b18863289963e357b57/ http://autobuild.buildroot.net/results/bd8/bd8cdf976937c7b9029658871929f4be464b7a47/ http://autobuild.buildroot.net/results/652/652c3afe844e912061fbc5991e6fecad98ff6e6f/ And many more. When --disable-debug is passed to configure, as is automatically done by the autotools infrastructure since 822a757456e (infra: Move --enable/--disable-debug to package/Makefile.in), the configure script will try to strip debugging (-g) options from the C/CXXFLAGS. The logic to do so is unfortunately buggy, so it ends up mangling options like -mfloat-gprs=double that we use on certain PowerPC variants, breaking the build. Fix it by adjusting the sed regexp to be more selective in what it strips. The package unfortunately doesn't cleanly autoreconf, so configure is patched instead of configure.ac. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* adwaita-icon-theme: depends on host-libgtk3Eric Le Bihan2014-11-042-1/+2
| | | | | | | | | | | The adwaita icon theme can only be selected with libgtk3 and depends on host-libgtk3 to build. Fixes http://autobuild.buildroot.org/results/f8d/f8d0e2198fa54f9141512e2db6dc46e3cee1cd44/ Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* mpd: bump to version 0.19.2Gustavo Zacarias2014-11-043-32/+2
| | | | | | | Patch now upstream. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* lttng-tools: update hashPeter Korsgaard2014-11-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes: http://autobuild.buildroot.net/results/4c0/4c0f8583986d72fbc879d21bef65246bc9b4a732/ http://autobuild.buildroot.net/results/db4/db4011b3444c71942b1a269dd16b18652fd22d97/ http://autobuild.buildroot.net/results/220/220ef41676096bafd2e38f4fbb892eb0a7d654d8/ http://autobuild.buildroot.net/results/545/545371f5a39c85aba0d15a41cdc46e1cf6c1ba9f/ And many more. Upstream silently updated the tarball on 30/10, breaking the build. The only difference between the old and new tarballs is that the version number is fixed: diff -urpN old/lttng-tools-2.5.1/include/version.h new/lttng-tools-2.5.1/include/version.h --- old/lttng-tools-2.5.1/include/version.h 2014-10-20 21:47:51.000000000 +0200 +++ new/lttng-tools-2.5.1/include/version.h 2014-10-31 16:33:17.000000000 +0100 @@ -20,7 +20,7 @@ #ifndef VERSION_H #define VERSION_H -#define GIT_VERSION "heads/stable-2.5-0-g56eb774" +#define GIT_VERSION "2.5.1" The copy of the old tarball on sources.buildroot.net has also been removed. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* qextserialport: allow building with Qt5Thomas Petazzoni2014-11-032-5/+9
| | | | | | | | qextserialport builds fine with both Qt4 and Qt5, so this commit enables it for Qt5. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* qjson: allow building with Qt5Thomas Petazzoni2014-11-032-2/+4
| | | | | | | | | Since commit 18714011b231fc326c96782134fbea778ab6a94d ("qjson: bump version"), qjson can be built either against Qt4 or Qt5. This commit therefore allows this package to be selected when Qt5 is enabled. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* qt5: expose a QT5_QMAKE variable for other Qt5 packagesThomas Petazzoni2014-11-031-0/+3
| | | | | | | | | Much like package/qt/qt.mk exposes a QT_QMAKE variable that other qmake-based Qt4 libraries/applications can use in their .mk file, this commit adds a QT5_QMAKE variable to allow the same for Qt5 packages. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package: prepare to support modules that work with Qt or Qt5Thomas Petazzoni2014-11-035-4/+8
| | | | | | | | | | | | | | | | | | | | | | Currently, all the Qt external modules (qtuio, qjson, etc.) can only be compiled against Qt4. However, some of them (qjson, qextserialport at least) can compile with either Qt4 or Qt5. Therefore, this commit adjusts the Config.in logic to make it possible for certain modules to be selected with either Qt4 or Qt5. We use the same approach as the one of for Python 2 vs. Python 3 modules: - in package/Config.in, the package Config.in files are included either if BR2_PACKAGE_QT or BR2_PACKAGE_QT5 are enabled. - each individual package is then responsible for having a dependency on either BR2_PACKAGE_QT, or BR2_PACKAGE_QT5 or both depending on what they support. In this commit, we add a dependency on BR2_PACKAGE_QT to all packages, since for now, they only support Qt4. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* qt5: select qt5basePeter Korsgaard2014-11-031-0/+1
| | | | | | | | | | | qt5base is (as the name hints) the basics of anything related to qt5, so enabling qt5 without enabling qt5base doesn't make any sense as nothing will get built. Selecting it here also simplifies the upcoming series to add qt5 support to external qt modules. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* qemu: needs IPv6Peter Korsgaard2014-11-031-2/+4
| | | | | | | | | | | | Fixes http://autobuild.buildroot.net/results/f53/f53d4d47a6b65c40c1b122dfad61d9164e533bf0/ Actually only the linux-user code needs it, but with the _CUSTOM_TARGETS option it is difficult to ensure it only for userland emulation, so just add it to the main qemu option. At the same time add the missing wchar/mmu dependencies to the comment. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* qemu: fix build when python3 is enabledPeter Korsgaard2014-11-031-1/+1
| | | | | | | | | | | | | | | Fixes: http://autobuild.buildroot.net/results/04e/04ec455e352319a46dc06def1762c65ad28a12a1/ http://autobuild.buildroot.net/results/f19/f1932657912674af444602ac59211b6caf6841ca/ http://autobuild.buildroot.net/results/18a/18a43df80616280506a44ac3abc327ddf0e7b079/ http://autobuild.buildroot.net/results/44c/44c00b50248018c4e81f4fbb1041d35b78f89640/ And many others. When python3 for the target is enabled, $(HOST_DIR)/usr/bin/python points to host-python3, not host-python - Breaking the build. Ensure host-python is used. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* avahi: fix libgtk3 build issue by patching Makefile.in instead of Makefile.amPeter Korsgaard2014-11-032-21/+19
| | | | | | | | | | | | | | | | Fixes: http://autobuild.buildroot.net/results/f0b/f0b4f8c46eb1de6cf5ed081dacd248c66c591aa3/ http://autobuild.buildroot.net/results/dac/daca5d030b8ecc6d11901e2936fe2151d0930852/ http://autobuild.buildroot.net/results/05e/05e7fb9a888169ba7c4cb28abdb4febb5215354c/ http://autobuild.buildroot.net/results/743/743f30b1816b17a0a1397b7fd8b5a8571c4dde03/ And many others. So we no longer need to autoreconf the package. Autoreconfing is non-trivial as it uses m4 macros from glib, but we don't want to unconditionally pull in glib. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* orc: disable for uclinuxPeter Korsgaard2014-11-031-0/+2
| | | | | | | | | | | Fixes http://autobuild.buildroot.net/results/445/4456e49a6c33a80570b4f59ec9799a8d4a314af1/ The orc configure script doesn't recognize uclinux, so builds using BR2_BINFMT_FLAT fails. While this could be patched, orc doesn't have any acceleration for blackfin and orc isn't a hard dependency of any other package, so just disable it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* libwebsockets: needs host-openssl when built with openssl supportPeter Korsgaard2014-11-031-1/+1
| | | | | | | | | | | | | | | Fixes http://autobuild.buildroot.net/results/d01/d0190a6e5c6b5aa78cfefc29e4e8a4e4b135450b/ http://autobuild.buildroot.net/results/9bb/9bb8defedb8024de83eb3a609ab584efb5d0d2b0/ http://autobuild.buildroot.net/results/e4a/e4a1b298e7e158d3614b89e61d40ef9a00e7ff67/ http://autobuild.buildroot.net/results/5e2/5e24a90058111f7d5618047410f809b45bc165f6/ And many others. The build system wants to create a ssl key for testing using host-openssl, so ensure it is available. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* host-openssl: use correct prefix so libssl / libcrypto can be foundPeter Korsgaard2014-11-031-4/+5
| | | | | | | | | | | | | | | | | | | | Fixes (root cause of): http://autobuild.buildroot.net/results/d01/d0190a6e5c6b5aa78cfefc29e4e8a4e4b135450b/ http://autobuild.buildroot.net/results/9bb/9bb8defedb8024de83eb3a609ab584efb5d0d2b0/ http://autobuild.buildroot.net/results/e4a/e4a1b298e7e158d3614b89e61d40ef9a00e7ff67/ http://autobuild.buildroot.net/results/5e2/5e24a90058111f7d5618047410f809b45bc165f6/ And many others. The host version of openssl should be configured to use the host directory as its prefix and the INSTALL_PREFIX dance shouldn't be used, as otherwise host-openssl will look in /usr for its libraries. While we are at it, ensure our host CFLAGS are used similar to how we do for the target build. Also enable zlib support as we already list it as a dependency. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* dbus: Remove DBUS_USERS duplicateMaxime Hadjinlian2014-11-031-5/+2
| | | | | Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* targetcli-fb: bump versionMaxime Hadjinlian2014-11-031-1/+1
| | | | | Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/ffmpeg: bump version to 2.4.3Bernd Kuhls2014-11-021-1/+1
| | | | | Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* package/dovecot-pigeonhole: bump version to 0.4.6Bernd Kuhls2014-11-021-1/+1
| | | | | Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
OpenPOWER on IntegriCloud