summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* devtool: modify: use correct local files directory nameMarkus Lehtonen2015-10-011-1/+1
| | | | | | | | | | | The name of the directory for local source files under srctree is 'oe-local-files', not 'local-files'. Fixes a bug that slipped through in b7ab82485e4514e07ab8a76e554da27ddc92e6c0. (From OE-Core rev: 68cbe684fe6d8fe3a44e47ed85837d09077df6d5) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xuser-account: Take over xuser specific D-Bus policyJussi Kukkonen2015-10-015-47/+15
| | | | | | | | | | | Move connmans xuser-related D-Bus policy to a separate file that xuser-account installs: This way connman does not need to depend on xuser-account. Add policies for bluez and ofono in the same file. (From OE-Core rev: 9f37ce18b7d79135a67474187b6119980e0130ae) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: Use upstream D-Bus policyJussi Kukkonen2015-10-012-20/+2
| | | | | | | | | | | | | | | The Bluez D-Bus policy is much too open and affects not just bluez but all system services: Use upstream policy configuration instead. This change has a chance of affecting other D-Bus services: the bug that is fixed here may have hidden problems in other policies. [YOCTO #8414] (From OE-Core rev: 0f6f87c60a6ffeff6b3f53d25f4023749103e262) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest: run-ptest not required to run do_install_ptestIan Ray2015-10-011-5/+5
| | | | | | | | | | | | Modify do_install_ptest_base to run do_install_ptest and install the Makefile irrespective of the presence of ${WORKDIR}/run-ptest. This change allows "ptest-aware" packages to install run-ptest as part of the make machinery. (From OE-Core rev: 2055517d91e0c55ed108d3a6f52abd1d2c6824b2) Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distrodata: Take account proxies on distrodata tasksLeonardo Sandoval2015-10-012-50/+69
| | | | | | | | | | | | | | | | | | | | | | | Proxies defined in the enviroment where not taken into account on the distrodata tasks. This commit implied passing the datastore into the distro_check library and context manager for the urllib.urlopen function. One way to run distrodata tasks is using 'universe' as target and the 'all' distrodata task: $ bitbake universe -c distrodataall $ bitbake universe -c distro_checkall $ bitbake universe -c checklicenseall Logs are located under TMPDIR/log [YOCTO #7567] (From OE-Core rev: 7d1c3470bb06e43245ccb7f067121de606506430) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: update-recipe: enable var history trackingMarkus Lehtonen2015-10-012-3/+3
| | | | | | | | | | | | Enable variable history tracking so that the variables are updated in the correct file - i.e. in the file they are already defined. [YOCTO #7715] (From OE-Core rev: b54796d013c562972e962126400503085281b425) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/selftest/yoctobsp: Basic tests for yocto-bsp scriptLeonardo Sandoval2015-10-011-0/+39
| | | | | | | | | | | | Unit tests include listing properties and creating BSP using the default kernel, both tests done for supported architectures. Test can be manually executed with: $ oe-selftest --run-tests yoctobsp.YoctoBSP (From meta-yocto rev: e84fb6fe8219f874b0157bdf53489bbb5f7f81cb) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/lib/bsp/engine: Indent the karch properties when stored into a fileLeonardo Sandoval2015-10-011-1/+1
| | | | | | | | | | Make a bit more human-friendly the karch properties when storing into a file. (From meta-yocto rev: 39292d397658a8e30c73d4cdaced66cb0efa8380) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: Update templates to 4.1 kernelLeonardo Sandoval2015-10-0122-15/+535
| | | | | | | | | | Add 4.1 kernel support. Old bbapends were not removed, so user still have the option for 3.14/3.19 kernels. (From meta-yocto rev: f47ea7224765a3c3da3a9e0a989173b2b1950cfc) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scrips/lib/bsp/engine: List properties to stdout when output parameter is ↵Leonardo Sandoval2015-10-011-2/+2
| | | | | | | | | | | | | omitted When user wants to output the list of properties for a corresponding architecture and the output parameter is given (--o/-outfile), there is no need to show the properties into the console. (From meta-yocto rev: bd133e2a6e626b4158f5a303d85205de9c66e8f2) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/yocto-bsp: Exit successfully when asking for helpLeonardo Sandoval2015-10-011-1/+1
| | | | | | | | | | When user asks for help, the command should not exit with non-zero status (failure), so removing the non-zero value on the system exit call. (From meta-yocto rev: 98970326fb2f08e684cfc856103b2f9110c9f4fb) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-yocto-bsp: bump to linux-yocto 4.1 for the non-x86 BSPsKevin Hao2015-10-014-3/+12
| | | | | | | | | | Boot test for all these boards. (From meta-yocto rev: 577768063124771d7469b1f860e5291cd8e019fc) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: siggen: Make it clear why nostamp tasks signatures don't matchRichard Purdie2015-10-011-1/+9
| | | | | | | | | | | | If you run bitbake-diffsigs against two differing sigdata files from nostamp tasks it shows no difference despite the differing checksum. Change the code so this shows up as a nostamp 'taint' and at least makes the issue clearer to the end user. (Bitbake rev: 97679d18955dadaa34f9450564e44da99984d140) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Add handling of virtual/xxx provider mappingsRichard Purdie2015-10-011-0/+9
| | | | | | | | | | | | This firstly prints debug messages which show how bitbake decided to resolve the virtual/xxx providers which is useful for debugging. If the siggen has a tasks_resolved() method, it calls this, passing in the mappings, allowing that to do things with the resolved names. (Bitbake rev: d473fc84acddfd69a7207affcd89f65ea2ecf730) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: taskdata: Add a function to return the virtual/ mapping dataRichard Purdie2015-10-011-0/+12
| | | | | | | | | | | | | When building an execution task graph, bitbake does resolve virtual/xxx namespaces into specific providers. This data isn't exported anywhere however. This adds a function so that runqueue can at least retrieve this data which can then be used by the system. (Bitbake rev: ce51a51482d0900060512b24503714a730d72266) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cookerdata: Rename BBPKGS -> BBTARGETSRichard Purdie2015-10-011-2/+2
| | | | | | | | | | | | | | | | | | BBPKGS is a confusing name from before we tried to straighten out our terminology. Its also a mostly unknown variable that isn't in wide use. I've been asked about it recently and before people start relying more heavily on it, I'd like to rename it BBTARGETS which better describes what it does. Its not currently in the manuals, I'd prefer to document it under the better name. I've not provided any migration path for the variable since I believe its unused currently. It allows the targets to built to be specified from a conf file in addition to those on the commandline. (Bitbake rev: f60c6a2172bceeb5682dcb738a02c4bf26176566) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-worker: Guard against multiprocessing corruption of event dataRichard Purdie2015-10-011-0/+9
| | | | | | | | | | | | | | | | | | | | In the forked child, we may use multiprocessing. There is only one event pipe to the worker controlling process and if we're unlucky, multiple processes can write to it at once corrupting the data by intermixing it. We don't see this often but when we do, its quite puzzling. I suspect it only happens in tasks which use multiprocessng (do_rootfs, do_package) and is much more likely to happen when we have long messages, usually many times PAGE_SIZE since PAGE_SIZE writes are atomic. This makes it much more likely within do_roofs, when for example a subprocess lists the contents of a rootfs. To fix this, we give each child a Lock() object and use this to serialise writes to the controlling worker. (Bitbake rev: 3cb55bdf06148943960e438291f9a562857340a3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/wic: Use SetupLocal instead of SetupRichard Purdie2015-10-011-1/+1
| | | | | | | | | | | If we replace the code Setup method, we don't get the cleanup it performs and this just resulted in failures on the autobuilder due to a stale config fragment. Setup will call SetupLocal so this should be a safe and easy fix to resolve the auobuilder failures. (From OE-Core rev: 16957f5f1de0f1fb4052d5aef93ee10c893f4a38) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass: fix the bug of checking the existing sections in do_strip()Kevin Hao2015-10-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Ross reported the following waring when building edgerouter BSP: WARNING: Section not found: .comment The reason is that the testing of the existing sections in do_strip() returned the wrong value. Please see the following code in do_strip(): for str in ${KERNEL_IMAGE_STRIP_EXTRA_SECTIONS}; do { if [ "$headers" != *"$str"* ]; then bbwarn "Section not found: $str"; fi "$CROSS_COMPILE"strip -s -R $str ${KERNEL_OUTPUT} }; done The "*" doesn't have special meaning in the if string test, so it will return true even the $str is a substring of $headers. Fix this issue by replacing it with "! (echo "$headers" | grep -q "^$str$")". Reported-by: Ross Burton <ross.burton@intel.com> (From OE-Core rev: 4965f122ca67c0ff60dc60f7885db1ed9db909b4) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto_{3.14,3.19,4.1}: qemuarm enable virtio driversAníbal Limón2015-10-013-0/+3
| | | | | | | | | | | | | | | We are experimenting segfault in qemu arm SCSI driver because it's broken [1][2] so enable virtio drivers to use as default. [YOCTO #8060] [1] https://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00093.html [2] https://lists.nongnu.org/archive/html/qemu-devel/2010-07/msg01473.html (From OE-Core rev: e8e4cf4e830ee5c5f92dd8ab38c4072a3a43c411) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-internal: qemuarm enable usage of virtio devicesAníbal Limón2015-10-011-2/+12
| | | | | | | | | | | | | | | | | | | We are experiencing occasional segfaults in scsi sym53c8xx driver on qemuarm boot. There are some old discussions into the mailing lists [1] about the scsi problem and seems to be isn't fixed. We use virtio blk/net devices into qemuarm64 also are supported into qemuarm so change to use it because virtio devices are the best choice. [YOCTO #8060] [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8060#c10 (From OE-Core rev: bbfb3cd06e0ff5661ef3732ebfffa74b94400cd9) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnome-doc-utils: xslt - don't install MakefilesWenzong Fan2015-10-011-3/+0
| | | | | | | | | | | All the xml files under xslt will be installed by default, the buildtime stuffs that Makefile, Makefile.in, Makefile.am are not needed for target. (From OE-Core rev: 61240e9f7e40400d49a91a0f1f0446755bd17294) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* apr-utils: cleanup buildpaths for target stuffsWenzong Fan2015-10-011-0/+6
| | | | | | | | | | | * cleanup buildpaths from apu-1-config: - remove ${STAGING_DIR_HOST} from CC, CPP ... - set APU_SOURCE_DIR, APU_BUILD_DIR as empty (From OE-Core rev: d61e73a37f805fd56efda1a6cfe7262356fc6274) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* apr: cleanup buildpaths from target stuffsWenzong Fan2015-10-011-1/+8
| | | | | | | | | | | | | | * cleanup buildpaths from apr_rules.mk and apr-1-config: - remove ${STAGING_DIR_HOST} from CC, CPP ... - set APR_SOURCE_DIR, APR_BUILD_DIR as empty * install ${HOST_SYS}-libtool to sysroot only, it's required for building apache2 but not suitable for target. (From OE-Core rev: 44c1a6af03ce9b45e5bfd6956062aa2b3a1be741) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* curl: cleanup buildpaths from curl-configWenzong Fan2015-10-011-0/+5
| | | | | | | | | | | curl-config will be installed to target, cleanup buildpaths in it: * remove ${STAGING_DIR_HOST} from CC, CFLAGS ... (From OE-Core rev: 3e4978a534afc7fd4b82a044da8d9774cf09a4f0) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dropbear: fix key generation when systemd is in use and rootfs is readonlyAlexander Kanavin2015-10-012-3/+9
| | | | | | | (From OE-Core rev: 7e13fc603aa86219bf15e355ca9ea9275308cca5) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: tweak the key location for dropbear when rootfs is readonlyAlexander Kanavin2015-10-011-0/+11
| | | | | | | | | In the same way it's done for openssh. (From OE-Core rev: a4b91f5199dd4d1302484cbd972a484d36f7886f) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssh: fix sshd key generation when systemd is in use and rootfs is readonlyAlexander Kanavin2015-10-012-6/+19
| | | | | | | | | [YOCTO #8365] (From OE-Core rev: d5ea131fe94939daabee1afe8219683de259b7a3) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: when building a readonly rootfs, tweak ssh settings ↵Alexander Kanavin2015-10-011-12/+12
| | | | | | | | | | | regardless of init system in use Previously it was done only if sysvinit was in DISTRO_FEATURES. (From OE-Core rev: 8aa5c66a29c1394e0418e94bdd49e5b268ffc790) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-tools: Drop KERNELDIR referenceRichard Purdie2015-10-011-2/+0
| | | | | | | | | The source makes no reference to KERNELDIR any more and this make the recipe machine specific. Simply drop the unused reference. (From OE-Core rev: 21bad4c807acd4c596fcca8afeab737161fbbb39) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-ide-support: No need to mark as nostamp anymoreRichard Purdie2015-10-011-1/+0
| | | | | | | | | With the modern checksum infrastructure, this is no longer needed (much in the same way images no longer need this). (From OE-Core rev: 30e83bbc3f90b4cd4caf8ad7ca847267ae50cf7e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* adt-installer: No need to mark as nostampRichard Purdie2015-10-011-1/+0
| | | | | | | | | With the modern checksum infrastructure, this is no longer needed (much in the same way images no longer need this). (From OE-Core rev: db0ffc5a109c0b5e91f1fc67ac679bdc558c251f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distutils3: Avoid MACHINE specific checksumsRichard Purdie2015-10-011-0/+4
| | | | | | | | | | | | | | The MACHINE variable is used to handle sysroot paths within one of the patches to python3-native. In this context, it is relocation safe and the resulting packages should not have MACHINE specific checksums, therefore excluding MACHINE in this context is safe. This whole setup is ugly and ideally we should come up with a better way of handling this but at least allow a stop gap solution for now. (From OE-Core rev: be4e6ea8a92bd90f354f8c04eade39ccce8b73d5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer-omx: Improve variable expansion of ${S}Richard Purdie2015-10-011-2/+1
| | | | | | | | | | The way ${S} is expanded into CFLAGS means the recipe is marked as depending on the path within which its built. We can avoid this by avoiding the expansion which then allows reuse of the recipe from sstate. (From OE-Core rev: 560e778589afbc5da9a20bd0fbba09b910207604) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Exclude sstate-outputdirs flag from checksumsRichard Purdie2015-10-011-1/+1
| | | | | | | | | | | | | | | | This was making deploy tasks MACHINE specific since they place output into DEPLOY_DIR_IMAGE which contains MACHINE. On the plus side, this was accidentally ensuring the output was placed for each machine, on the downside it was triggering a rebuild every time for the different checksum. There is a better way to handle this which avoids the rebuild, see the following tweak to do_deploy to mark it as MACHINE specific in a different way. (From OE-Core rev: 59800189690f887e6f3e8c3139fa6a404b76ac71) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* deploy: Mark deploy tasks as MACHINE specificRichard Purdie2015-10-011-0/+1
| | | | | | | | | | This adds the markup to inform bitbake to rerun the deploy task per MACHINE. This makes sense since DEPLOY_DIR_IMAGE contains MACHINE. Doing it this way means the same artefact will be reused from sstate rather than rebuilt. (From OE-Core rev: 4052e0858d72505728c2a746fac935bf281903fd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Add SIGGEN exclusion for oprofile kernel dependencyRichard Purdie2015-10-011-0/+1
| | | | | | | | | | The oprofile kernel dependency is a simple RRECOMMENDS, it therefore doesn't have any interface constraints and doesn't need to rebuild every time the kernel changes. (From OE-Core rev: 0898361e4ca4b0c00d0470d130d24802f66c1064) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Improve siggen exclusion to handle virtual/libcRichard Purdie2015-10-011-3/+1
| | | | | | | | | | Now the system supports virtual/xxx in SIGGEN_ variables, convert this one to use virtual/libc instead of the hardcoded expansion which is error prone. (From OE-Core rev: d4a7a1b2d6bee1b6578cc7b56b6ca730ea453144) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* multilib_global: Add handling of SIGGEN variables for multilibRichard Purdie2015-10-011-5/+23
| | | | | | | | | | | | multilib task signatures turned out to have issues since SIGGEN_EXCLUDERECIPES_ABISAFE and SIGGEN_EXCLUDE_SAFE_RECIPE_DEP did not have multilib mappings. This adds those mappings in which in turn improves multilib task checksums to match the standard non-mulitlib versions. (From OE-Core rev: ea872b735c92a30d03cfa32953e060430e6f7f0b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/sstate: Add tasks_resolved handler for virtual/xxx mappingsRichard Purdie2015-10-011-0/+20
| | | | | | | | | | | | | | In SIGGEN_EXCLUDERECIPES_ABISAFE and SIGGEN_EXCLUDE_SAFE_RECIPE_DEP we really need to be able to use virtual/xxx namespaces but this currently doesn't work. To make this work, we need to translate them into the resolved providers. After such a hook was added to bitbake, we can add this translation here. (From OE-Core rev: 0a6d0d040ab7f885b667a34f4ddcc775d135c07c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/sstatetests: Add test that MACHINE doesn't change target sigsRichard Purdie2015-10-011-1/+46
| | | | | | | | | | When we change between two machines with the same tune, we shouldn't see rebuilds of binaries. This adds a test for this using the qemux86copy machine. We also extend the test to cover multilibs. (From OE-Core rev: df49d7a0f80673e73f753e8650cd88a086e77245) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-selftest: Add qemux86copy machineRichard Purdie2015-10-011-0/+3
| | | | | | | | | | I know Martin finds something like this useful for testing sstate signatures, this adds one to meta-selftest so we can use it from oe-selftest in the sstate tests there too. (From OE-Core rev: 7ed3364b7ca61b210fce5ed014ab700e24ee470b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/sstatetests: Add check for same sigs for SDKMACHINERichard Purdie2015-10-011-1/+11
| | | | | | | | | | | | Extend one of the sstate tests to also ensure that changing SDKMACHINE doesn't change the target task checksums. Also fix a typo and improve debugging by turning the diff filtering off in all cases (if the test fails, we want to full list). (From OE-Core rev: 24bb41f273148db023721804b98676a92f9a5f9c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* multilib.conf: Ensure MACHINE doesn't change target sigsRichard Purdie2015-10-011-0/+1
| | | | | | | | | Sysroot paths (which happen to contain MACHINE) should not cause the signatures to change every time MACHINE changes so exclude this from them. (From OE-Core rev: 5f3773e84332e9100b8739adf4831269329e0033) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-multilib-config: Ensure SDK_ARCH doesn't change target sigsRichard Purdie2015-10-011-0/+1
| | | | | | | | | | | Changing SDKMACHINE (which changes SDK_ARCH) shouldn't cause target task signatures to change. Exclude the dependency on SDK_ARCH for this reason. It only affects nativesdk builds and those already account for SDK_ARCH in the build WORKDIR paths. (From OE-Core rev: dae7c45fac1d877203f173842d43abc4883b808b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/package_manager: Handle empty package list in opkg caseRichard Purdie2015-10-011-1/+1
| | | | | | | | | | | | If you build buildtools-tarball with opkg as the package manager, it passes in an empty target packages list and fails. This allows the code to cope with an empty package list (in sync with the rpm backend). (From OE-Core rev: b460afb12bb16a4b56d800c953c5f5c7da0bff84) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/utils/decorators: Append the testname without the full pathLeonardo Sandoval2015-10-011-0/+4
| | | | | | | | | | | | | | | | | | | | | When getting the failures/errors/skipped lists, include the unit test without the full path. This issue was found on this scenario | test_1_logrotate_setup (oeqa.runtime.logrotate.LogrotateTest) ... FAIL | test_2_logrotate (oeqa.runtime.logrotate.LogrotateTest) ... ok Where test_1_logrotate failed and test_2_logrotate should not have run because @skipUnlessPassed("test_1_logrotate_setup") def test_2_logrotate(self): (From OE-Core rev: 8715beff7b910209627da3726b18b7abf801b557) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: fix multi-layer patch applicationBruce Ashfield2015-10-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Updating the kern-tools SRCREV to import the following fix: kgit-meta: resume after last applied patch When the auto-resume (resume point detection) was removed from the processing of a meta-series, it ignored the fact that a single patch series may in fact be processed a number of times. Two layers patching a kernel will generate two different runs on the same branch, which always start at patch one. This will obviously break with duplicate patches. To avoid this, we simply track the last patch applied, and explicitly tell the patch scripts where to start. This gets us resume functionality, without the overhead of resume point detection. (From OE-Core rev: 692f1333e257556e7462b2436dd60e865869349c) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/4.1: braswell bug fixesBruce Ashfield2015-10-013-10/+10
| | | | | | | | | | | | | | Updating the 4.1 SRCREVs to integrate the following DRM backports: a8abc111a96d drm/i915: Only wait for required lanes in vlv_wait_port_ready() 81354180432b Revert "drm/i915: Hack to tie both common lanes together on chv" d660fc117731 drm/i915: Work around DISPLAY_PHY_CONTROL register corruption on CHV 0e797e9cb717 drm/i915: Implement chv display PHY lane stagger setup (From OE-Core rev: 2ea7533b5d45bb459284dd1c3f81d4bcac88f882) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/4.1: update to 4.1.8 -stableBruce Ashfield2015-10-013-16/+16
| | | | | | | | | | There are some important fixes and CVEs in 4.1.8, so we update the SRCREVs to integrate the -stable changes. (From OE-Core rev: 0cd10fc32fd6a3faced69ef206271c8afde17533) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.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 13:03:44 +0000