summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* classes/sanity: avoid bblayers version issue when switching between poky and ↵Paul Eggleton2015-02-232-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | other DISTRO values If you create a build directory with poky, or set DISTRO to "poky" and run bitbake, you'll get a bblayers.conf file with LCONF_VERSION set to 6. If you then set DISTRO to any other value where the new distro config doesn't pull in poky's config, e.g. "nodistro", you would then get a bblayers.conf version error which didn't immediately make sense. (The layer versions have been out-of-step ever since meta-yocto-bsp was split out of meta-yocto several years ago). This is just painful and we'd rather users didn't have to deal with it. Obviously it isn't an OE-Core problem per se, but a simple way to resolve it for everyone is to bump OE-Core's version to 6 with an automatic no-op upgrade. Also ensure that multiple upgrade functions (such as the poky one) have a chance to execute by not breaking out of the loop as we were before. Fixes [YOCTO #6139]. (From OE-Core rev: 2fdeee2fad69445b0d97148826c7b027820be63a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bind: fix and enable parallel build"Richard Purdie2015-02-231-0/+1
| | | | | | | | | | This reverts commit b003df03358aea4e9e094ee339a9f6796866961e. We keep seeing parallel make failures on the autobuilder (From OE-Core rev: af46b9f5dd5436b3d48f2fcd7a69f32343b62442) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "logrotate: 3.8.8 -> 3.8.9"Richard Purdie2015-02-234-60/+48
| | | | | | | | This reverts commit 0a69248db774f169318fc5954c805f0a7e8803dc. The update causes QA failures on the autobuilder. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "openssl: fix and enable parallel build"Richard Purdie2015-02-231-0/+3
| | | | | | | | | | This reverts commit 7502fa5febdd7a2281d626f7040782fb1f9af59e. We keep seeing parallel make failures in openssl :( (From OE-Core rev: 9afc85a7be203c5a0eac1977e777a24504cb3088) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-native: Reverts usage of distutils.sysconfig On older versions of ↵Alejandro Hernandez2015-02-232-12/+99
| | | | | | | | | | | Python, sysconfig read the Makefile and Python.h, generated at build time now it uses _sysconfigdata which contains information about the HOST, erroneous in our case, this causes an error when bulding something using distutils since it obtains compiler information and such. Also fixes configuration of _ctypes/libffi (From OE-Core rev: 3c76d5ef1f4d5270c94661d9fde7e31391b5cc2d) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Python: Upgrade from 2.7.3 to 2.7.9:Alejandro Hernandez2015-02-2333-2818/+366
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Based on Paul Eggletons work to partially upgrade to Python 2.7.6 Modified: default-versions.inc: switched to python 2.7.9 generate-manifest-2.7.py: fixed _sysconfigdata python-2.7-manifest.inc: fixed _sysconfigdata python.inc: Updated checksums and source, no LICENSE change just updated some dates python-native_2.7.3 -> python-native_2.7.9 and updated patches python_2.7.3 -> python_2.7.9, and added ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no in EXTRA_OECONF to solve python issue #3754, only needed when cross compiling, also updated patches use_sysroot_ncurses_instead_of_host.patch: New patch to use ncursesw from sysroot instead of hosts, introduced by fix for python issue #15268 Rebased: 01-use-proper-tools-for-cross-build.patch 03-fix-tkinter-detection.patch 05-enable-ctypes-cross-build.patch 06-avoid_usr_lib_termcap_path_in_linking.patch avoid_warning_about_tkinter.patch builddir.patch fix_for_using_different_libdir.patch host_include_contamination.patch multilib.patch nohostlibs.patch search_db_h_in_inc_dirs_and_avoid_warning.patch Deleted (fixed on upstream): 06-ctypes-libffi-fix-configure.patch CVE-2013-4073_py27.patch gcc-4.8-fix-configure-Wformat.patch json-flaw-fix.patch posix_close.patch pypirc-secure.patch python-2.7.3-CVE-2012-2135.patch python-2.7.3-CVE-2013-1752-smtplib-fix.patch python-2.7.3-CVE-2014-1912.patch python-2.7.3-CVE-2014-7185.patch python-2.7.3-berkeley-db-5.3.patch python-fix-build-error-with-Readline-6.3.patch remove-BOM-insection-code.patch remove_sqlite_rpath.patch python2.7.3-nossl3.patch [YOCTO #7059] (From OE-Core rev: d4ad95f0d5f08891637c644e85b09da9c4585059) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: fix broken clones of git recipesPaul Eggleton2015-02-231-0/+33
| | | | | | | | | | | | | | | | | | | | Because we move the workdir when extracting source, then move the source and delete the temporary workdir, you lose the indirection symlink pointed to by the alternates file (which is created when the fetcher clones it from DL_DIR with -s) and the resulting repository is broken. In any case, for a source repo that the user may put their own changes into, we can't really rely on a clone made with -s in case the original goes away - because of cleanall, DL_DIR disappearing, etc. So repack the repository so that it is a complete, non-shared clone after unpacking. (While I'm at it, add a test for devtool modify with a git recipe which verifies that this works.) (From OE-Core rev: dccdde4321c48a571677995a4e1dfc583e899cbe) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: update-recipe: add handling for git recipesPaul Eggleton2015-02-231-1/+69
| | | | | | | | | | | | | When updating git-based recipes, in a lot of cases what you want is to push the changes to the repository and update SRCREV rather than to apply patches within the recipe. Updating SRCREV is now the default behaviour for recipes that fetch from git, but this can be overridden in both directions using a new -m/--mode option. (From OE-Core rev: 654792bb87610ee3569d02a85fa9ec071bf8ab6d) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/recipeutils: minor improvements to patch_recipe()Paul Eggleton2015-02-231-2/+2
| | | | | | | | | | * Ensure it knows where to put SRCREV and S * Handle prepend/append and functions in general (From OE-Core rev: a770c3764efa857a8b1f0ce4b398277cd483a6af) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: build: run do_populate_sysroot instead of do_installPaul Eggleton2015-02-231-0/+40
| | | | | | | | | | | | If you want to be able to make use of libraries in conjunction with devtool then we need to install them into the sysroot for other recipes to use. Make it a configuration option in case it needs to be changed at runtime. (From OE-Core rev: 94f517ad8e55edfbe6f06afd963bcfeb849626ff) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: reset: run bitbake -c clean on recipePaul Eggleton2015-02-231-0/+4
| | | | | | | | | | | If you've added a new recipe, you want the output cleaned when you do devtool reset, otherwise cruft from building the recipe may remain which could interfere with future builds. (From OE-Core rev: 664d1a7fe8f8288fabc582d00f6e36ab29496ec5) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/kernel-yocto: extend SRCTREECOVEREDTASKSPaul Eggleton2015-02-231-1/+1
| | | | | | | | | | | | * Add do_shared_workdir which was added recently * Add do_fetch and do_unpack to this list, because at the moment if you enable externalsrc through a bbappend the += in this class wipes out the original value from externalsrc (which is set with ?=) (From OE-Core rev: 5717e3b60731d2cb9394c13bff049a467c3aeec1) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/externalsrc: show a warning on compilingPaul Eggleton2015-02-231-0/+6
| | | | | | | | | | | | Make sure there's no chance of anyone forgetting they have a recipe set up for externalsrc; otherwise you could get confused about what is going on. (With our default logging setup we can't make it a note because the UI doesn't forward those; otherwise I would have used bb.note().) (From OE-Core rev: 7b73473bc9d19331a103cf4958059d3ceb84b486) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/externalsrc: add workaround for recipes that use SRCPV in PVPaul Eggleton2015-02-231-0/+4
| | | | | | | | | | | | | | | | | Here we set SRC_URI to blank, however doing so means that the function that is called when you expand the default value of SRCPV (i.e. bb.fetch2.get_srcrev()) will fail, so any recipe that references SRCPV in PV couldn't previously be used with externalsrc. (At some point we may fix the function to work in the externalsrc case, but then we would also need to ensure that ${B} did not change as a result of PV changing any time the HEAD revision changes in the external source tree, or you'll lose any intermediate build artifacts.) (From OE-Core rev: 26f8060c3475ec988194b2163e422ba4e776fd8b) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/externalsrc: fix source being wiped out on clean with kernelPaul Eggleton2015-02-231-0/+14
| | | | | | | | | | | | | kernel.bbclass adds ${S} do do_clean[cleandirs], but this means if you run bitbake -c clean <kernelrecipe> then your external source tree will be trashed, which could be a disaster. For safety, remove ${S} from cleandirs for every task. We also have to do the same for ${B} in the case where EXTERNALSRC_BUILD is set to the same value as EXTERNALSRC. (From OE-Core rev: b5071fb2667b8751885d38ca62fa36c870177cd5) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/patch: fix PATCHTOOL = "git" with source in a subdirectoryPaul Eggleton2015-02-231-2/+5
| | | | | | | | | | | | | For recipes that have their actual source in a subdirectory of what is fetched (e.g. mkelfimage), we need to find the root of the repository within the GitApplyTree code that attempts to set up the required git hooks and use that, rather than expecting the root to be the same as ${S}. (From OE-Core rev: d820303f64ea610338ec11ffd79269e7831d1da9) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pulseaudio: upgrade to 6.0Cristian Iorga2015-02-235-102/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes: - BlueZ 5 native HSP (headset) support; - BlueZ 5 HFP (hands-free) profile support via oFono; - systemd socket activation support; - Better support for multichannel and 2.1 profiles; - Remap optimisations; - Many minor improvements, bug fixes, and i18n updates. - Switched to ${BP} variable. - Patch 0001-configure.ac-Check-only-for-libsystemd-not-libsystem.patch removed, no longer necessary. - Patch CVE-2014-3970.patch included upstrem, removed. - Slightly changed copyright notice, only a clarification. libsamplerate based resamplers are now deprecated, because they offer no particular advantage over speex. Dependency to libsamplerate0 dropped. [ RB: disable systemd until systemd.bbclass can handle user units ] (From OE-Core rev: c4de42aadd4c8a4a8f16c25e7dcdefef79daf030) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine/qemu: Switch from ext3 to ext4Richard Purdie2015-02-212-2/+2
| | | | | | | | | | There is no good reason not to use ext4 at this point, it has advantages and few drawbacks. Therefore switch the qemu machines over (and the default runqemu script options). (From OE-Core rev: 430b9ae71b1aa76f8421127d17e0e0723d4818d3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: set a variable to map to the OE Layer Index namePaul Eggleton2015-02-211-0/+2
| | | | | | | | | | | | | | | | | | | Add a variable that allows us to map the OE-Core layer to the name that represents it in the OpenEmbedded layer index. This will be used by bitbake-layers layerindex-fetch so that it knows that for example OE-Core is already fetched and included in the current configuration. Note - it won't be required for us to go around and set this for every layer - we can do the matching based on repo and subdirectory, but OE-Core is somewhat special in that it does sometimes appear in different places, for example in poky. [YOCTO #5348] (From OE-Core rev: d1cf0edd79ec3ba3bd17126183e4cb99aa50ffaf) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add two variables for layer indexChong Lu2015-02-211-0/+6
| | | | | | | | | | | | Add BBLAYERS_LAYERINDEX_URL variable that bitbake-layers can use to find layer index. Add BBLAYERS_FETCH_DIR variable that bitbake-layers can use to specify fetch directory. [YOCTO #5348] (From OE-Core rev: ae585a7d2744222606aeb533815d22ade8e10097) Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/selftest/bblayers: use dashed subcommandsPaul Eggleton2015-02-211-3/+3
| | | | | | | | | | | | bitbake-layers subcommands with underscores are the old syntax; the dashed form has been supported (and displayed in the help text) for quite a while now, and the old syntax is about to be unsupported, so use the dashed form in the tests. (From OE-Core rev: ab2efd82b2c3419e0139b91c79a9993b257970c9) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Dont offer to be parsed for non-glibc TCLIBC selectionKhem Raj2015-02-211-8/+4
| | | | | | | | | | | | | We now can support musl along with uclibc and glibc earlier when only alternative was uclibc this check was fine but now we need to consider non-glibc vs glibc case instead of uclibc vs glibc Change-Id: Id794ce193c6557b5435002a8f9b6eb608738b696 (From OE-Core rev: 5d7bc14d22da87837741fefae5924571fdff750d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tclibc-musl: Use musl for providing virtual/libintl instead of gettextKhem Raj2015-02-211-1/+1
| | | | | | | | | | Lets try to use musl version of libintl and see how far we get Change-Id: I0259049eb6461ab9b579c7f3ad401fefede24621 (From OE-Core rev: 4ed94affbce657db58c5099c8882a8d0292abaf1) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-tools: add PACKAGECONFIG for kmodRobert Yang2015-02-211-1/+2
| | | | | | | | | | | Fixed: lttng-tools-2.6.0: lttng-tools-ptest rdepends on libkmod, but it isn't a build dependency? [build-deps] lttng-tools-2.6.0: lttng-tools rdepends on libkmod, but it isn't a build dependency? [build-deps] (From OE-Core rev: a79d489a2fa532e6f87fe3cf0b55485fb08fd72e) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-compare: update Rename-rpm-check.sh-to-pkg-diff.sh.patchRobert Yang2015-02-211-17/+20
| | | | | | | | | | | The patch can't be applied by "git am -3" with newer version of git (such as 2.0.1), and can't be applied by "git am/apply" with any version, now fix it (From OE-Core rev: 14990de8c7481c3aaf77174a7541d5bfb9a7411d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/package_manager: Performance tweak in regex usageRichard Purdie2015-02-211-3/+3
| | | | | | | | | | | | | Profiling a core-image-sato-sdk rootfs, we're spending over 40s compiling the same regex over and over again, roughly around 5 million times. This is suboptimal, fix for a 40s improvement on a 18.5minute task execution time. (From OE-Core rev: d0244702752f54fb74be427af1663e46bfff9a5d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: Add a patch to speedup mkfsRichard Purdie2015-02-212-0/+53
| | | | | | | | | | | See the patch description, this adds a tweak to an algorithm to improve core-image-sato-sdk mkfs time from over 8 minutes to about 35s. Needs discussion upstream but seems reasonable for our uses of it. (From OE-Core rev: 468fa9a7fac86bb0fcd3cbd18dc1492b57ca25f3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-armv7a.inc, tune-arm920t.inc: Fix PACKAGE_EXTRA_ARCHSMartin Jansa2015-02-212-2/+2
| | | | | | | | | | | | | * each DEFAULTTUNE with thumb enabled should list it's arm variants in PACKAGE_EXTRA_ARCHS, otherwise packages which force arm ISA won't be found in do_rootfs * armv7athf-neon-vfpv4 was missing its own PACKAGE_ARCH and also the arm variant (From OE-Core rev: fd7f3cd9affbfb9ce483a5a1d6054da2365fcb0e) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* feature-arm-thumb.inc: respect ARM_INSTRUCTION_SET when adding thumb suffixMartin Jansa2015-02-213-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * this means that recipes with ARM_INSTRUCTION_SET explicitly changed to arm will be built in feed without thumb suffix, the same does apply for workdir, e.g. after "bitbake glib-2.0" you can see: tmp-glibc/work/armv5e-oe-linux-gnueabi: glib-2.0 glibc glibc-initial tmp-glibc/work/armv5te-oe-linux-gnueabi: acl db gdk-pixbuf kmod .... and tmp-glibc/deploy/ipk: all armv5e armv5te qemuarm * feed config should be ok, because all default DEFAULTTUNEs always include "arm" variants of all supported PACKAGE_ARCHs * for more details see http://lists.openembedded.org/pipermail/openembedded-core/2014-April/091960.html the toolchain path issues were resolved in 1.8 * add ARM_INSTRUCTION_SET = "arm" to glibc-collateral.inc and comment in glibc.inc to fix glibc-locale and glibc-scripts build (From OE-Core rev: 3e760031f91fb87c3e2f62b77a117eb41164f259) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kexec-tools: fix build failure on aarch64_be architectureFathi Boudra2015-02-211-62/+40
| | | | | | | | | | | | * refresh/cleanup the patch to apply cleanly on 2.0.9 * get rid of configure - it's autogenerated * configure.ac: use aarch64* wildcard (From OE-Core rev: 66457319e4050fee569aeccd1fe98fbf9f046f02) Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xorg-font-common: fix sysroot injection for encoding mapsRichard Tollerton2015-02-211-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | The xorg font builds use `pkg-config --variable=mapdir fontutil` to locate encoding maps. This variable ought to be sysroot-relative, but neither pkg-config nor font-util nor the fonts themselves provide any facility to add the sysroot back in. We're presently adding the sysroot by by twiddling MAPFILES_PATH in configure.ac. This is broken; it's actually defined in aclocal.m4, because the definition is provided by fontutil.m4. Another (more speculative) criticism is that it also hardcodes a build-specific absolute path into builds which might (incorrectly) encode it into target-installable packages. A somewhat more robust, focused, and clear solution is to override UTIL_DIR on the make command line. (UTIL_DIR, not MAPFILES_PATH, is what is actually referenced in the build.) (From OE-Core rev: 5cd320d8d21cd784b32f12a6944dc647a75abf94) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* font-util: remove MAPFILES_PATH overrideRichard Tollerton2015-02-211-4/+0
| | | | | | | | | | | | | | | | | | | | | MAPFILES_PATH is a configuration variable that is used by packages using font-util, which tells those packages how to compute it in fontutil.m4. Presently, we're manually twiddling things so that MAPFILES_PATH will consult the native sysroot, when building under *any* architecture. This complicates building other packages immensely, and also generates broken on-target packages, because the contents of font-util-dev will reference the native sysroot on the build machine (!). We don't even need to twiddle MAPFILES_PATH anymore so just delete it. This code also had a path bug (referencing /usr/lib/pkg-config instead of /usr/lib/pkgconfig) which is also fixed by deletion. (From OE-Core rev: 4199703db82d79408e0575e1332ad79375e14c39) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* font-util: stage encoding maps into sysrootBen Shelton2015-02-211-0/+5
| | | | | | | | | | | | | | | | | font-util installs encoding maps into /usr/share/fonts/X11. This path may not exist on the host (many distros install these into /usr/share/fonts/util) so they must exist in the sysroot in order for e.g. `pkg-config --variable=mapdir fontutil` to work correctly. However, currently /usr/share/fonts is explicitly not installed into sysroots, so the encoding maps were not getting found. Fix this by explicitly staging ${datadir}/fonts/ into the sysroot. (From OE-Core rev: a1598266c828ad0b73df971b22d6a2e3e1dd5cab) Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg: fix systemd unit installationRoss Burton2015-02-211-6/+2
| | | | | | | | | | | SYSTEMD_SERVICE doesn't need to be set conditionally, and units should be installed if the systemd DISTRO_FEATURE is enabled, not if sysvinit isn't enabled. (From OE-Core rev: bb8a7b906204b25f07fe568883c2d605593c323c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "kernel-arch.bbclass: add arm64 support to U-Boot architecture map"Nathan Rossi2015-02-211-1/+0
| | | | | | | | | | | | | | | | This reverts commit 0b891265716c414ade29d587fc1a3c4ea7beadbe. U-Boot does support AArch64, this however was only added to newer versions of U-Boot and at the time of this original commit the U-Boot in OE-Core did not support the 'arm64' architecture. OE-Core now has a newer version of U-Boot for the mkimage recipe and thus supports the 'arm64' architecture. (From OE-Core rev: fd8158134f3d7a7c795c818cc50eb2858a6cae06) Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* logrotate: 3.8.8 -> 3.8.9Robert Yang2015-02-214-48/+60
| | | | | | | (From OE-Core rev: 32848c7015f5d70c4245a9b1bb77c21faef8653d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-gitdb: 0.6.1 -> 0.6.4Robert Yang2015-02-211-2/+2
| | | | | | | (From OE-Core rev: 66be4fc8bd08df1c2807a61eebbae912cf07157d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-git: 0.3.3 -> 0.3.6Robert Yang2015-02-211-2/+2
| | | | | | | (From OE-Core rev: 8846e5a1896bc2083a326cc542d2cdde83b915da) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* git: 2.2.1 -> 2.3.0Robert Yang2015-02-213-11/+12
| | | | | | | (From OE-Core rev: 92a27c29570541564d65bf43325a333960b40183) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cups: 2.0.1 -> 2.0.2Robert Yang2015-02-214-41/+6
| | | | | | | | | | Removed the patch since upstream has fixed it: 0001-test-ippserver.c-check-avahi-before-use.patch (From OE-Core rev: e1a8de7d55710199d357c88c22f3f1887d562b61) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* quilt: 0.63 -> 0.64Robert Yang2015-02-213-4/+4
| | | | | | | | | | quilt-0.63.inc -> quilt.inc: we don't have multiple quilt-xxx.inc, so use quilt.inc rather than quilt-0.63.inc. (From OE-Core rev: 941be822ee7772b70fe78e6b61278bb8567bc905) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernelshark: Update to version 2.5.3Ben Shelton2015-02-212-37/+11
| | | | | | | | | | | | | | | | | | | | | | | | Update to version 2.5.3 to match trace-cmd. Changes include: - Remove kernelshark-fix-syntax-error-of-shell.patch (the syntax error is no longer present in the new version). - Specify bindir_relative and libdir in EXTRA_OEMAKE as in the trace-cmd recipe so files get installed to the right place. Additionally, remove unnecessary EXTRA_OEMAKE options. - Fix up the do_install steps to remove the plugins directory; that directory now lives under /usr/lib. - Set NO_PYTHON=1 because building the ctracecmd Python module requires swig, which is not available in oe-core. (From OE-Core rev: 2f177644dab083bc5306bce1bf2ff2ef8851c862) Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* trace-cmd: Update to version 2.5.3Ben Shelton2015-02-214-101/+6
| | | | | | | | | | | | | | | | | | | | | | | Updating adds new features including the very useful 'profile' option. Changes include: - Remove addldflags.patch (already upstream in the new version). - Remove make-docs-optional.patch (docs are built in a separate target in the new version). - Update SRC_URI, SRCREV, PR, and PV in the .inc file and don't override them in the recipe. - Fix a typo in LIC_FILES_CHECKSUM so 'endline' is properly defined. - Drop PR. (From OE-Core rev: 30eba39bd3b915477c584d8bebd194446497175e) Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/parselogs: Add exception for new mips error messageRichard Purdie2015-02-211-0/+1
| | | | | | | | The 3.19 kernel introduces this error, ignore it for now. (From OE-Core rev: 2a0a14275ca00b2d3ca867c82548a41e3bb10986) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: warn when a generated BSP description is usedBruce Ashfield2015-02-211-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | The meta data (in tree or out of tree) that describes a BSP, its patches and configuration is not always available when a new/default or manually configured machine is built. When this happens, the tools generate a skeleton BSP and use a architecture defconfig for the build. If this is by design, the build is typically sane and everything works fine. If an existing BSP description was expected, chances are that the resulting kernel will not be correct. To avoid surprising the user when a default/skeleton BSP is used for the build, we can make it obvious to the user by emitting a warning like the following: WARNING: [kernel]: An auto generated BSP description was used, this normally indicates a misconfiguration. Check that your machine (myqemux86-64) has an associated kernel description. [YOCTO: #3383] (From OE-Core rev: f4a460afc4e2676cbf1daaa1d6723da9e6146526) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: introduce 3.19 versioned recipesBruce Ashfield2015-02-212-0/+60
| | | | | | | | | | | | Introducing the v3.19.x recipes for the validated linux-yocto kernel. Build, boot and sanity testing was performed on qemu for all major architectures. (From OE-Core rev: 329a028bec428e8dc8cf3420c6e462de2898c8aa) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: remove 3.10 and 3.17 recipesBruce Ashfield2015-02-215-146/+0
| | | | | | | | | | | | | In accordance with the kernel release criteria we support the latest mainline kernel + the last LSTI kernel + a development kernel. 3.19 will be introduced as the latest mainline, and 3.14 is the released LTSI kernel, which means that we remove the 3.10 and 3.17 variants. (From OE-Core rev: 19203a95f4b65e0a009a738fb4fc216e985a0835) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: make kernel configuration audit user visibleBruce Ashfield2015-02-213-8/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After a linux-yocto style kernel is configured, a kernel configuration audit is executed to detect common errors or issues with the config. This output used to be visible, but was made less obvious to not alarm users unnecessarily (since some configuration issues are acceptable). There are some classes of configuration issue that are worth being visible, and that is specified configuration values that do not make the final .config. These dropped options can result in any number of runtime failures, so flagging them at build time makes sense. The visibility of auditing is controlled by KCONF_AUDIT_LEVEL: 0: no reporting 1: report options that are specified, but not in the final config 2: report options that are not hardware related, but set by a BSP The default level is 1, with level 2 and above being for BSP development only. If these conditions are detected, warnings will be generated as follows: WARNING: [kernel config]: specified values did not make it into the kernel's final configuration: Value requested for CONFIG_SND_PCSP not in final ".config" Requested value: "CONFIG_SND_PCSP=y" Actual value set: "" or WARNING: [kernel config]: BSP specified non-hw configuration: CONFIG_BLOCK CONFIG_CFG80211_WEXT CONFIG_CORDIC CONFIG_CRC8 CONFIG_EFIVAR_FS CONFIG_EFI_PARTITION CONFIG_NET CONFIG_NETDEVICES CONFIG_PARTITION_ADVANCED CONFIG_WEXT_CORE CONFIG_WEXT_PROC CONFIG_WIRELESS At this point thse are only a warnings, since there needs to be time for layers and configuration fragments to be validated against this new check. [YOCTO: #6943] (From OE-Core rev: ad4d59495194b37bc510e9891bd14c0a2ac30dba) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to 3.19Bruce Ashfield2015-02-213-8/+8
| | | | | | | | | Updating the libc-headers now that the kernel has released. (From OE-Core rev: b3721560fe523c144690ebfeb203b3735d0f6843) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Update to glibc 2.21 release tagDan McGregor2015-02-202-7/+5
| | | | | | | | (From OE-Core rev: 530565c6cb77319f4cc49edeea6fec6be997415d) Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-17 05:35:10 +0000