summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2018-02-06python3: update target and native recipes to 3.5.4Derek Straka
Use the latest 3.5 version until the 3.6 migration is complete Removed the following upstreamed patches: - python3/Fix-29519-weakref-spewing-exceptions-during-interp-f.patch - python3/upstream-random-fixes.patch Rebased the following pathes: - python3/0001-cross-compile-support.patch Regenerated the manifest based on the latest release version Updated the license checksum for the latest version that updated the copyright dates (From OE-Core rev: eb80d0391d7d4e83a61ed8850d936b102be3fa02) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06ltp: remove patches that already have fixes upstreamAnders Roxell
The following patches has already fixes for the issues they are solving in upstream. - 0001-add-_GNU_SOURCE-to-pec_listener.c.patch - 0011-Rename-sigset-variable-to-sigset1.patch - 0025-mc_gethost-include-sys-types.h.patch - 0027-sysconf01-Use-_SC_2_C_VERSION-conditionally.patch - 0033-shmat1-Cover-GNU-specific-code-under-__USE_GNU.patch Suggested-by: Yi Zhao <yi.zhao@windriver.com> (From OE-Core rev: 88e12a14540e10718fb2e68f27834d9b7565ab7e) Signed-off-by: Anders Roxell <anders.roxell@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06python2-manifest: update the manifest file for python 2.7.14Derek Straka
The manifest file was not regenerated when the package was updated. (From OE-Core rev: c42a1cf42b88c0dc02baf807ee2aa3dab058c4cd) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06python-native: add dependency for gdbm and db native packagesDerek Straka
These two packages are required to ensure the manifest files contain all of the generated packages. Without this, the db and gdbm packages will not contain the .so files as they are skipped during the compilation steps (From OE-Core rev: 912c06615269f42230db2d93d70db2b340ed270a) Signed-off-by: Derek Straka <derek@asterius.io> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06qemu: fix memfd_create with glibc 2.27Ross Burton
glibc 2.27 has added memfd_create() but this conflicts with a copy in qemu, so take a patch from upstream to fix building with glibc 2.27. (From OE-Core rev: 207733bb875b1a6b932ecd04a34a0ee118511d1f) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06sysstat: 11.6.1 -> 11.7.1Huang Qiyu
Upgrade sysstat from 11.6.1 to 11.7.1. (From OE-Core rev: 5a6c5234c8685e205ae16729b82288dc8f687122) Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06ruby: 2.4.2 -> 2.5.0Huang Qiyu
1.Upgrade ruby form 2.4.2 to 2.5.0. 2.Update the checksum of LIC_FILES_CHKSUM. 3.Delete ruby-CVE-2017-9224.patch, ruby-CVE-2017-9227.patch, ruby-CVE-2017-9229.patch, since it is integrated upstream. 4.Modify ruby-CVE-2017-9226.patch, since the data has been changed. (From OE-Core rev: 67b9f407f7c40c63c7f9518b4ee3d4d1cc7c75ce) Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06rng-tools: modify 'read error' messageJoe Slater
Expand messages output if entropy data cannot be read. (From OE-Core rev: 23cf9be2065d6ea01f6d10cbed64a590c31e5bfc) Signed-off-by: Joe Slater <joe.slater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06musl: Update to latest masterKhem Raj
The changes are https://git.musl-libc.org/cgit/musl/log/?qt=range&q=4000b0107ddd7fe733fa31d4f078c6fcd35851d6..628cf979b249fa76a80962e2eefe05073216a4db (From OE-Core rev: ed1598d08e53c92a5df286de518a9b355ee50f59) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06devtool: set up git repos so that singletask.lock is ignoredPaul Eggleton
singletask.lock is written out while certain tasks execute for recipes that have externalsrc.bbclass enabled - this includes recipes in devtool's workspace. It appears that there's a race where singletask.lock will be there one minute and then when we try to get the file checksum of it (since we want to know if anything in the source tree has changed) it will be gone, and git chokes. To fix that, add singletask.lock to .git/info/exclude in the repository, regardless of whether we created the repository or not. In any case singletask.lock should never be tracked by git, so this is a good thing to be doing for that reason as well. This fixes oe-selftest failures in test_devtool_modify that we've seen on the Yocto Project autobuilder: bb.data_smart.ExpansionError: Failure expanding variable do_compile[file-checksums], expression was ${@srctree_hash_files(d)} which triggered exception CalledProcessError: Command '['git', 'add', '-A', '.']' returned non-zero exit status 128. Note that this only fixes this issue for devtool; if you are using externalsrc independently of devtool there's a chance this will still be an issue unless you add singletask.lock to your .gitignore. (From OE-Core rev: 334ba846c795fc0d8c73ce05a1b0882739c86650) 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>
2018-02-06npm.bbclass: Node module name and recipe name can be differentBöszörményi Zoltán
Some NPM modules have the same name as their low level dependencies. To prevent recipe naming conflicts, allow node module recipe names to start with the "node-" prefix. (From OE-Core rev: 6b417c7c3a38463c64756beae9817fa2a80fd09e) Signed-off-by: Zoltán Böszörményi <zboszor@pr.hu> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06npm.bbclass: Fix building node modules with npm@5Böszörményi Zoltán
npm cache clear throws an error with npm@5 and suggests to use npm cache verify instead. But our cache is actually empty, so use npm cache clear --force. npm install in the source directory creates symlinks with npm@5. Use a combination of npm pack and npm install module-version.tgz that works the same way with older and new npm versions and is guaranteed to create actual copies instead of directory symlinks. This change allows using nodejs 8.x LTS, tested with 8.9.4. (From OE-Core rev: 2d7d2a460842c8747df17990970f22f4a11f36f6) Signed-off-by: Zoltán Böszörményi <zboszor@pr.hu> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06waf.bbclass: cd to ${S} before checking versionJoshua Watt
waf requires that the current working directory be the project root (in this case ${S} when it is invoked. The check to get the waf version was being executed as a prefunc for do_configure, which meant it was executed before the current working directory was switched to ${S}, and thus would fail with some recipes. Fix this by changing to ${S} before executing "waf --version" (From OE-Core rev: aa168ee7f785ff007ca645db57698883922b5eb3) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06image_types: tar with --numeric-ownerMax Krummenacher
If --numeric-owner is neither used when creating or extracting the archive containing the rootfs then tar tries to change the numeric uid/gid of the files based on user/group names of the host used to extract the archive. Create the archive with --numeric-owner to remove the burden of having to use --numeric-owner when extracting. (From OE-Core rev: 061e04cb6335a10f560e57255b7335b8c9891207) Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06sanity.bbclass: modified error messageJuro Bystricky
(From OE-Core rev: ed41167521ccae14952e500d7432cb776636f4e9) 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>
2018-02-06maintainers.inc: update maintainershipYi Zhao
Reassign some Robert Yang's recipes to Yi Zhao. Remove guile and mailx since these recipes were removed from oe-core. (From OE-Core rev: 9dc77b11f7e01d9fdf30b9aabe198d9a60c3cd3e) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06security_flags.inc, xorg-driver-common.inc: Move SECURITY_X_LDFLAGS logicTom Rini
We need to ensure that all xorg modules are linked with SECURITY_X_LDFLAGS to ensure that they will be able to resolve their run time dependencies. The approach of listing each driver in security_flags.inc lets less frequently used drivers be run-time broken. Move the flag logic into xorg-driver-common.inc so that all xorg modules from all layers will have the correct security flags used. Cc: Khem Raj <raj.khem@gmail.com> (From OE-Core rev: 27fce6ec277788f8fad0c9799e784df80f791120) Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06bitbake.conf: Add xattr to DISTRO_FEATURES_NATIVENiko Mauno
Commit db1f1adace58763c35774e3fdfeaac5c3ca646fd disabled 'xattr' from DISTRO_FEATURES when native packages are built, whereas for target packages it was retained. This changed eg. mtd-utils-native to build without extended attributes (capabilities) support from there on. Thus even setcap was called succesfully for a binary during pkg_postinst on build host, the capabilities did not exist on target rootfs due to now xattr-less host-side mkfs utility. Adding xattr to DISTRO_FEATURES_NATIVE restores previous behaviour, fixing the discontinuity in capability propagation to target device rootfs. (From OE-Core rev: 2ad3b8ae1c56a46bf14fc6bc4c34e4b3a568d741) Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-31tcmode-default.inc: drop preferred version of gzip-nativeMartin Jansa
* gzip was recently upgraded from 1.8 to 1.9, now all the builds show: NOTE: preferred version 1.8 of gzip-native not available (for item gzip-native) NOTE: versions of gzip-native available: 1.9 * drop the setting, because nobody is probably going to use older gzip-native than 1.4 when there is only 1.9 available in oe-core (From OE-Core rev: a0988c3374e964170d1d24fc230306b887432d31) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30pulseaudio: improve glibc 2.27 patchRoss Burton
This patch looks like it will be merged upstream. (From OE-Core rev: 59c5fb3c80eb1699caad8dc2175ab1eed67bf66e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30make: add missing Signed-off-byRoss Burton
(From OE-Core rev: 5282774e0a8df40a04808622e6d265157477488f) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30gettext: beat library detection into shapeRoss Burton
For reasons I can't explain gettext uses several hundred lines of convoluted m4 to find the paths to a library. If we don't tell it where to find a library it will hunt around and potentially have host contamination as /usr/lib on the host is explicitly searched. If we tell it the prefix to a library then we get bad RPATHs in the binaries (such as /usr/lib/../lib), and the search assumes that it knows best about what the library directories are under that prefix (even when it's wrong). So, replace the lookup where possible with pkg-config calls (libxml2, glib, libcroco). libunistring doens't have a pkgconfig file so just don't use the system libunistring: the library is tiny anyway. (From OE-Core rev: 1ff35fbbdd50660b86f8e254685ae0c8338b6e11) (From OE-Core rev: e6c0f8eddf8ff4a6132934a69e0f3450d4843ece) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30linux-yocto: update genericx86* SRCREVs for v4.9Anuj Mittal
Bump to stable kernel release 4.9.78. (From meta-yocto rev: 8a895e83a7a5c09d2f9f4069b8c8eb92d9b3b738) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30linux-yocto: update genericx86* SRCREVs for v4.4Anuj Mittal
Bump to stable kernel release 4.4.113. (From meta-yocto rev: 0cf39e1429549a11e6487906e89c830bdf985741) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30linux-yocto: update genericx86* SRCREVs for v4.12Anuj Mittal
Bump to stable kernel release 4.12.19. (From meta-yocto rev: 4c9ced4020f4cc3092af06889bf6ac209e15d5a6) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30tcmode-default.inc: bump LINUXLIBCVERSION to 4.14%Martin Jansa
* linux-libc-headers were updated without updating PREFERRED_VERSION causing following messages being shown in every single build: NOTE: preferred version 4.12% of nativesdk-linux-libc-headers not available (for item nativesdk-linux-libc-headers) NOTE: versions of nativesdk-linux-libc-headers available: 4.14.13 NOTE: preferred version 4.12% of linux-libc-headers not available (for item linux-libc-headers) NOTE: versions of linux-libc-headers available: 4.14.13 NOTE: preferred version 4.12% of linux-libc-headers not available (for item linux-libc-headers-dev) NOTE: versions of linux-libc-headers available: 4.14.13 NOTE: preferred version 4.12% of nativesdk-linux-libc-headers not available (for item nativesdk-linux-libc-headers-dev) (From OE-Core rev: df07a95f270492dba9fa04f917617b1aaee123b9) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30kexec-tools: remove unused patch fileJuro Bystricky
(From OE-Core rev: 1a28d928e5fd39bd23c420ba7cdeda79344a743b) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30libcrypt: remove unused patch fileJuro Bystricky
(From OE-Core rev: cd34a6dc9f0507ed3514c7fb333b313a0b0590c2) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30tzcode: remove unused patch filesJuro Bystricky
(From OE-Core rev: 7118b4df6d43de4d27426826ce2dce93b2baf9b4) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30gcc-7.3: Drop upstreamed musl cpuinfo patchKhem Raj
This patch is already in gcc-7-branch https://github.com/gcc-mirror/gcc/commit/6e6c7fc1e15525a10f48d4f5ac2edd853e2f5cb7 Thanks nsz for noticing it (From OE-Core rev: 3d9c32f31047e9fae289b45fcf733c5df1ddaceb) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30rootfs.py: change the notice about deferring scripts to first boot from ↵Alexander Kanavin
warning to a note Now that the first boot deferral needs to be requested explicitly, it's not really something to be concerned about. (From OE-Core rev: 19f3f4c60060ff5ed3c1c9871e18fcd4d128c5a3) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30package_rpm.bbclass: run pre/post installation scriptlets using sh -eAlexander Kanavin
This allows catching errors in the scriptlets which would otherwise go unnoticed, e.g. this sequence: ==== bogus_command proper_command ==== would work just fine. Note that this patch needs all of the preceding patches, as otherwise running failing scriptlets with -e would defer them to first boot, instead of properly reporting failure and aborting the package installation. (From OE-Core rev: 3cd8a55d5298ce9cc176e402fdb727abb26a1a4c) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30meta/lib/oe/package_manager.py: deprecate 'exit 1' as a way to defer to ↵Alexander Kanavin
first boot 'exit 1' is not optimal for two reasons: 1) Code is hard to read; it is not obvious that it means 'defer what follows to first boot'. 2) Worse, this hides actual errors in the scriptlets; there is no difference between scriptlet failing because it's intended to be run on target and scriptlet failing because there's a bug or a regression somewhere. The new, supported way is to place the code that has to run on target into pkg_postinst_ontarget(), or, if a more fine-tuned control is required, call 'postinst-intercepts defer_to_first_boot' from pkg_postinst() to explicitly request deferral to first boot. (From OE-Core rev: d12cf56e9ff2a4f13dfbef9290ea5647b52b3f6d) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30package.bbclass: add support for pkg_postinst_ontarget()Alexander Kanavin
This function is a convenient and more readable shortcut for situations when the postinst code always needs to run on target. All commands that cannot be executed during cross-install and can only be run on target should go into this function. They will only be executed on first boot (if package was cross-installed) or immediately during package installation on target. Plain pkg_postinst() works as before: it is run during cross-install time, it can contain a request to defer to first boot, and it is also run during package installation on target. Also fix the oeqa test for this functionality to use the new function where appropriate. (From OE-Core rev: 229f4e975fb6957f44b5c56735fd6d58564098d7) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30meta/lib/oe/rootfs.py: do not execute defer_to_first_boot when processing ↵Alexander Kanavin
postinst_intercept hooks That hook is empty, and doesn't need to be executed; it merely indicates that packages that have used it are requesting to defer their postinst scripts to first boot unconditionally. (From OE-Core rev: 939f7f1a06cd2db05aeb5e75a66322314e10aa6d) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30meta/lib/oe/rootfs.py: separate first boot deferral logic into a separate ↵Alexander Kanavin
function (From OE-Core rev: 4612291411ad788df88d5fc6dde98ff53fd91002) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30postinst_intercepts: add a delay_to_first_boot hookAlexander Kanavin
This allows postinsts scripts to explicitly request a deferral to first boot (by calling 'postinst_intercept delay_to_first_boot') instead of 'exit 1' which should be used only to indicate actual script failures. (From OE-Core rev: 853ac4a061e47c70b61e255c3cf6109d2058d2cc) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30ltp: bump to release 20180118Anders Roxell
Removed 3 patches that have been upstreamed: - 0030-lib-Use-PTHREAD_MUTEX_RECURSIVE-in-place-of-PTHREAD_.patch - 0037-ltp-fix-format-security-error.patch - 0038-generate-reproducible-gzip.patch Reworked path 0002-Add-knob-to-control-whether-numa-support-should-be-c.patch. (From OE-Core rev: a65081b27109393ff6ec29cd122c017bff637928) Signed-off-by: Anders Roxell <anders.roxell@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30bitbake.conf: Add comm to HOSTTOOLSNiko Mauno
This mitigates following issues during u-boot do_compile() step -- otherwise, if comm is not available, they are quietly ignored: .../scripts/check-config.sh: line 33: comm: command not found .../scripts/check-config.sh: line 39: comm: command not found Since 'comm' is provided by coreutils package, adding it to HOSTTOOLS was considered a lower impact fix compared to adding coreutils-native buildtime dependency to u-boot recipe. (From OE-Core rev: 6dc33687de9edd4269cbaf85e30945771f61f313) Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30ofono: use patch sent upstream instead of sedRoss Burton
Instead of using a sed to fix the hashbang in a test tool send a patch upstream and use that. This way we'll notice when the patch doesn't need to be applied anymore. (From OE-Core rev: 8b6c45dfdd6a7b469f5a0dd7308b25bdd4b1bf56) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30classes/utils: remove compatibility functionsRoss Burton
These base_* functions were moved into meta/lib/oe back in 2010 and wrappers left in utils.bbclass for compatibility. It's been eight years, so I think it's time to remove them. (From OE-Core rev: 0391fcad9103abca0796a068f957d0df63ab4776) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30meta: don't use deprecated functions from utils.bbclassRoss Burton
These functions were moved to meta/lib/oe in 2010 and the base_* functions in utils.bbclass were intended to be a short-term compatibility layer. They're still used in a few places, so update the callers to use the new functions. (From OE-Core rev: c97acbd034532895ce57c6717ed1b3ccc7900b0d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30bluez5: only depend on pygobject if its going to workRoss Burton
(From OE-Core rev: 5db515593d8a70e58a09e8db9327c5a3616945bf) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30ofono: only depend on pygobject if its going to workRoss Burton
(From OE-Core rev: 9a2d15d8360418890c40191644e22e830071b39d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30libxshmfence: fix build with glibc 2.27Ross Burton
With glibc 2.27 memfd_create() is behind a _GNU_SOURCE guard, so use AC_USE_SYSTEM_EXTENSIONS to define it. (From OE-Core rev: 88b3d730021107985ea749c92e52a323690f87dc) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30systemd: Fix build with glibc 2.27Khem Raj
(From OE-Core rev: cf4fc7804f093f5b570eaeaa39cb5dce5db1e379) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30pulseaudio: Fix build with glibc 2.27Khem Raj
memfd_create is now available in glibc (From OE-Core rev: 8f893588ff42db711763d0a8977b733df8389774) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30e2fsprogs: 1.43.7 -> 1.43.8Huang Qiyu
Upgrade e2fsprogs from 1.43.7 to 1.43.8. Backport patch to fix build on BE systems (From OE-Core rev: 6c7f32bd8b27c4dd91c1ac20f091358982e9c275) Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30perl: Undefine d_libm_lib_version.Daniel Díaz
A recent commit in GLIBC [1] got rid of _LIB_VERSION, which makes Perl's build fail: | pp.c:47:5: error: unknown type name '_LIB_VERSION_TYPE'; did you mean '__VERSION__'? | _LIB_VERSION_TYPE _LIB_VERSION = _IEEE_; | ^~~~~~~~~~~~~~~~~ | __VERSION__ | pp.c:47:38: error: '_IEEE_' undeclared here (not in a function); did you mean '_SIZET_'? | _LIB_VERSION_TYPE _LIB_VERSION = _IEEE_; | ^~~~~~ | _SIZET_ | make[1]: *** [pp.o] Error 1 The current config.sh enables d_libm_lib_version for everyone, with special cases left to undefine it as fixup (such as MUSL [2]). Since this may only affect some BSDs and Cygwin [3], it follows that the opposite (defining it) should be a fixup for those special cases. [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=813378e9fe17e029caf627cab76fe23eb46815fa [2] http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/perl/perl_5.24.1.bb?id=8ca61a5464743ff85b6d26886112750d6ddd13e0#n127 [3] https://perl5.git.perl.org/perl.git/blob/443bd156a6baaf7a8fe6b6b05fcf6c4178140ed2:/pp.c#l42 (From OE-Core rev: f01af4159fe8f75cb1d6a5cbce9cb73e1c8cc19f) Signed-off-by: Daniel Díaz <daniel.diaz@linaro.org> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30make: Backport fixes to not assume glibc internal glob implementationKhem Raj
Exposed with glibc 2.27 (From OE-Core rev: cdf370f1bd046ba6207b63c9a82bdfff2b261a7d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-06-11 20:22:22 +0000