summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFiles
2014-12-21siteinfo: account for 32 and 64 bit armJoe Slater4
Pull wordsize related items from arm-common and put in arm-32. Leave them as they were. Copy arm-32 to arm-64 and comment out all variables. Re-define to correct values leaving items which do not appear to be used undefined. Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21Add machine qemuarm64Kai Kang2
Add machine qemuarm64. The configure files are derived from linaro. Update: * rename genericarmv8 to qemuarm64 for coordination in oe-core * include qemu.inc then remove common part of config * disable using autoserial * move arch-armv8.inc from machine/include/arm64 to machine/include/arm [YOCTO #6487] Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21linux-yocto: depend on libgcc for aarch64Kai Kang1
Make aarch aarch64 kernel depend on libgcc. In arch/arm64/Makefile, it adds LIBGCC to libs-y: LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name) libs-y += $(LIBGCC) In file Makefile in top directory, libs-y is assigned to to var KBUILD_VMLINUX_MAIN. It uses script link-vmlinux.sh to link vmlinux.o, and when execute function vmlinux_link() in link-vmlinux.sh, KBUILD_VMLINUX_MAIN is passed to ${LD}. If build without libgcc, the value of LIBGCC is just libgcc.a without parent directory. linux-yocto fails to build: | LD vmlinux.o | aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or directory Add libgcc to aarch64 kernel dependency. Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21python-2.7-manifest.inc: add stdlib argparse moduleMaciej Borzecki2
Adding argparse module from Python's standard library. The module has replaced previous python-argparse package that was build using source that are not part of Python 2.7 release. Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21python-argparse: remove external argparse moduleMaciej Borzecki1
Python argparse module is a part of a standard library since Python 2.7 release. Remove externally built module in favor of the stdlib one. Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21opkg-utils: Update SRCREVPaul Barker1
The new upstream commit incorporates the following fix to update-alternatives from Chen Qi <Qi.Chen@windriver.com>: update-alternatives: avoid double slash problem The link path stored by update-alternatives should always be absolute and so we do not need to add an additional slash when joining to $OPKG_OFFLINE_ROOT. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21byacc: Upgrade to 20141128Chong Lu1
Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21cups: Upgrade to 2.0.1Chong Lu2
Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21less: Upgrade to 471Chong Lu1
Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21devtool: add QA testsPaul Eggleton1
Add some QA tests for devtool (and recipetool). These aren't comprehensive but at least they are a start, and have already helped me catch and fix a number of regressions. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21scripts/devtool: Support deploy/undeploy functionJunchun Guan1
Deploy recipe output files to live target machine using scp Store the files list and target machine info in localhost if deployment is done Undeploy recipe output files in target machine using the previous deployment info [YOCTO #6654] Signed-off-by: Junchun Guan <junchunx.guan@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21scripts/devtool: add development helper toolPaul Eggleton3
Provides an easy means to work on developing applications and system components with the build system. For example to "modify" the source for an existing recipe: $ devtool modify -x pango /home/projects/pango Parsing recipes..done. NOTE: Fetching pango... NOTE: Unpacking... NOTE: Patching... NOTE: Source tree extracted to /home/projects/pango NOTE: Recipe pango now set up to build from /home/paul/projects/pango The pango source is now extracted to /home/paul/projects/pango, managed in git, with each patch as a commit, and a bbappend is created in the workspace layer to use the source in /home/paul/projects/pango when building. Additionally, you can add a new piece of software: $ devtool add pv /home/projects/pv NOTE: Recipe /path/to/workspace/recipes/pv/pv.bb has been automatically created; further editing may be required to make it fully functional The latter uses recipetool to create a skeleton recipe and again sets up a bbappend to use the source in /home/projects/pv when building. Having done a "devtool modify", can also write any changes to the external git repository back as patches next to the recipe: $ devtool update-recipe mdadm Parsing recipes..done. NOTE: Removing patch mdadm-3.2.2_fix_for_x32.patch NOTE: Removing patch gcc-4.9.patch NOTE: Updating recipe mdadm_3.3.1.bb [YOCTO #6561] [YOCTO #6653] [YOCTO #6656] Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21scripts: add scriptutils modulePaul Eggleton1
Add a utility module for scripts. This is intended to provide functions only really useful before bitbake has been found (or only of particular interest to scripts). At the moment this includes functions for setting up a logger and for loading plugins. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21scripts/recipetool: Add a recipe auto-creation scriptPaul Eggleton4
Add a more maintainable and flexible script for creating at least the skeleton of a recipe based on an examination of the source tree. Commands can be added and the creation process can be extended through plugins. [YOCTO #6406] Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21classes/externalsrc: set do_compile as nostampPaul Eggleton1
Most of the time what you want when using this class is for do_compile to execute more than just once - every time the source changes would be ideal, but that's a little tricky to accomplish. Thus, set do_compile as nostamp to get something close. Note that in order to be effective this also requires the change to bitbake that causes nostamp task signatures to change on each execution. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21oeqa/utils: make get_bb_var() more reliablePaul Eggleton1
* Enable querying exported variables * Use strip() to remove quotes so any internal quotes are not disturbed Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21kernel-devsrc: Ensure we have a dependency on the actual sourceRichard Purdie1
Tthe kernel populate_sysroot can come from sstate, we need the full source here. We therefore depend on the configure task which isn't covered by sstate to ensure we get the right set of files. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21lib/oe: add recipeutils modulePaul Eggleton1
Add a module to help provide utility functions for dealing with recipes. This would typically be used by external tools. Substantial portions of this module were borrowed from the OE Layer index code; other functions originally contributed by Markus Lehtonen <markus.lehtonen@intel.com>. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21lib/oe/patch: add support for extracting patches from git treePaul Eggleton1
When patches from a recipe have been written out to a git tree, we also want to be able to do the reverse so we can update the patches next to the recipe. This is implemented by adding a comment to each commit message (using git hooks) which we can extract later on. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21lib/oe/patch.py: abort "git am" if it failsPaul Eggleton1
If we don't do this, you may still be in the git am resolution mode at the end of applying patches, which is not desirable. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21lib/oe/patch: use --keep-cr with git amPaul Eggleton1
Preserving carriage returns is important where the patch contains them. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21lib/oe/patch: auto-commit when falling back from git amPaul Eggleton1
When PATCHTOOL = "git", if we're not able to use "git am" to apply a patch and fall back to "git apply" or "patch", it is desirable to actually commit the changes, attempting to preserve (and interpret) the patch header as part of the commit message if present. As a bonus, the code for extracting the commit message is callable externally in case it is useful elsewhere. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21lib/oe/patch: fall back to patch if git apply failsPaul Eggleton1
When PATCHTOOL = "git", git apply doesn't support fuzzy application, so if a patch requires that it's better to be able to apply it rather than just failing. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21classes/package: move read_shlib_providers() to a common unitPaul Eggleton2
This allows us to use this function elsewhere in the code. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21meta-environment: don't mark tasks as nostampPaul Eggleton1
With siggen being changed to alter the signature of nostamp tasks on the fly, having these tasks as nostamp results in the SDK being rebuilt every time, which is not desirable. In any case this is just legacy from the days before we used signatures to take care of ensuring these tasks get re-run when they need to be. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21core-image-sato-sdk: Use kernel-devsrc to ensure kernel module builds workRichard Purdie1
With the move of the kernel source to the kernel-devsrc, we need this package to ensure the kernel module sanity tests made on core-image-sato-sdk continue to pass. Therefore update the name of the package included in the image. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21boot-directdisk: Use kernel from DEPLOY_DIR_IMAGE, not sysrootRichard Purdie1
After the recent kernel changes, this avoids failures like: DEBUG: Executing shell function build_boot_dd install: cannot stat '/home/pokybuild/yocto-autobuilder/yocto-worker/build-appliance/build/build/tmp/sysroots/qemux86-64/usr/src/kernel/bzImage': No such file or directory WARNING: exit code 1 from a shell command. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21bootimg: Use deploy artefacts, not STAGING_KERNEL_DIRRichard Purdie1
bzImage is no longer in STAGING_KERNEL_DIR. Rather than add it back, depend on the kernel deploy task and find it in DEPLOY_DIR_IMAGE. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21kernel: Fix non linux-yocto buildsRichard Purdie1
After the recent kernel changes, non linux-yocto builds stopped working properly for two reasons: a) ${S} was being reset to ${WORKDIR}/git for example and STAGING_KERNEL_DIR did not contain the source b) Most builds were using ${B} == ${S} This patch adds a fixup to the unpack function to handle the case where ${S} != ${STAGING_KERNEL_DIR} and also set up the infrastrcture so that B != S for kernel builds from now on. The kernel build system is one of the best for supporting this and there is no good reason not to take advantage of it. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21kernel-devsrc: Ensure we don't race against do_make_scripts from ↵Richard Purdie1
module-base.bbclass do_install for kernel-devsrc can race against do_make_scripts from module-base.bbclass. Since there is a lock there to guard against concurrency already, we can just use it here to avoid a race. Ultimately, this can all likely be much more streamlined but this resolves the immediate build failures. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21kernel-devsrc: Handle ppc crtsaves.o explictly for nowRichard Purdie1
Resolve kernel module build failures for qemuppc by including crtsaves.o. I'm not particularly happy to be doing this, it should perhaps be contained in the kernel-dev package. Until the overlap between kernel-devsrc and kernel-dev is resolved, this at least removed the regressions. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20kernel-devsrc: Inherit module-baseRichard Purdie1
As a "normal" recipe, mulitlib would try and extend it for multilibs. By inheriting module-base, we can avoid this since we now look more 'kernel' like. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20kernelsrc.bbclass: Ensure fetch/unpack/patch tasks don't runRichard Purdie1
In particular this removes a race condition where a ${S}/patches directory could be created by do_unpack. This confuses kern-tools. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20linux-libc-headers: Upgrade 3.17 -> 3.17.7Richard Purdie3
Whilst we don't usually take linux-libc-headers point release, 3.17.3 fixes a userspace header issue which caused gdb to fail to build on mips. We therefore may as well upgrade to the latest point release. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20linux-libc-headers: update to 3.17Bruce Ashfield3
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20socat: fix compile erorr against 3.17+ kernel headersBruce Ashfield2
With the linux 3.17 kernel socat's configure detects the wrong include for errqueue.h which results in a compilation error. By backporting the gentoo patch from: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/socat/files/socat-1.7.2.4-linux-3.17.patch Fixes the build issue Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20linux-yocto/3.14: update to 3.14.26, integrate ltsi and -rt updatesBruce Ashfield3
Updating the 3.14 tree to the latest korg 3.14.26, as well as integrating 3.14 LTSI content, and refreshing preempt-rt. Minor conflict resolutions were performed between ltsi, stable and -rt Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20linux-yocto/3.10: update to v3.10.62Bruce Ashfield3
Updating to the latest korg -stable update for the 3.10 series. Minor merge conflict resolution was done with the standard/ltsi and standard/preempt-rt branches. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20linux-yocto/3.17: update to v3.17.6Bruce Ashfield2
Integrating the latest korg -stable update for v3.17 Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20lttng-modules: fix mm_compaction_isolate_template buildBruce Ashfield2
linux-stable integrated the 3.16 commit f8c9301fa5a2a [mm/compaction: do not count migratepages when unnecessary] with the 3.14.25 update. So we have to update the lttng-module linux version codes to use the new definition in builds greater than 3.14.24 or 3.16. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20linux-yocto/3.14: update to v3.14.24Bruce Ashfield3
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20linux-yocto/3.10: update to v3.10.59Bruce Ashfield3
Updating to the latest 3.10 -korg stable update. We also bring in a meta change for the valley island IO configuration. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20linux-yocto/3.17: update to v3.17.2Bruce Ashfield2
Updating to the korg 3.17.2 -stable release. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20linux-yocto/3.17: update to v3.17.1Bruce Ashfield2
Updating to the kver to the latest korg stable update. This fixes some important bugs (as well as the usual mix of more minor ones), in particular libata bugs and SSD corruption issues are fixed. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20kernel: Clean ${S} before unpackRichard Purdie1
Currently unpack just forces sources over the current files. This change ensures ${S} is cleaned out before sources are unpacked. This resolves issues seen when upgrading to the new kernel class changes. Ultimately, this should probably move to base.bbclass but one step at a time, this solves an immediate problem blocking the other patches from merging. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20sanity: TMPDIR ABI change for kernel processRichard Purdie2
The kernel source is being moved into the sysroot, to do this and preserve previous builds, we need to change the TMPDIR ABI and provide a function to uninstall all kernels from the sysroot. This change adds code to do that and increases the ABI number. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20kernel-yocto: make sure git tags get dereferenced properly in do_patch()Jeff Wang1
Commit 92c1ece6c347030d48995a36f4c67861356e59d3 causes the test in do_patch() in kernel-yocto.bbclass to fail if ${machine_srcrev} is an annotated tag. The check is meant to ensure that ${machine_srcrev} is an ancestor of HEAD, but if ${machine_srcrev} is a tag, then "$(git rev-parse --verify ${machine_srcrev})" evaluates to the SHA of the tag instead of what it's pointing to. Replacing "$(git rev-parse --verify ${machine_srcrev})" with "$(git rev-parse --verify ${machine_srcrev}~0)" fixed the problem by finding the object pointed to by the tag, and not the tag itself. This also works for commit IDs that are not tags, hence is safe in a scenarios. Jeff Wang <jeffrey.wang@ll.mit.edu> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20kernel-yocto: fix non-git buildsBruce Ashfield1
The ability to build non-git repositories was broken by two changes: - The existence of an empty 'patches' directory created during the unpack phase. This dir was incorrectly identified as a valid meta directory and broke the build. By ensuring that it is removed before creating the empty repository, it will no longer be found instead of the real meta directory. - The attempt to reset the git repository to a specific SRCREV when no SRCREV was provided. By checking for a SRCREV of 'INVALID', we avoid any processing and failed git operations. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20lttng/perf: depend on virtual/kernel:do_installBruce Ashfield2
To ensure that the minimal environment has been created for out of tree module builds, perf and lttng should depend on the do_install task of the kernel. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-12-20images: introduce core-image-kernel-devBruce Ashfield1
When building a new kernel, or testing and update to the kernel there are a set of packages that are sensitive to APIs, build system and other changes associated with the kernel. After building this recipe, we can be reasonably sure that a new kernel package and coupled userspace have been built, installed and tested via a single image. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-10 22:05:20 +0000