AgeCommit message (Collapse)Author
2015-04-29busybox: unbreak tar of uncompressed filesyocto-1.7.2dizzy-12.0.2Saul Wold
A patch was added to fix compressed tar files, but broke uncompressed tar files, this fix is from the busybox mailing list [YOCTO #7645] (From OE-Core rev: 2e67a2d35ffcaa0d35363b05209060aff7026c9a) Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2015-04-27fontcache: allow to pass different fontconfig cache dirMartin Jansa
(From OE-Core rev: fc732ee788a254ec388cff8fe5619348014255d3) Signed-off-by: Martin Jansa <> Signed-off-by: Richard Purdie <>
2015-04-27postinst-intercepts/update_font_cache: fix ownership of fontconfig cacheJonathan Liu
The file ownership of the cache files in /var/cache/fontconfig needs to be set to root:root otherwise it inherits the user and group id of the build user. [YOCTO #7411] (From OE-Core rev: 0ecccc7e75f2833c4f2599ce46b6fb9a0bc06e22) Signed-off-by: Jonathan Liu <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-04-27pulseaudio: use stricter PACKAGES_DYNAMICMartin Jansa
* I don't see any usage for libpulse-* packages * adding '-' resolves the issue when we have separate recipe for pulseaudio-modules-droid which isn't built to satisfy RDEPENDS with the same name, because generic pulseaudio recipe seems to RPROVIDE it through PACKAGES_DYNAMIC (From OE-Core rev: 88dfdf7f87f5ea9f5b6200896fc7e7f5374929df) Signed-off-by: Martin Jansa <> Signed-off-by: Richard Purdie <>
2015-04-24bitbake: lib/bb/utils: add safeguard against recursively deleting things we ↵Paul Eggleton
shouldn't Add some very basic safeguard against recursively deleting paths such as / and /home in the event of bugs or user mistakes. Addresses [YOCTO #7620]. (Bitbake master rev: 56cddeb9e1e4d249f84ccd6ef65db245636e38ea) (Bitbake rev: fbf1c39641f78d553961974a2bb96256eb9496e7) Signed-off-by: Paul Eggleton <> Signed-off-by: Richard Purdie <>
2015-04-24bitbake: fetch/git: Remove a possible trailing '/' in subpathAnders Darander
If the subpath parameter to the git fetcher ends with a trailing '/', bb.utils.prunedir() will be called on '/'... Fixes [YOCTO #7620]. (Bitbake master rev: 380a3fb372c8b0a53dd7528562e6e7a222dc76ef) (Bitbake rev: faffa1c4a4d8353b21a0d359076153da0dc31a05) Signed-off-by: Anders Darander <> Signed-off-by: Richard Purdie <>
2015-04-24ref-manual: Updates to the TCLIBC variable descriptionScott Rifenbark
An old note still existed in this entry that stated we don't support glibc. This is not true. I deleted the note. Reported-by: Paul Eggleton <> (From yocto-docs rev: 3a8f5210dfa401bf2d2c9df86dd744c6b39671d7) Signed-off-by: Scott Rifenbark <> Signed-off-by: Richard Purdie <>
2015-04-20valgrind: enable building on 4.x kernelMartin Jansa
(From OE-Core rev: 7351c03e3bd674fcad4cb805bba3f34ef20d7003) Signed-off-by: Martin Jansa <> Signed-off-by: Richard Purdie <>
2015-04-18build-appliance-image: Update to dizzy head revisionRichard Purdie
(From OE-Core rev: 907ef15bb8bf6bd4fb9edb529240ed9982626401) Signed-off-by: Richard Purdie <>
2015-04-18dpkg: Fix patch to adjust for older codeSaul Wold
The older version of dpkg uses subproc_wait_check() instead of the newer subproc_reap() (From OE-Core rev: 3e5632a02ee8f07705d5c34a57f36c6932a2e6cb) Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
2015-04-17build-appliance-image: Update to dizzy head revisionRichard Purdie
(From OE-Core rev: 723e5486e89c6ebe4533ad05ebe5346744c452b1) Signed-off-by: Richard Purdie <>
2015-04-17poky: Update to 1.7.2 release versionRichard Purdie
(From meta-yocto rev: f1b296085c8e511861de951db594884bc7ab42c8) Signed-off-by: Richard Purdie <>
2015-04-17gcc-target: Don't install target gcc libdir filesRichard Purdie
Installing /usr/lib/gcc/* means we'd have two copies, one from gcc-cross and one from here. These can confuse gcc cross where includes use #include_next and builds track file dependencies (e.g. perl and its makedepends code). For determinism we don't install this to the sysroot, ever and rely on the copy from gcc-cross. [YOCTO #7287] (From OE-Core rev: 15b3324b769dc92e1b0d4b9da9fbfccbc8dde9dd) (From OE-Core rev: e80025efbfc8e8df01950045975d103b6d7f87b4) Signed-off-by: Richard Purdie <>
2015-04-17initscripts: Remove /etc/volatile.cache on upgradeBryan Evenson
/etc/volatile.cache is a cached copy of a script (which is generated by /etc/init.d/ that generates the volatile filesystem directories. Since volatile.cache is a generated file, it is not necessarily changed if is updated. As a result, the stale script can add/remove the wrong directories on the next system boot. If initscripts is being upgraded, make sure volatile.cache gets deleted. (From OE-Core rev: 3bdc098028732a4b22b1e65e5566b4cbe105fd41) Signed-off-by: Bryan Evenson <> Signed-off-by: Richard Purdie <>
2015-04-17base-files: Check for /run and /var/lock softlinks on upgradeBryan Evenson
Commit ea647cd9eebdc3e3121b84074519c4bb305adac9 moved the locations of /run and /var/lock to match the FHS 3 draft specifications. However, the install doesn't remove the existing directories. As a result, upgrading a system may result in /run as a softlink to /var/run and /var/run as a softlink to /run, creating a circular link. During pre-install, check for the existence of the old softlinks and remove them so the new directories can be installed. (From OE-Core rev: edeeee8432dc749b02e5e6eca0503229e394ebd3) Signed-off-by: Bryan Evenson <> Signed-off-by: Richard Purdie <>
2015-04-17dpkg-native: Avoid 'file changed' errors from tarRichard Purdie
Hardlink count duing do_package_write_deb can change causing dpkg-deb failures. We don't care about this error case so avoid it by checking the tar exit code. [YOCTO #7529] (From OE-Core rev: 8ee36a5f2f9367550d28bf271afc53bca6ff3d5f) (From OE-Core rev: bcb124931af57dc2f9d8fe9cbbabd5f8ee58e414) Signed-off-by: Richard Purdie <>
2015-04-17files/ fix replace target_sdk_dir twice in ↵Aníbal Limón
environment setup file When specify a target sdk dir that contains default install dir as subdir, target_sdk_dir=/opt/poky/$version/ custom_target_sdk_dir=/opt/poky/$version/some The target_sdk_dir variable in environment-setup file is replaced twice causes to point to wrong PATH. In order to fix filter environment-setup file in second replacement. [YOCTO #7032] (From OE-Core rev: 02ecaa69abe97fe2f01cd609e0e59933c0f9ddbf) (From OE-Core rev: 9f2825cf35d04ec99d29e0e4266410a8843dd80d) Signed-off-by: Aníbal Limón <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17gcc-runtime: Remove libgfortran data from receipeDaniel Dragomir
Remove libgfortran packages from PACKAGES list as long as libgfortran has separate receipe since commit 5bde5d9b39ea67f19a1a6aedd0c08c6cfedcbe5f gcc: Allow fortran to build successfully in 4.8 Otherwise, when fortran support will be enabled in the compiler, both lingfortran and gcc-runtime receipes will create the same files and will try to install them. This will cause errors: ERROR: The recipe libgfortran is trying to install files into a shared area when those files already exist. Those files and their manifest location are: ... Please verify which recipe should provide the above files. (From OE-Core rev: 872342fa3d08edede4a0105ac3ddb0f2ae3224b4) (From OE-Core rev: de2aa7a56790581406f219339c9022638cd47494) Signed-off-by: Daniel Dragomir <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17fontcache.bbclass: prepend to PACKAGEFUNCS instead of appendingJonathan Liu
Appending to PACKAGEFUNCS results in the font packages missing the postinst/postrm scripts and the fontconfig cache not being generated in /var/cache/fontconfig when creating images or installing font packages. This is because the package data has already been emitted by emit_pkgdata in PACKAGEFUNCS. Prepend to PACKAGEFUNCS to ensure add_fontcache_postinsts is executed before emit_pkgdata. [YOCTO #7410] (From OE-Core rev: 7c6d8054bb87e56180920d790efc25d42e25ab8c) Signed-off-by: Jonathan Liu <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17libunwind: backport patch to link against libgcc_s intead of libgccJonathan Liu
(From OE-Core rev: 986b46517ed9cd0821821371faab68e92c2d6dab) Signed-off-by: Jonathan Liu <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17autotools: Avoid find race for S = "${WORKDIR}"Richard Purdie
For recipes with PACKAGES_remove = "${PN}", the find which removes .la files can race against deletion of other directories in WORKDIR e.g.: find: '/home/autobuilder/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0-r7/sstate-build-populate_lic': No such file or directory | WARNING: /home/autobuilder/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0-r7/temp/run.do_configure.6558:1 exit 1 from | find /home/autobuilder/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0-r7 -name \*.la -delete The simplest fix is to add the find option which ignores these kind of races. [YOCTO #7522] (From OE-Core rev: dd8099ca3092fbd5c685e5ef1b1c5a8185a6893d) (From OE-Core rev: 1334c1f78b0020855a2579cfc1f4ab077151e917) Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17cpio: fix CVE-2015-1197Robert Yang
Additional directory traversal vulnerability via symlinks cpio CVE-2015-1197 Initial report: Upstream report: And fix the indent in SRC_URI. [YOCTO #7182] (From OE-Core rev: af18ce070bd1c73f3619d6370928fe7e2e06ff5e) (From OE-Core rev: 68aaca0ff60a9cc770583d3dd89b0c4281b88675) Signed-off-by: Robert Yang <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17patch: fix CVE-2015-1196Robert Yang
A directory traversal flaw was reported in patch: References: [YOCTO #7182] (From OE-Core rev: 4c389880dc9c6221344f7aed221fe8356e8c2056) (From OE-Core rev: e2032c5788f7a77aa0e4e8545b550551c23a25fb) Signed-off-by: Robert Yang <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17e2fsprogs: CVE-2015-0247Sona Sarmadi
Fixes a heap buffer overflow in lib/ext2fs/openfs.c which allows a trivial arbitrary memory write under certain conditions. References (From OE-Core rev: 572437720b6698a3a10627fcd9654ef10f827836) (From OE-Core rev: 67ac6070b1b11a3459ed8fd7e145eb476e493dc6) Signed-off-by: Sona Sarmadi <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17e2fsprogs: Add a patch to speedup mkfsRichard Purdie
See the patch description, this adds a tweak to an algorithm to improve core-image-sato-sdk mkfs time from over 8 minutes to about 35s. Needs discussion upstream but seems reasonable for our uses of it. (From OE-Core rev: 468fa9a7fac86bb0fcd3cbd18dc1492b57ca25f3) (From OE-Core rev: 5aee64c9577affc35ad1555f2a7eb9d287b9fda4) Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17util-linux: fix CVE-2014-9114Armin Kuster
Backport a patch to fix CVE-2014-9114. The patch has been integrated in util-linux-2.26. [YOCTO #7180] Hand applied do to version differencses. (From OE-Core rev: de0c751f57de118bba808f85fa255bb2d99ed9cb) Signed-off-by: Chen Qi <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17tzdata: update to 2015bArmin Kuster
Changes affecting future time stamps Mongolia will start observing DST again this year, from the last Saturday in March at 02:00 to the last Saturday in September at 00:00. (Thanks to Ganbold Tsagaankhuu.) Palestine will start DST on March 28, not March 27. Also, correct the fall 2014 transition from September 26 to October 24. Adjust future predictions accordingly. (Thanks to Steffen Thorsen.) Changes affecting past time stamps The 1982 zone shift in Pacific/Easter has been corrected, fixing a 2015a regression. (Thanks to Stuart Bishop for reporting the problem.) Some more zones have been turned into links, when they differed from existing zones only for older time stamps. As usual, these changes affect UTC offsets in pre-1970 time stamps only. Their old contents have been moved to the 'backzone' file. The affected zones are: America/Antigua, America/Cayman, Pacific/Midway, and Pacific/Saipan. Changes affecting time zone abbreviations Correct the 1992-2010 DST abbreviation in Volgograd from "MSK" to "MSD". (Thanks to Hank W.) (From OE-Core rev: b00539285ffce0b7d954bc0610c986aa53c8255f) (From OE-Core rev: 7f8c1229ec79d256d7249725d8a90312c452e9e7) Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17tzcode: update to 2015bArmin Kuster
Changes affecting code Fix integer overflow bug in reference 'mktime' implementation. (Problem reported by Jörg Richter.) Allow -Dtime_tz=time_t compilations, and allow -Dtime_tz=... libraries to be used in the same executable as standard-library time_t functions. (Problems reported by Bradley White.) Changes affecting commentary Cite the recent Mexican decree changing Quintana Roo's time zone. (Thanks to Carlos Raúl Perasso.) Likewise for the recent Chilean decree. (Thanks to Eduardo Romero Urra.) Update info about Mars time. (From OE-Core rev: fbd98e677dcf6324cf713d888aa85c4264f42ec9) (From OE-Core rev: 098055d44b20010771b420a0ff5640ea7921e455) Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17tzdata: fix HOMEPAGERobert Yang
(From OE-Core rev: 7efed4d963bd8424af0ddebc3a09226182232759) (From OE-Core rev: 5217300dcb40e77dae51f2ad5f05aee17a47adef) Signed-off-by: Robert Yang <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17which 2.18: fix SRC_URIRobert Yang
It is the GPLv2+ version, the old SRC_URI is down, use fedoraproject's repo. Its homepage is also down, but I can't find a new one for it. (From OE-Core rev: 41c4bad11e4a8ebc13f2e4a9712265f3946bf0a8) (From OE-Core rev: e9ed18b3f207ccd5f49118b674006ae3ea37db2d) Signed-off-by: Robert Yang <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17dpkg: add perl to RDEPENDSRobert Yang
perl scripts: packages-split/dpkg/usr/bin/dpkg-parsechangelog:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-mergechangelogs:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-architecture:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-vendor:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-shlibdeps:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-scanpackages:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-buildpackage:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-genchanges:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-gensymbols:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-distaddfile:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-buildflags:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-checkbuilddeps:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-gencontrol:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-scansources:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-source:#!/usr/bin/perl packages-split/dpkg/usr/bin/dpkg-name:#!/usr/bin/perl packages-split/dpkg/usr/lib/dpkg/parsechangelog/debian:#!/usr/bin/perl (From OE-Core rev: eb7179e3c182dc456956fd8ae7e0b512488ad0f2) (From OE-Core rev: bddfec608b065c54ddf2cd3c8bb7668aba929927) Signed-off-by: Robert Yang <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17serf: fix 'ccache' buildsEnrico Scholz
'scons' cleans the environment which breaks ccache builds because CCACHEDIR can point to an unexpected location: | ccache arm-linux-gnueabi-gcc ... context.c | ccache: failed to create .../serf/1.3.8-r0/.home/.ccache (No such file or directory) Issue is described in and because 'bitbake' cleans environment we can pass it completely instead of trying to enumerate needed env. With the 'env.patch' the FULLCC variable is not needed anymore (which would break when CC is 'ccache arm-...-gcc' and host ccache is used) because the correct $PATH is available during scons build: | sh: .../sysroots/x86_64-oe-linux/usr/bin/arm-linux-gnueabi/ccache: No such file or directory | scons: *** [context.o] Error 127 (From OE-Core rev: 24c35c63b85621b263e7a211dc39b2257154cd28) Signed-off-by: Enrico Scholz <> Signed-off-by: Ross Burton <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <> fix rootfs failure with multilib enabledChen Qi
With the current code, if we use debian package backend and enable multilib support, the do_rootfs process would always fail with error messages like below. E: Unable to locate package packagegroup-core-boot This patch fixes the above problem. (From OE-Core rev: d140d556ae30b6dbd0ffce8882c3e22b17050820) (From OE-Core rev: c4306385f6f2139474a4389a465c1650e10b2444) Signed-off-by: Chen Qi <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <> Signed-off-by: Aníbal Limón <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17linux-yocto/3.17: update to v3.17.8Bruce Ashfield
Updating to the latest korg stable version. (From OE-Core rev: 4d342c2531bbb33c9101dcd7a669a620c8cf6917) (From OE-Core rev: 5eb9911fd8c0c83d51c377b088c85ee10605376f) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Conflicts: meta/recipes-kernel/linux/ meta/recipes-kernel/linux/ remove arm64, not supported in dizzy. Signed-off-by: Richard Purdie <>
2015-04-17linux-yocto-tiny_3.17: Update to actually use 3.17 git repoSaul Wold
The named release was still using the -dev git repo which did not contain the SRCREV referenced in the numbered/named version. (From OE-Core rev: b4f2f39ce0f4690ed51d14d1034b9f5e21c0f5a0) (From OE-Core rev: 9b5eb3b534e0153e40a16b7b83d6eaa2dc0f155e) Signed-off-by: Saul Wold <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17linux-yocto/3.14: update to 3.14.29Bruce Ashfield
Updating to the latest korg -stable release for 3.14. (From OE-Core rev: a6a64ee87182c6fa62117e68fafc4ec25ceefc0b) (From OE-Core rev: e34f906abbe77ec4979ac40f01e35989445db86b) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Conflicts: meta/recipes-kernel/linux/ removed arm64 since its not supported in Dizzy. Signed-off-by: Richard Purdie <>
2015-04-17linux-yocto/3.10: update to v3.10.65Bruce Ashfield
Integrating the latest korg -stable updates for 3.10 LTSI. (From OE-Core rev: d159e9db537f68ed91d4a1ab0f432ac1d0020697) (From OE-Core rev: 407023e0ed7b19b548448dbfb4c03b1c88b7ba21) Signed-off-by: Bruce Ashfield <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-17powertop: Fix build for !uclibcMartin Jansa
* EXTRA_LDFLAGS isn't defined for !uclibc and configure fails when it reads it unexpanded, see config.log snippet: configure:4177: checking whether the C compiler works configure:4199: i586-oe-linux-gcc -m32 -march=i586 --sysroot=/OE/sysroots/qemux86 -O2 -pipe -g -feliminate-unused-debug-types -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed ${EXTRA_LDFLAGS} conftest.c >&5 i586-oe-linux-gcc: error: ${EXTRA_LDFLAGS}: No such file or directory configure:4203: $? = 1 configure:4241: result: no (From OE-Core rev: c8f9b5c9a8e5179c2013f25decd6a5483df9c716) Signed-off-by: Martin Jansa <> Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <>
2015-04-15bitbake: bitbake: tests/data: add test for incorrect remove behaviourRoss Burton
The _remove operator isn't working correctly when used with a variable that expands to several items, so add a test case to exercise this path. (Bitbake rev: cb2a62a5fbffb358528a85b46c1fc6383286cb9d) (Bitbake rev: ed950f95fc80f069e800e9c6e785641f307e6512) Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-15bitbake: bitbake: data_smart: split expanded removal values when handling ↵Ross Burton
_remove Given these assignments: TEST="a b c d" TEST_remove = "b d" TEST evaluates to "a c". However, if the _remove override is given as a variable: TEST="a b c d" FOO = "b d" TEST_remove = "${FOO} TEST evaluates to "a b c d", because when FOO is expanded it isn't split into a list. Solve this by splitting all members of removeactive once they've been expanded. [ YOCTO #7272 ] (Bitbake rev: 207013b6dde82f9654f9be996695c8335b95a288) (Bitbake rev: c25b0e0ca289f6ad0ed697a0b0252fa48ab5dd0b) Signed-off-by: Ross Burton <> Signed-off-by: Richard Purdie <> Signed-off-by: Armin Kuster <> Signed-off-by: Richard Purdie <>
2015-04-15toolchain-scripts: Allow the CONFIGSITE_CACHE variable to be overriddenRichard Purdie
In multilib and baremetal configurations, this variable can cause a variety of problems due to the use of TCLIBC. At least allowing it to be overriden is a start and allows various configurations to avoid the issue. (From OE-Core rev: 816a62af5181e940f4b5e5f35f6775499fad94eb) Signed-off-by: Richard Purdie <>
2015-04-15openssl: Fix x32 openssl patch which was not buildingBrendan Le Foll
x32 builds where broken due to patch rebase not having been done correctly for this patch (From OE-Core rev: 8e46230fe94c44ab81a0ca9cb8b2c9f7b605e226) Signed-off-by: Brendan Le Foll <> Signed-off-by: Richard Purdie <>
2015-04-11bitbake: fixes bad substitution when running devshellRichard Tollerton
Running bitbake inside make results in the exported environment variable MAKEOVERRIDES="${-*-command-variables-*-}", which the shell chokes on when trying to expand it. But of course, it probably shouldn't have been trying to expand it in the first place -- so just escape the dollar sign. (Bitbake rev: 18cd0ce6a55c9065c3f1bf223b47d817b5efcd8f) (Bitbake rev: 34226a9e02f319a7547967bbdaca3ca918927dd1) Signed-off-by: Richard Tollerton <> Signed-off-by: Richard Purdie <> Signed-off-by: Alejandro Hernandez <> Signed-off-by: Richard Purdie <>
2015-04-11bitbake: cooker/server: Fix up 100% CPU usage at idleRichard Purdie
The recent inotify changes are causing a 100% cpu usage issue in the idle handlers. To avoid this, we update the idle functions to optionally report a float value which is the delay before the function needs to be called again. 1 second is fine for the inotify handler, in reality its more like 0.1s due to the default idle function sleep. This reverts performance regressions of 1.5 minutes on a kernel build and ~5-6 minutes on a image from scratch. (Bitbake rev: 0e0ba408c2dce14a0fabd3fdf61d8465a031495b) (Bitbake rev: 88dfe16b5abd804bae0c1e3b60cb93cb951cbc3f) Signed-off-by: Richard Purdie <>
2015-04-11bitbake: cooker: read file watches on server idleAlexandru DAMIAN
The inotify facility monitoring changes to the config files could be overwhelmed by massive changes to the watched files while server is running. This patch adds verification the notification watches to the server idle functions, in addition to the cooker updateCache command which executes only infrequently, thus preventing overflowing the notification buffer. [YOCTO #7316] (Bitbake rev: 996e663fd5c254292f44eca46f5fdc95af897f98) (Bitbake rev: b44694b1efc7389536df2f901a8b70321edfeeba) Signed-off-by: Alexandru DAMIAN <> Signed-off-by: Richard Purdie <>
2015-04-11bitbake: cooker: Improve pyinotify performanceRichard Purdie
Benchmarks show that the introduction of pyinotify regressed performance. This patch ensures we only call the add_watch() function for new entries, not ones we've already processed which does improve performance as measured by "time bitbake -p". This doesn't completely remove the overhead but it does substantially reduce it. (Bitbake rev: 493361f35f6cc332d4ea359a2695622c2c91a9c2) (Bitbake rev: f668b347a8f9563f41d454288b9d4632190f308f) Signed-off-by: Richard Purdie <>
2015-04-11bitbake: cooker: Further optimise pyinotifyRichard Purdie
We currently add crazy numbers of watches on files. The per user limit is 8192 by default and on a system handling multiple builds, this can be an issue. We don't need to watch all files individually, we can watch the directory containing the file instead. This gives better resource utilisation and better performance further reverting some of the performance regression seen with the introduction of pyinotify. (Bitbake rev: a2d441237916a99405b800c1a3dc39f860100a8c) (Bitbake rev: 6ab3945fc54b2a242292a874d78ebd8cccb99573) Signed-off-by: Richard Purdie <>
2015-04-11bitbake: cooker: Fix pyinotify handling of ENOENT issuesRichard Purdie
We try and add watches for files that don't exist but if they did, would influence the parser. The parent directory of these files may not exist, in which case we need to watch any parent that does exist for changes. This change implements that fallback handling. (Bitbake rev: 979ddbe4b7340d7cf2f432f6b1eba1c58d55ff42) (Bitbake rev: 6d0abc6a5c9b8b37eecfa63fbcb5343162bc9311) Signed-off-by: Richard Purdie <>
2015-04-11bitbake: cooker/cache/parse: Implement pyinofity based reconfigureRichard Purdie
Memory resident bitbake has one current flaw, changes in the base configuration are not noticed by bitbake. The parsing cache is also refreshed on each invocation of bitbake (although the mtime cache is not cleared so its pointless). This change adds in pyinotify support and adds two different watchers, one for the base configuration and one for the parsed recipes. Changes in the latter will trigger a reparse (and an update of the mtime cache). The former will trigger a complete reload of the configuration. Note that this code will also correctly handle creation of new configuration files since the __depends and __base_depends variables already track these for cache correctness purposes. We could be a little more clever about parsing cache invalidation, right now we just invalidate the whole thing and recheck. For now, its better than what we have and doesn't seem to perform that badly though. For education and QA purposes I can document a workflow that illustrates this: $ source oe-init-build-env-memres $ time bitbake bash [base configuration is loaded, recipes are parsed, bash builds] $ time bitbake bash [command returns quickly since all caches are valid] $ touch ../meta/classes/gettext.bbclass $ time bitbake bash [reparse is triggered, time is longer than above] $ echo 'FOO = "1"' >> conf/local.conf $ time bitbake bash [reparse is triggered, but with a base configuration reload too] As far as changes go, I like this one a lot, it makes memory resident bitbake truly usable and may be the tweak we need to make it the default. The new pyinotify dependency is covered in the previous commit. (Bitbake rev: 0557d03c170fba8d7efe82be1b9641d0eb229213) (Bitbake rev: 47809de6459deb346929e4ca6efa87a997cfcb38) Signed-off-by: Richard Purdie <>
2015-04-11bitbake: bitbake: Add pyinotify to lib/Richard Purdie
We need inotify support within bitbake and pyinotify provides the best mechanism to add this. We have a few options: a) Depend on pyinotify from the system b) Add in our own copy c) Only use pyinotify in cases like the memory resident server For a), it would mean adding in dependencies, updating documentation and generally creating churn for users as well as having implications for things like the build-appliance recipe. It turns out that glibc has the C functionality we need from version 2.4 onwards (2006) and that we just need a single python file for b), there is no binary module needed. We therefore add in a copy of pyinotify 0.9.5 into the tree meaning we can depend on it simply and unconditionally. c) is unattractive as we need fewer possible code paths, not more. (Bitbake rev: d49004a4e247e3958a2f7ea9ffe5ec92794e1352) (Bitbake rev: 2835b12288cf0c46586d6f708a0ee0b5e025cba3) Signed-off-by: Richard Purdie <>