summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* ref-manual: Fixed cross-reference anchor name.Scott Rifenbark2014-01-211-1/+1
| | | | | | | (From yocto-docs rev: 15c124c85e95e070c959ab110511ddd70acbb71f) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to the "Writing a New Recipe" section.Scott Rifenbark2014-01-211-117/+89
| | | | | | | | | Implemented some third review feedback from Paul Eggleton. (From yocto-docs rev: 3fd9c3cc4cf2aba876f0ad2ab36660ec32ea4c08) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added note about curly brace parsing to BitBake chapter.Scott Rifenbark2014-01-211-0/+40
| | | | | | | (From yocto-docs rev: 91f199552f0012f1790dbac4d038eac101f2a274) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Edits to TCLIBC variable.Scott Rifenbark2014-01-211-3/+3
| | | | | | | | | Some minor changes. (From yocto-docs rev: e545ee26e7e6c827c5ee6d7061f01eda58c9c82b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Examples" and "Post-Installation" sections.Scott Rifenbark2014-01-211-85/+87
| | | | | | | | | | | | | Applied review comments to these sections, which are part of the "Writing a New Recipe" section. Moved the Post-installation section out of the examples area into its own, higher-level section as it was not really an example. Other edits were direct result of Paul Eggleton's review. (From yocto-docs rev: c147a8bedf79d0be42d7b338e10b7e42d7c0b080) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Testing" section.Scott Rifenbark2014-01-211-2/+0
| | | | | | | | | | | Applied review comments from Paul Eggleton to this section, which is a part of the "Writing a New Recipe" section. Very minor fix to remove a sentence that was somewhat isolated and unecessary. (From yocto-docs rev: fd2a0eac1bc4b9e6af0bc8ce9a30802dbea35873) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Packaging" section.Scott Rifenbark2014-01-211-2/+3
| | | | | | | | | | | | | Applied some self-edits to this section that is part of the "Writing a New Recipe" section. There was no feedback from the second review but I noticed a few issues. Also, I added that reference on how to add a post-installation script from the "Enabling System Services" section as noted by Paul Eggleton. (From yocto-docs rev: 6be835637cb1dc232d6d6dd1dfe1bc803efecfd3) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Enabling System Services" section.Scott Rifenbark2014-01-211-20/+24
| | | | | | | | | | | | Applied review comments from Paul Eggleton to the section that is part of the "Writing a New Recipe" section. I changed the title of the section and applied some rewordings to better reprepresent exactly what sysvinit and systemd really are (managers). (From yocto-docs rev: 95c3ed5b7d1ace08828baacc8401e1ea5d96a06e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Installing" section.Scott Rifenbark2014-01-211-8/+17
| | | | | | | | | | Applied review comments from Paul Eggleton to this section that is part of the new "Writing a New Recipe" section. Minor edits. (From yocto-docs rev: a5116900ca42377c3dc19433b2f6046828ad2dcc) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Compilation" section.Scott Rifenbark2014-01-211-4/+22
| | | | | | | | | | | | Added review comments to the section inside the new "Writing a New Recipe" section. Minor word fixes. I did add a new common compilation failure scenario. All input from Paul Eggleton. (From yocto-docs rev: 5818a8882ff55fc27c5dc77233854465b8c2245b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Configuring the Recipe" section.Scott Rifenbark2014-01-211-14/+18
| | | | | | | | | | | Applied review edits from Paul Eggleton for this section that is part of the "Writing a New Recipe" section. Minor wording issues only. (From yocto-docs rev: 8e291826fcb9547c3fc16aa81ccf6867fe2e417d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to the "Licensing" section.Scott Rifenbark2014-01-211-6/+5
| | | | | | | | | | Applied review comments to this section per Paul Eggleton. Minor word changes. (From yocto-docs rev: 5130559003778e3b613d3d480350d041dfd10fcd) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Edits to the SPDXLICENSEMAP variable.Scott Rifenbark2014-01-211-1/+2
| | | | | | | | | Fixed wording to reference default mappings. (From yocto-docs rev: 4ceddbe8454f473907e5ae469102f3a43d20122c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Unpacking Code" section.Scott Rifenbark2014-01-211-7/+10
| | | | | | | | | Applied review comments to this section. (From yocto-docs rev: f4075f61ca081df6c87abd876207da968450a8f3) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Fetching Code" section.Scott Rifenbark2014-01-211-91/+101
| | | | | | | | | | | | | | | Applied review comments to this section. Specifically, I addressed the organization and got rid of the bullet list. I integrated this information into the examples used for the various SRC_URI snippits. Also, part of the feedback including separating out the patching information into an isolated section. I set up the section and moved minimal information into it. (From yocto-docs rev: 0a16977c2125402cdd04e24ad5bce074859eb28a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Running a Build on the Recipe"Scott Rifenbark2014-01-211-25/+24
| | | | | | | | | | Corrective edits to this section based on Paul's feedback. Several items addressed. (From yocto-docs rev: a09ebe38e0ad22ad4ab12eab3d5a73166e4c56f8) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Storing and Naming the Recipe"Scott Rifenbark2014-01-211-41/+39
| | | | | | | | | | | Re-ordered this such that the storage of the recipe comes first and that is followed by naming it. Also, formatted into a list to give a better sense of the suggested order. (From yocto-docs rev: aead82f034a097cbdfe38b3b1f09a60cc411d6ea) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Locate a Base Recipe" section.Scott Rifenbark2014-01-211-6/+7
| | | | | | | | | | Updated the introductory paragraph to be more general about where a user might locate an existing recipe as a base. (From yocto-docs rev: d6147d19785824cde29e82aa32916dcec5ae2276) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Edits to "Locate a Base Recipe" section.Scott Rifenbark2014-01-211-7/+12
| | | | | | | | | | | | I removed the note structure for the information about BitBake parcing curly braces. The note was to prominent. I added a leading sentence to better integrate the information into the section. (From yocto-docs rev: 21dd7ceced2c9867e4fefc2aab81a4ab3da3bc7d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.conf: Remove Debian Squeeze from SANITY_TESTED_DISTROSOlof Johansson2014-01-211-1/+0
| | | | | | | | | | Debian Squeeze is not a supported platform, since the bitbake python dependency on Python was bumped to 2.7. (From meta-yocto rev: d18666aebe2d1889dcf45dc0fda491970cb77433) Signed-off-by: Olof Johansson <olof.johansson@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.conf: add Debian 7.3 to SANITY_TESTED_DISTROSOlof Johansson2014-01-211-0/+1
| | | | | | | | | | 7.3 is a point release with security and bug fixes only, and I can confirm that it works. (From meta-yocto rev: baf65c002f6bc2ecf6c61a8ec5f1ad8b994b033d) Signed-off-by: Olof Johansson <olof.johansson@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: remove previous version's stampRobert Yang2014-01-211-9/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a potential problem if we don't remove the previous version's stamp, for example: The depend chain is: libtool-native -> autoconf-native -> m4-native We have two m4-native: 1.4.9 and 1.4.7 1) Clean all of them to make a fresh build so that we can reproduce the problem $ bitbake m4-native autoconf-native libtool-native -ccleansstate 2) Build libtool-native so that the m4-native_1.4.17 will be built $ bitbake libtool-native 3) Set PREFERRED_VERSION_m4-native = "1.4.9" and build again $ bitbake libtool-native 4) Set PREFERRED_VERSION_m4-native = "1.4.17" and build again $ bitbake libtool-native -ccleansstate && bitbake libtool-native Then the build will fail: [snip] | m4: unrecognized option '--gnu' | Try `m4 --help' for more information. | autom4te: m4 failed with exit status: 1 [snip] The is because when we change m4-native to 1.4.17 and build libtool-native again: 5) libtool-native depends on autoconf-native, and autoconf-native's version isn't change, so it can remove the current stamp and mirror the sstate (the one depends on m4-native_1.4.9) from the SSTATE_DIR correctly. 6) The mirrored autoconf-native depends on m4-native_1.4.17's do_populate_sysroot, and the stamp is already there (which is made by step 2), so it would do nothing, but this is incorrect, since the one that really in the sysroot is m4-native_1.4.9, then the error happens. Remove previous version's stamp in sstate_clean() will fix the problem. [YOCTO #5422] (From OE-Core rev: 4659d29b1040349116549644e45035a5b37d9311) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs/populate-extfs.sh: fix a problem on dashRobert Yang2014-01-211-1/+1
| | | | | | | | | | | | | | | | | | | | | | | The dash can't handle the or [[ in parameter expansion, for example: A=/usr/bin/[[ B=[[ C="${A%$B}" The C should be "/usr/bin" in common, but it will be /usr/bin/[[ on dash, use dirname to fix it. NOTE: There are 3 lines about parameter expansion, only fix the DIR="${DIR%$TGT}" since the other 2 works will and are very useful in this case. [YOCTO #5712] (From OE-Core rev: 22f90c5aec4f0b0360d1d960226f9965d83d589b) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: package Marvell SD8797 firmwareAndreas Oberritter2014-01-211-1/+7
| | | | | | | (From OE-Core rev: 8fcd5accbe8ffca9e0c5233419c1571741c76c03) Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* guile: don't use the identifier 'noreturn'Robert Yang2014-01-212-0/+66
| | | | | | | | | | | | | | | Fix the build error of autogen-native which depends on guile-native: ysroots/x86_64-linux/usr/include/guile/2.0/libguile/error.h:40:24: error: expected ')' before '__attribute__' sysroots/x86_64-linux/usr/include/guile/2.0/libguile/error.h:40:24: error: expected ',' or ';' before ')' token sysroots/x86_64-linux/usr/include/guile/2.0/libguile/error.h:42:27: error: expected ')' before '__attribute__' [YOCTO #5743] (From OE-Core rev: 05d226bee199e9d45f0bb6143d3a78f3f2e93186) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/git: Dereference unresolved tags with ls-remoteRichard Purdie2014-01-211-1/+1
| | | | | | | | | | | We need to deference tags when trying to map them to commit IDs with ls-remote. If we don't do this, a given commit might not show up later in a specific branch. There appears to be no good reason not to do this. (Bitbake rev: 8ef24f4c834298348172b96ec0b855bf09552b09) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/git: Anchor names when using ls-remoteRichard Purdie2014-01-211-2/+2
| | | | | | | | | | | | | | | | When specifying tags, they're searched for unanchored so foo/bar could match: refs/heads/abc/foo/bar refs/heads/xyz/foo/bar refs/heads/foo/bar This change anchors the expressions so they are based against heads or tags (or any other base level tree that has been created). (Bitbake rev: df2e0972cd1db7abd5ec8b7cb295fb0c42e284a4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Improve invalid SRCREV error messageRichard Purdie2014-01-211-10/+5
| | | | | | | | | The current message can be ambiguous, improve it (and also rename a variable to clean up the rest of the function). (Bitbake rev: 0c1bb7c0fce7b0f334311a2893ccb00385fa8d55) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Sanity check SRCREV matches rev/tag parameterRichard Purdie2014-01-212-6/+29
| | | | | | | | | | | | | | | Add a sanity check so that if some SRCREV is set and a rev parameter is given to the url, the revision given should match. Any tag parameter behaves the same as rev. If both are specified, error to tell the user we're confused rather than do something which may or may not be what they intended. Also add some unittests for this. (Bitbake rev: e82a4ab48991035866da9914c8b75a9bfbc9a7fc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Clean up srcrev_internal_helperRichard Purdie2014-01-211-9/+16
| | | | | | | | | | Currently INVALID and None are checked as incorrect values under different circumstances. This code standardises those checks to be consistent. We should phase out the use of "INVALID". (Bitbake rev: 86ef4e65ce18b71dc69643586bd2aa8f48703171) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: show warning when package is providing already provided shlibMartin Jansa2014-01-211-2/+9
| | | | | | | | | | | | | * move read_shlib_providers before registering package as provider and show warning when different package tries to provide something already provided. [YOCTO #4628] (From OE-Core rev: 8141e3f61f12c8901b990496bcf6b76a9db95a57) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: move reading shlibs providers to separate functionMartin Jansa2014-01-211-20/+23
| | | | | | | | | | | | * prepare for reading shlibs providers only from dependency tree of current recipe [YOCTO #4628] (From OE-Core rev: c5076f33ac27c0c2b0743bf6dc4edc983254c467) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc: use exact match in blacklists, re-start with empty ↵Martin Jansa2014-01-211-15/+18
| | | | | | | | | | | | | | | | | system_package_blacklist * unify debug messages a bit * old implementation allowed partial match in blacklist, it's safer to explicitly list exact matches * I was able to build all entries from system_package_blacklist with icecc enabled, lets assume that they were already resolved by newer versions (we've fixed a lot of parallel issues in recipes which were detected even without icecc and this list is very old). (From OE-Core rev: 5a5319d2e6f41bb0e290d6a1decbd996e9572690) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc: Fix allarch and native recipes having different signaturesMartin Jansa2014-01-211-0/+4
| | | | | | | | | | | | * for different MACHINES * is there more elegant way to have "overridable" function so that signature handler properly uses only the branch without STAGING_BINDIR_TOOLCHAIN? (From OE-Core rev: 418a353a011ca8f04ecc3e2d29f2d1a415492081) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc: use bb.utils.which also for 'as'Martin Jansa2014-01-211-1/+6
| | | | | | | | | | | | | | | | | | * it was introduced in commit 3a842ec52e7d010767b13bdcb5629ac07b3ee9e7 Author: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Date: Fri Sep 16 10:55:16 2011 +0400 Subject: icecc.bbclass: replace with updated version without any explanation in which case ${ICECC_CC} -print-prog-name=as is returning as in current working directory, but will keep old behavior just in case (From OE-Core rev: 6092da20fc3ceb1bc6b4872ad16df565f05723b7) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc: Don't replace non-empty PARALLEL_MAKE with empty ICECC_PARALLEL_MAKEMartin Jansa2014-01-211-1/+1
| | | | | | | | | | | | | | | | | | | | * it's needed for use-case like this: # Inherit icecc here, so that all builders have the same sstate signatures INHERIT_DISTRO += "icecc" # and then disable its function by default (so that people still need to explicity # enable it in local.conf if they have configured icecc and want to use it. # You need to set _empty_ value in local.conf to enable icecc function: # ICECC_DISABLED = "" ICECC_DISABLED ??= "1" * so default ICECC_PARALLEL_MAKE is still empty, but we want build to respect our PARALLEL_MAKE, unfortunately we cannot do something like ICECC_PARALLEL_MAKE ??= "${PARALLEL_MAKE}", because that would cause PARALLEL_MAKE to reference itself. (From OE-Core rev: 7e586d5b7c8c7f20eafc32624200f60a8ed9a582) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* allarch: Set empty TARGET_PREFIX and TARGET_FPUMartin Jansa2014-01-211-0/+2
| | | | | | | | | | | | | | | | | | | * set empty TARGET_PREFIX This has a bit weird reason caused by unsupported setup where external-toolchain is used in some DISTRO only for some MACHINEs and internal is used for other MACHINEs. Because external-toolchain usually comes with different TARGET_PREFIX it was causing allarch recipes to have different signatures even when they don't use toolchain at all. Empty TARGET_PREFIX also helps to find allarch recipes which still have default dependency on e.g. virtual/${TARGET_PREFIX}gcc. * add TARGET_FPU just for completeness (it was used in icecc.bbclass but now it's vardepexcluded there as well) (From OE-Core rev: 180ba7f6603b35eb66946649d8860022d2c329b7) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig: include native/cross/nativesdk deps in target signaturesMartin Jansa2014-01-211-4/+0
| | | | | | | | | | | | | | | | | | | | * I don't have any real evidence or good statistics for this, but when comparing signature dumps from my big bitbake world builds I usually see a lot of rebuilds caused by changes in .bbclasses and only very rare would be the case where oe-core upgrade brings changes in -native recipes and no change in .bbclasses used from target recipes * changing the default to include them shouldn't cause significant increase in rebuilds and sstate reuse a bit safer * people working on toolchain (e.g. using gcc from AUTOREV) can easily extend sstate_rundepfilter to ignore them again (it's easier than removing existing filter), example how add own signature handler in your layer is here: https://github.com/openwebos/meta-webos/commit/9ac3a7c803e7793b3274e4998f167b6278db8042 (From OE-Core rev: 336a7897e39b9e42dcfcba9e2520ea96b0c6a8d6) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-tiny.conf: Add PACKAGECONFIG to disable opkg-utils python dependenciesRichard Purdie2014-01-191-0/+3
| | | | | | (From meta-yocto rev: 5b191256efdf4ae7d0f58cd2612048d832b86556) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto-bsps: update reference BSPs to v3.10.25Bruce Ashfield2014-01-191-5/+5
| | | | | | | | | Update the 3.10 Yocto reference BSPs to the korg 3.10.25 update. (From meta-yocto rev: ae17d80c6240589a48266c82b3df1e3787864049) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-utils: Remove strange PACKAGES native overrideRichard Purdie2014-01-191-3/+0
| | | | | | | | | This code makes no sense, native.bbclass clears PACKAGES anyway. Drop it. (From OE-Core rev: 9c8d9781794ed0886a79c8ce4544ba98be0ff858) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-utils: Add basic PACKAGECONFIG for python dependenciesRichard Purdie2014-01-191-3/+6
| | | | | | | | | | In small configurations its useful not to have python dependencies. This patch adds code to disable those using PACKAGECONFIG. This allows us to fix poky-tiny after the recent move of update-alternatives to opkg-utils. (From OE-Core rev: 0c0039048fd97cdd3cf28f9e1c829a716dfd68ea) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: add explicit build dependency on DBus when ptest is enabledRoss Burton2014-01-191-0/+2
| | | | | | | | | | | | If the tests are enabled then configure will check for the presence DBus. It's generally present through the runtime dependencies so this often succeeds but as it isn't a build dependency it's possible for DBus to be present at configure time but removed at compile time, resulting in build failures. (From OE-Core rev: 0150e86a7609579cf26f5ef5c6c69b521340218e) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-selftest: Patch sstate tests to work with new sstate-cache naming and contentCorneliu Stoicescu2014-01-191-13/+15
| | | | | | | | | | | Made modifications to account for: - .siginfo files present in sstate-cache from non sstate-enabled tasks - new naming format for sstate files (From OE-Core rev: d23ad4255ad7465383286fa7805392aa70845ace) Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcl: fix the TCL_INCLUDE_SPECRobert Yang2014-01-191-15/+45
| | | | | | | | | | | | | | | | | | | | | | We have moved the header files to ${includedir}/tcl${VERSION}, but we didn't fix the TCL_INCLUDE_SPEC which is still ${includedir}, it should also be ${includedir}/tcl${VERSION} Note: this commit modifiey alter-includedir.patch, so it doesn't look very clear, I only fixed one line in both configure and configure.in: -eval "TCL_INCLUDE_SPEC=\"-I${includedir}\"" +eval "TCL_INCLUDE_SPEC=\"-I${includedir}/tcl${VERSION}\"" The other changes are because I use git to create the patch while the previous one uses svn. [YOCTO #5732] (From OE-Core rev: a263281d9c774a03cce76caa3cc477cc85a9c2a9) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg/opkg-utils/chkconfig: Clean up u-a-cworth referencesRichard Purdie2014-01-193-2/+2
| | | | | | | | | Catch some u-a-cworth references that slipped through the move of u-a to opkg-utils and its rename to -opkg. (From OE-Core rev: a9ff0bbac5ae0688525c71f0a358f0750a277269) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-alternatives: We now use u-a in nativesdk so make sure the dependency ↵Richard Purdie2014-01-191-1/+1
| | | | | | | | | | | | | | is present When update-alternatives was part of opkg which got built in most nativesdk scenarios, this missing dependency wasn't an issue. We now need nativesdk-opkg-utils so we need to ensure the dependency is present in nativesdk cases. This avoids build failures with the recent u-a move to opkg-utils. (From OE-Core rev: 7e0adf676da45e49287b7ce6478a6dbfd8fa117f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto-dev: bump version to 3.13+Bruce Ashfield2014-01-191-1/+1
| | | | | | | (From OE-Core rev: 0e0307a23d50b2a0efd228e7e99baabc980ab9de) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa: allow a layer to provide it's own TEST_TARGET classStefan Stanacar2014-01-192-4/+22
| | | | | | | | | | | | Allows a layer to define new classes in <layer>/lib/oeqa/utils/controllers.py and completely control or extend deployment of a target. (core currently has QemuTarget and SimpleRemoteTarget). The value of TEST_TARGET must be the name of the new class. (From OE-Core rev: 9b81aff0aca42353d448b1e9522f89842e23c7b2) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x11vnc: fix CAPS_LOCK issuesLaurentiu Palcu2014-01-191-1/+5
| | | | | | | | | | | | | | | | | Currently, pressing CAPS_LOCK on the viewer changes the lock state on the server and the key will not change the case. To fix this, use -skip_lockkeys option to ignore all Caps_Lock, Shift_Lock, Num_Lock, Scroll_Lock keysyms received from viewers, in order to leave the lock state on the server side unchanged. However, the keys will appear correctly on the remote side. [YOCTO #4149] (From OE-Core rev: 1e06d5ce83439b5bd75a958f305e6a880d40333d) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-15 08:42:39 +0000