summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ref-manual: Added gobject-introspection.bbclass description.Scott Rifenbark2016-04-181-0/+22
| | | | | | | (From yocto-docs rev: e6c40815c2a6ea3c94126ef43e586a01cb721ea8) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added reference for npm.bbclass.Scott Rifenbark2016-04-181-0/+14
| | | | | | | (From yocto-docs rev: 7bf6401ad16ad83743d82a3b7592f77237c453f8) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Fixed typo in the nopackages.bbclass descriptionScott Rifenbark2016-04-181-1/+1
| | | | | | | (From yocto-docs rev: c73d36e01b501471d24a174a8be77f1798d0ea5e) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added description for bash-completion.bbclassScott Rifenbark2016-04-181-1/+10
| | | | | | | (From yocto-docs rev: a3b29e84b5d521d70585b8a2a7bd989c643cd310) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added nopackages.bbclass description. Fixed stray typo.Scott Rifenbark2016-04-181-0/+9
| | | | | | | (From yocto-docs rev: aa34f219237d6490fc0061ecd0644d4093957729) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added description for the INSTALL_TIMEZONE_FILE variable.Scott Rifenbark2016-04-181-0/+16
| | | | | | | (From yocto-docs rev: 768935078510bcf4300ff5e05e87c9bed10a0cde) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the PREFERRED_PROVIDER variable with a note.Scott Rifenbark2016-04-181-0/+11
| | | | | | | (From yocto-docs rev: 5d3a3e9ea8670f784f9c06cb244a9d5981bb1e76) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Dropped references to the autotools_stage classScott Rifenbark2016-04-181-4/+2
| | | | | | | (From yocto-docs rev: f13f1925f1ea47a87730844109ed224b16c1f587) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, dev-manual: Scrubbed boot-directdisk and bootimg classesScott Rifenbark2016-04-183-64/+6
| | | | | | | | | | | | These classes have been removed. The bootimg class was sucked into the image-live class. I removed the reference sections to both classes and fixed the references throughout the manual set as needed. (From yocto-docs rev: 649d56b54987580039cbd52f54642112f810ffad) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the uninative.bbclass description.Scott Rifenbark2016-04-181-8/+17
| | | | | | | | | Dropped the "experimental" verbiage and added real detail. (From yocto-docs rev: ca63ab4bac2885037741afdc78ee307233159a2e) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Converted "meta-yocto" to "meta-poky"Scott Rifenbark2016-04-1810-54/+54
| | | | | | | | | Occurrences in many manuals and one figure. (From yocto-docs rev: 26d30cd162083c62216fb4ab526d0b231f453de1) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bsp-guide: Updated yocto-bsp create example output.Scott Rifenbark2016-04-181-8/+8
| | | | | | | (From yocto-docs rev: f764adf95f7dca7243cee7412035958962091205) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added the migration section for 2.1Scott Rifenbark2016-04-181-12/+540
| | | | | | | (From yocto-docs rev: ed1eec9139d8a9caf32f0cc896f651cafecece4f) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-project-qs, ref-manual: Upgraded minimum Git requirementScott Rifenbark2016-04-182-3/+3
| | | | | | | | | This minimum Git requirement is now version 1.8.3.1. (From yocto-docs rev: c68aa31442f7ac58a6f597f3074416afaab95882) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added rootfs-postcommands class description.Scott Rifenbark2016-04-181-0/+4
| | | | | | | (From yocto-docs rev: 237f8c8fbefc0ad753d47d891b24a49e0e0c6b5e) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the EXTRA_OEMAKE variable description.Scott Rifenbark2016-04-181-0/+6
| | | | | | | | | Provided information about the new default "". (From yocto-docs rev: 75ab9805614fc9501191eef0000c7a9214765392) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Updated "Additional Implementation Details" sectionScott Rifenbark2016-04-181-10/+34
| | | | | | | | | | | | | | | Fixes [YOCTO #5517] I added two package management system generic implementation details to the section. This brings the section up to speed as the definitive work on combining multiple versions of library files into one image. We no longer have to refer the reader to a separate wiki page. (From yocto-docs rev: 450e718ca1b853f332c4e607a5a76efd689f7769) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: lib/bb/utils: add docstring for contains()Ross Burton2016-04-181-1/+19
| | | | | | (Bitbake rev: e9174723ea6d0dff5f7f3042009761cf42284947) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ca-certificates: support ToyboxPatrick Ohly2016-04-182-0/+35
| | | | | | | | | | | "mktemp -t" is deprecated and does not work when using Toybox. Replace with something that works also with Toybox. (From OE-Core rev: 8d47d075ca02612fe16e403be1aa2079edc3ef5f) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oetest: make console output more verboseEd Bartosh2016-04-181-7/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Added output of test runner to bitbake console output. bitbake <image> -c testimage now reports test progress to the console: NOTE: Executing RunQueue Tasks ... NOTE: recipe core-image-lsb-1.0-r0: task do_testimage: Started core-image-lsb-1.0-r0 do_testimage: test_ping (oeqa.runtime.ping.PingTest) ... ok core-image-lsb-1.0-r0 do_testimage: test_ssh (oeqa.runtime.ssh.SshTest) ... ok ... ---------------------------------------------------------------------- core-image-lsb-1.0-r0 do_testimage: Ran 38 tests in 785.100s core-image-lsb-1.0-r0 do_testimage: core-image-lsb-1.0-r0 do_testimage: OK (skipped=1) Adding more output to the console should also prevent autobuilder to kill long running tests as ab assumes that test is stuck if no console output produced by it for a long time. [YOCTO #8238] (From OE-Core rev: 06aa68138ec67623892221fbe9516bbb3795b48e) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dhcp: CVE-2016-2774Catalin Enache2016-04-182-0/+66
| | | | | | | | | | | | | | | | ISC DHCP 4.1.x before 4.1-ESV-R13 and 4.2.x and 4.3.x before 4.3.4 does not restrict the number of concurrent TCP sessions, which allows remote attackers to cause a denial of service (INSIST assertion failure or request-processing outage) by establishing many sessions. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-2774 (From OE-Core rev: 2fc84114c6323bf1e3d3598af52dd1523168c9fc) Signed-off-by: Catalin Enache <catalin.enache@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: fix perl being included when building with ipkPaul Eggleton2016-04-182-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to some logic within opkg, a package with the name matching a dependency will always win over a package with that name in RPROVIDES - even if there is an RCONFLICTS (which is silently ignored), higher feed priority and version. The end result is that buildtools gets perl installed instead of the nativesdk-buildtools-perl-dummy package and that perl (with missing dependencies) gets used in preference to the host one, which is precisely what we were trying to avoid. This is almost certainly a bug in opkg, especially as the other package's dependencies aren't properly installed under these circumstances either. However, specifying RREPLACES works around this, and with no apparent side-effects is probably the safest solution for now. At the same time I noticed that in prepending to SDK_PACKAGE_ARCHS we were actually ending up with a low priority for the dummy package feed rather than a high one, so change to append it instead. This has no effect on the packages that get installed at the moment, but should be done in case the package manager behaviour changes to factor in the feed priority in future. Fixes [YOCTO #9469]. (From OE-Core rev: b18134ddaf949b4f001a1613ab876aed6324040a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball.bb: fix unexpected operatorRobert Yang2016-04-181-1/+1
| | | | | | | | | | | | | Fixed: run.create_sdk_files.45747: 131: [: =: unexpected operator The SDKMACHINE is not set by default. (From OE-Core rev: 528388c3cef027d436fc794c73d57a247521c238) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/selftest/base.py: Correct a reference to meta/lib/oeqa/selftestPeter Kjellerstedt2016-04-181-1/+1
| | | | | | | (From OE-Core rev: 4ed2a6d43ea19a3026d94666fc342493689d7d46) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-selftest: Correct the usage examplesPeter Kjellerstedt2016-04-181-4/+4
| | | | | | | (From OE-Core rev: 7f5d150e4f9270e586c8a279ee64561c54689ffc) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: sdk-update: reset git metadata on updateStephano Cetola2016-04-182-4/+10
| | | | | | | | | | | | | | | | | Replace git pull with fetch and reset to avoid the merge logic in the event that the layers repo in the published SDK we're updating to isn't fast-forward merge from the local repo. Also add gitignore and committer info during publish to avoid errors and to be sure that the first commit has a dummy user in it. [ YOCTO #9368 ] (From OE-Core rev: 4657bc9d165e51981e034e73e7b92552e873eef7) Signed-off-by: Stephano Cetola <stephano.cetola@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Load TUN at startupJuro Bystricky2016-04-181-2/+6
| | | | | | | | | | | | | | | | | | | | This patch addresses the issue of not being able to execute "runqemu" in the Build Appliance. The root cause of the problem was that TAP/TUN was not available, although required by "runqemu". In addition, the recommended remedy $ sudo modprobe tun would fail for two reasons: modprobe not in PATH (user builder), and "iptables" located in /usr/sbin but expected in /sbin. [YOCTO #9437] (From OE-Core rev: 65db0a29be91a157522cf02ebb21961b8ba55759) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers.inc: set openssl PREFERRED_PROVIDER to opensslAndre McCurdy2016-04-181-0/+3
| | | | | | | | | | | | Although the oe-core openssl recipe is currently the only provider of openssl, make the preference for using it explicit in anticipation of a libressl recipe being added to meta-oe. (From OE-Core rev: 34be80665f1edf96ccaa8f0c612464f0704ec564) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bind: CVE-2016-2088Jussi Kukkonen2016-04-182-0/+248
| | | | | | | | | | | | | | | | | Duplicate EDNS COOKIE options in a response could trigger an assertion failure: Fix with a backport. bind as built with the oe-core recipe is not at risk: Only servers which are built with DNS cookie support (--enable-sit) are vulnerable to denial of service. Fixes [YOCTO #9438] (From OE-Core rev: da38a9840b32e80464e2938395db5c9167729f7e) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: Disable __sync_add_and_fetch_8 on nios2Marek Vasut2016-04-183-0/+32
| | | | | | | | | | | | | | | | The NIOS2 softcore does not implement the __sync_add_and_fetch_8, so disable it accordingly. (From OE-Core rev: 9ef23b0273a87bd19dcc9c21cc1c53b1f8480668) Signed-off-by: Marek Vasut <marex@denx.de> Cc: Ley Foon Tan <lftan@altera.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Ross Burton <ross.burton@intel.com> Cc: Thomas Chou <thomas@wytron.com.tw> Cc: Walter Goossens <waltergoossens@home.nl> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel: fitimage: Fix do_deploy taskhash mismatchMarek Vasut2016-04-181-0/+1
| | | | | | | | | | | | | | | | | | The kernel_do_deploy_append() uses DATETIME variable , so the taskhash of the kernel_do_deploy() function changes if fitImage is used. The buildsystem will complain accordingly: ERROR: linux-yocto-4.4.3+gitAUTOINC+bcc6509084_1a72cec834-r0 do_deploy: Taskhash mismatch 49a5899a6895dcebd311dcb59870f370 verses 37c8dd3aae44134492a876f21c1b641b for /Yocto/poky/meta/recipes-kernel/linux/linux-yocto_4.4.bb.do_deploy ERROR: Taskhash mismatch 49a5899a6895dcebd311dcb59870f370 verses 37c8dd3aae44134492a876f21c1b641b for /Yocto/poky/meta/recipes-kernel/linux/linux-yocto_4.4.bb.do_deploy Fix this by excluding the DATETIME variable from the checksum. (From OE-Core rev: 42ed25f693a4898f517c9ffc7920e5d994ac692d) Signed-off-by: Marek Vasut <marex@denx.de> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* images: zero out the rootfs_extra_space in initramfs imagesStephano Cetola2016-04-182-0/+2
| | | | | | | | | | | Setting IMAGE_ROOTFS_EXTRA_SPACE impacts the initramfs images, results in an error about INITRAMFS_MAXSIZE. (From OE-Core rev: 3ee82430f3f3eb62cbc949658808d109222e8b24) Signed-off-by: Stephano Cetola <stephano.cetola@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ext-sdk-prepare.py: exclude do_rm_work from unexpected output; create unit testBill Randle2016-04-182-11/+91
| | | | | | | | | | | | | | | | | When installing the esdk with INHERIT += "rm_work", the script complains about do_rm_work as unexpected output from the bitbake run. This patch ignores any output lines with do_rm_work and further refactors the output comparison into its own function creates a new unit test to verify the fix. The unit test can be run direct from the command line or via oe-selftest. [YOCTO #9019] (From OE-Core rev: d41930e1daa933cf4bf063fa79a2e8fc9129e1b1) Signed-off-by: Bill Randle <william.c.randle@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-user-manual: Updated the 'bitbake -h' output example.Scott Rifenbark2016-04-181-3/+9
| | | | | | | (Bitbake rev: 4ca651d32d9e5fbf7f932b4167804905969f4c3a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-user-manual: Updated "Conditional Metadata" sectionScott Rifenbark2016-04-181-0/+6
| | | | | | | | | | Added information about using lower-case characters and no underscore characters when using OVERRIDES. (Bitbake rev: 4397a023f8bf738913d71a38b3e06503207311e2) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-user-manual: Updated discussion about using "inherit"Scott Rifenbark2016-04-151-0/+10
| | | | | | | | | | | | Fixes [YOCTO #9343] I updated the inherit directive section to note that you can inherit multiple classes using a single line. (Bitbake rev: 3f29ebec593f20894f7a2a0b6d50ee22474aee75) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: providers: Add PREFERRED_RPROVIDER supportRichard Purdie2016-04-152-23/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sometimes you can end up in a situation where you need to specify that a specific runtime entity should be provided by a specific entry. An example of this is bluez where you could end up in a situation where for example: NOTE: multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5) NOTE: consider defining a PREFERRED_PROVIDER entry to match libasound-module-bluez NOTE: multiple providers are available for runtime bluez-hcidump (bluez-hcidump, bluez5) NOTE: consider defining a PREFERRED_PROVIDER entry to match bluez-hcidump The only option here is to set something like PREFERRED_PROVIDER_bluez4 = "bluez4" which is clearly not very informative. I've actually held off adding RPROVIDER support for a long while as this does have sigificant potential for misuse. It doesn't for example allow multiple runtime providers of the same name to coexist, that simply isn't supported. It therefore doesn't replace some of the name mappings such as busybox verses coreutils that OE-Core faces as that is a different problem with different constraints. This mechanism is simply to provide bitbake with a hint to decide what the dependency tree should look like. Also, this allows us to stop printing a confusing message telling the user to set PREFERRED_PROVIDER when the setting needed would be rather ambiguous. [YOCTO #5044] (Bitbake rev: 62eb39d1474d024b204634689071700605c6095c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: providers: We don't depend on previous build resultsRichard Purdie2016-04-151-3/+3
| | | | | | | | | | Back in history the code did depend on previous build results. This was bad for determinism and we no longer do that. Update comments to match the current behaviour. (Bitbake rev: c3fa7e561c22786d3ac57d04c367aa50f1b3b820) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker/knotty: Prefix parse logs with filename being parsedRichard Purdie2016-04-152-1/+10
| | | | | | | | | | | | | We now prefix log messages coming from worker task context with the PF and task info, however parsing messages all have to be manually prefixed which is ugly and error prone. This change modifies the log handler filter so this happens automatically, meaning we don't have to change every message to include that information. This makes error messages longer but more usable. (Bitbake rev: 1af0ccaac81e182c4ca520037dda362d180e5605) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: pass exception to finishAsyncCommandRichard Purdie2016-04-151-2/+2
| | | | | | | | | | | | | | | | An invalid task causes bitbake to exit incorrectly, firing a CommandCompleted event rather than a CommandFailed one. This means that clients listening for CommandFailed events are unable to detect the build failure even though one occurred. Passing an exception string to finishAsyncCommand when a task fails causes the CommandFailed event to be fired correctly. [YOCTO #9087] (Bitbake rev: 98a2c37e077b16e3bc8bb102bd18b293130d15a4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* fs-perms.txt: fix ROOT_HOME's permissionRobert Yang2016-04-151-0/+3
| | | | | | | | | | | It should be 0700 rather than 0755. Reported-by: Charles Chan <charles.wh.chan@gmail.com> (From OE-Core rev: 37aac647d510557323083c77c3114476440a325d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "fs-perms.txt: fix ROOT_HOME's permission"Ross Burton2016-04-151-1/+0
| | | | | | This reverts commit eeae2ac4887298bcbab0e105798818414686dc97. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildstats: Fix tracebacks for early task failuresRichard Purdie2016-04-151-0/+2
| | | | | | | | | | | | | If a failure occurs early in the task, its possible we can have a TaskFailed before the TaskStarted event can be triggered. This in turn causes another traceback as the directory buildstats writes files into doesn't exist. Ensure the directory exists so we can see the original error. (From OE-Core rev: bd0a65ec47ebf55c549c9ef276b201b72396ce2b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Update to use PREFERRED_RPROVIDERRichard Purdie2016-04-151-4/+2
| | | | | | | | | | | Get rid of the very confusing PREFERRED_PROVIDER_bluez4 using the new/better PREFERRED_RPROVIDER syntax. [YOCTO #5044] (From OE-Core rev: e5c43dc7f1e17f360b5dc762045ccf7895d18843) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/sstatetests: fix no-op sstate testRoss Burton2016-04-151-0/+1
| | | | | | | | | | | | | The test to verify that certain classes when inherited were no-ops only passed if the build already inherited buildhistory. To ensure that the test works as expected, use INHERITS_remove to ensure that the classes are not inherited in the base run. (From OE-Core rev: fc90c5db45933369b8fc0a33d6238876f5e5a087) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory: don't alter SDK creation stampsRoss Burton2016-04-151-4/+8
| | | | | | | | | | This class adds functions to the SDK creation hooks, so ensure that they're ignored in task stamps. (From OE-Core rev: b15b977d10b5165728c1238b8d67a73719d29d60) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dhcp: Enable update-rc.d serviceFabio Berton2016-04-151-1/+5
| | | | | | | | | | | do_install_append function installs init scripts but to enable this service we need to inherit update-rc.d class and set INITSCRIPT name and params. (From OE-Core rev: 854523f173ba9784f1e2a00804c0f5ef16e8cf85) Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/classes/qemu.bbclass: set -cpu of ppce5500/ppce6500 to e500mcZhenhua Luo2016-04-151-4/+4
| | | | | | | | | | | | | | The e5500 and e6500 cpu types are not supported by native qemu, set the value of -cpu to e500mc. Without this change, build will fail for packages which use qemuwrapper in compile phase due to the following error. | Unable to find CPU definition e.g. gobject-introspection (From OE-Core rev: e06c5c5447350049ebd1a6245fc2dd2608b265e5) Signed-off-by: Zhenhua Luo <zhenhua.luo@nxp.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: Disable syslog for more commandsPeter Kjellerstedt2016-04-153-36/+126
| | | | | | | | | | | | When building shadow-native, syslog was disabled for useradd and groupadd. This disables it also for groupdel, groupmems, groupmod, userdel and usermod (i.e., the use of syslog is now disabled for all commands supported by useradd_base.bbclass). (From OE-Core rev: 0791ba7ea82444729a1a7d1b2443f633bcba2002) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: upgrade: handle recipes where source is not first entry in SRC_URIPaul Eggleton2016-04-151-1/+9
| | | | | | | | | | | | | | It is unusual but not impossible to find recipes whose first entry is not the main source URL but instead some patch or other local file, for example python-cryptography in meta-python (which sets SRC_URI before inheriting pypi). There's nothing inherently wrong with this, and we shouldn't assume that the first entry is the main source URL, so just take the first non-local entry instead. (From OE-Core rev: c868198c1f6006789707b497c2ae34d7cc5e706f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>