summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
* conf: add maintainers.inc from meta-pokyRoss Burton2017-09-211-0/+825
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gawk: Enable native buildingNathan Rossi2017-09-181-0/+1
| | | | | | | | | | | | | | Also update the ASSUME_PROVIDED in bitbake.conf to contain gawk-native as the dependency is passed in via HOSTTOOLS for native builds. This allows for recipes to depend on gawk-native, and have the dependency met if not already provided by the host tools. (From OE-Core rev: cbc396dd10488990c98bb6fd94c7d10a736d57c1) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add default FILESYSTEM_PERMS_TABLESMark Hatle2017-09-181-0/+8
| | | | | | | | | | | | | | | | | | If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by the packages.bbclass. This made it difficult for a recipe or layer to 'append' to the default. Copy the default into the bitbake.conf, allowing future _append and += style actions. Default was remove from package.bbclass. If a value is not set, only the built-in perms fixes will be used. (From OE-Core rev: b65736e1b7161619a0c5972376d3e713ccf53850) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/conf/layers.conf: Add ca-certificates as ABISAFEMark Hatle2017-09-131-0/+1
| | | | | | | | | | | | | | | | | meta-oe was doing this before, but it was triggering a yocto-compat-script failure during the signature checking. The ca-certificates changing is ABISAFE, as the certificates themselves do not modify the compiles behavior of the applications. This should permit easier upgrades without as much rebuilding. The original value was set in meta-oe by commit ff7a4b13c4efeffc5853a93c6ff7265fa3d6c143. (From OE-Core rev: 583dca290c230fbc981c41fe91e8abeff616e633) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu conf: Fix kernel module autoloading for uvesafb on genericx86Alejandro Hernandez2017-09-133-3/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | After commit e8b1c653946ef921b65d47e52aea0dc530ef4286, we started seeing errors like the following during boot on genericx86 machines: uvesafb: failed to execute /sbin/v86d uvesafb: probe of uvesafb.0 failed with error -22 uvesafb: vbe_init() failed with -22 uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2) These were caused because the uvesa module was being loaded during boot, when it is only meant to be loaded on qemu according to: 6af89812e8a9931ffed63768ed85367519bf7aef Since genericx86-common.inc includes qemuboot-x86, the module also tries to be loaded on genericx86 machines, this patch removes the instruction from qemuboot-x86 and adds it in specific to both qemux86 machines confs so it is correctly loaded only on those. [YOCTO #11879] (From OE-Core rev: 261f9c382121c73b72556a151fdd4c7938b32a92) (From OE-Core rev: 554903483acb4af402feaba013366388db89e36b) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add bzr to HOSTTOOLS_NONFATALMartin Jansa2017-09-121-0/+3
| | | | | | | | | | | | | | | * it's used by bzr fetcher: meta/conf/bitbake.conf:FETCHCMD_bzr = "/usr/bin/env bzr" and when it isn't available in PATH do_fetch tasks fail with: /usr/bin/env: ‘bzr’: No such file or directory * it was also added in: https://patchwork.openembedded.org/patch/140107/ but this change wasn't merged (nor rejected AFAIS) (From OE-Core rev: c7ba7e9e7a7ca2caf453106112dc5a3c855b21d3) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: bump PR and fix install-efi and setup-live modulesCalifornia Sullivan2017-09-121-4/+4
| | | | | | | | | | | | | | | | | | | | Bump initramfs-framework PR, as it was missed in the previous initramfs-framework patch. These modules are shell scripts so they can be allarch. Fix the SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS in layer.conf, as these dependencies moved from the main recipe to these modules. Finally, set the PR to 4 in the new module recipes to avoid breaking package feeds. Fixes [YOCTO #12024]. (From OE-Core rev: d8af496dde699fadb2b21ff45cd20cf31e8abaf7) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add definition for BUILDSDK_CXXFLAGSChang Rebecca Swee Fun2017-08-311-0/+1
| | | | | | | | | | | | | | | | | | | | | ${BUILDSDK_CXXFLAGS} was introduced since commit 55c83cb239df5faf5e2143fffca47f2f16931cb3 cross.bbclass: override TARGET_* flags bitbake.conf has definitions for both ${BUILDSDK_CPPFLAGS} and ${BUILDSDK_CFLAGS} but there is none for ${BUILDSDK_CXXFLAGS}. This was a regression as in the past, CXXFLAGS is the same as CFLAGS in SDK environment. Adding definition for ${BUILDSDK_CXXFLAGS} will resolve CXXFLAGS being set wrongly in SDK environment. [YOCTO #11769] (From OE-Core rev: 073ca1cbd1b70d5b36618584a8c88cbba391a259) Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: Change recipe to be allarchOtavio Salvador2017-08-311-1/+5
| | | | | | | | | | | | | | | There is no COMPATIBLE_HOST in the recipe neither it makes sense for this to be machine specific. Possibly, initramfs-framework's based modules may be machine specific but if there is the case they can just RDEPENDS on initramfs-framework-base and provide the specific module as another recipe. (From OE-Core rev: 9a661bca9d9dd03627a5efaea0f9247394f05b0e) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Drop usage of build/BUILD_SYS and target/TARGET_SYS conf filesRichard Purdie2017-08-271-2/+0
| | | | | | | | | | | Its been highlighted that TARGET_SYS can be changed by MACHINE and DISTRO files so this doesn't work at all today. build/ configuration files also don't see to be used. Drop these forms of include files for those reasons and simplfy the code slightly. (From OE-Core rev: df61351b625fcd2e86aac7630944cc0403455de6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Add entries for pkgconfig (due to pkg-conf being added)Richard Purdie2017-08-241-0/+3
| | | | | | | | | This silences warnings generated after pkg-conf was added as an alternative pkgconfig provider. (From OE-Core rev: a8b89b3cf58fd3bc6c8f0cd3fd93a552818bc040) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: move some text from oe-setup-builddir to conf-notes.txtMing Liu2017-08-231-0/+5
| | | | | | | | | | | | | | This allows the end users to be able to override the entire notes showing on the shell console. For instance, Our company uses a external conf-notes.txt, and we run bitbake with some extra variables, looks like: F=xxx D=xxx M=xxx bitbake <target>, so we want to show exactly these texts on the shell console, that's why we need this change. (From OE-Core rev: 80bc8282df58dfeaae8f2f71ed2617d718e29f8b) Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: bump default version to 4.12Bruce Ashfield2017-08-232-2/+2
| | | | | | | | | | | Not all the qemu machines carry default kernel specifications. While we could drop these references, we'll bump them to 4.12 to pick up the latest and remove them in future commits. (From OE-Core rev: c58df63d88a07d3275e7337f7d284b0a50db82cc) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libc-headers: update to 4.12Bruce Ashfield2017-08-231-1/+1
| | | | | | | | | | | | The fall 2017 kernel will have 4.12 as the reference kernel, so we update the libc-headers to match. Build tested against glibc and muslc systems. (From OE-Core rev: 4b5cce1c691e991c80d255a4900220068ff6f062) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine-sdk: oldest kernel for x86/x86_64 is 3.2.0 nowRuslan Bilovol2017-08-233-3/+0
| | | | | | | | | | | | | | | | | With glibc upgrade to 2.26 release (commit d6a0bc57fa07 "glibc: Upgrade to 2.26 final release") it's not possible to build x86/x86_64 SDK for kernels lower than 3.2.0 (see glibc commit 139ace95756a "Require Linux kernel 3.2 or later on x86 / x86_64.") Thus drop SDK_OLDEST_KERNEL overrides from machine-specific conf files, so default version 3.2.0 from conf/bitbake.conf will be picked up. (From OE-Core rev: 0724896f7a2092abf2f3bafa9fac96c5210d39a5) Signed-off-by: Ruslan Bilovol <rbilovol@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl10: rename back to openssl and make it the default via PREFERRED_VERSIONAlexander Kanavin2017-08-191-0/+3
| | | | | | | | | | | | | | | | openssl 1.1 broke 3rd party layers a lot more than was expected; let's flip the switch at the start of next development cycle. Add a PROVIDES = "openssl10" to openssl 1.0 recipe; any dependency that is not compatible with 1.1 should use that in its DEPENDS, as the 1.0 recipe will later be renamed back to openssl10. This does not always work: http://lists.openembedded.org/pipermail/openembedded-core/2017-August/140957.html but for many recipes it does. (From OE-Core rev: 5585103c195104e85ed7ac1455bef91b2e88a04d) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu conf: replace deprecated option with new optionChen Qi2017-08-194-4/+4
| | | | | | | | | | | | Replace the deprecated '-usbdevice' option with '-device usb-xx' option. This would fix runqemu boot error like below. '-usbdevice' is deprecated, please use '-device usb-...' instead (From OE-Core rev: 2f1f3480d344f8521e01f456d2dcd6c4e989ec59) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add VOLATILE_LOG_DIR variableChen Qi2017-08-181-0/+4
| | | | | | | | | | | | | | | The default value is "yes" which results in the /var/log being a link pointing to /var/volatile/log which is on tmpfs. Setting valid boolean false value ('no', 'n', 'false', 'f', '0') would make /var/log to be a directory on persistent storage. [YOCTO #6132] (From OE-Core rev: 016bafce52f74462dc8f21a1c1b43ba2e6e59442) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.29Khem Raj2017-08-161-1/+1
| | | | | | | (From OE-Core rev: 3bf990eb275f63190a2cf7253527d6d49fd93f1a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: add a 1.1 versionAlexander Kanavin2017-08-131-0/+3
| | | | | | | | | | | | | | | | Existing openssl 1.0 recipe is renamed to openssl10; it will continue to be provided for as long as upstream supports it (and there are still several recipes which do not work with openssl 1.1 due to API differences). A few files (such as openssl binary) are no longer installed by openssl 1.0, because they clash with openssl 1.1. (From OE-Core rev: da1183f9fa5e06fbe66b5b31eb3313d5d35d11e3) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Upgrade to 2.26 final releaseKhem Raj2017-08-131-1/+1
| | | | | | | | (From OE-Core rev: d6a0bc57fa07d887a78aa8ed76e3bf4558dc5127) 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>
* x86-base.inc: enable live image typeEd Bartosh2017-08-091-1/+2
| | | | | | | | | | | | | | | | | | | live image type was replaced by hddimg recently. This made NOHDD and NOISO options ineffective as they only influence live builds. It also causes image building failure for image sizes >4Gb Returned back live image type and disabled building iso image. This doesn't change result (hddimg is built), but it makes NOHDD and NOISO working as expected. [YOCTO #11842] (From OE-Core rev: c787dcdd55bc55c6c64dec21b251706615114fe7) 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>
* bitbake.conf: whitelist BB_SERVER_TIMEOUT from config hashPaul Eggleton2017-08-091-1/+1
| | | | | | | | | | We don't need to reparse recipes just because BB_SERVER_TIMEOUT changed, so exclude it from the config hash. (From OE-Core rev: a686fcabacd49fdb814e646305c1f33fee1d5abf) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemux86 qemux86-64: Enable pciHe Zhe2017-08-092-2/+2
| | | | | | | | | | lspci and some other software require "pci" in MACHINE_FEATURES and PCI is valid in the qemux86* context. (From OE-Core rev: aec9a159dbc7a78953da73ba9dfccc9e9c9514a7) Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: drop do_bootdirectdisk do_vmimg referencesMing Liu2017-08-031-1/+0
| | | | | | | | | | | | do_bootdirectdisk and do_vmimg had been dropped by commit 929ba563: [ image: Convert vmdk/vdi/qcow2 to strict CONVERSION_CMD types ] Also drop the references to them and image-vm. (From OE-Core rev: 609f7f4ecd17c8299b97d9face098e3cc44fa6eb) Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative: Update to 1.7 uninative releaseRichard Purdie2017-07-301-3/+3
| | | | | | | | | This updates to a newer glibc and updates patchelf to include a bugfix to work with gold. (From OE-Core rev: a2ab288bd002ebb6e64d46e941fb122e1157ff49) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icu: update to 59.1Alexander Kanavin2017-07-271-4/+0
| | | | | | | | | | | | | | | License checksum change due to copyright year update. Latest icu will not compile with anything less than C++11, so drop the enforcement of an earlier C++ version. This should be okay, as there is now a fix in place for the problem of mixing native gcc 4/5 compiled code: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c21cec84886d9c70396e9be0ceb9a8ef300b54be (From OE-Core rev: b002f44ed5a07b42deb8cccdb192e12091cd654f) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* licenses.conf: enable CDDLv1 licenseMartin Kelly2017-07-211-0/+4
| | | | | | | | | | | The CDDL license is now used by open-vm-tools in meta-openembedded, so we need to add it in order to prevent warnings. (From OE-Core rev: 0dd9db29e56c75181219bb0dbac88a91989b702b) Signed-off-by: Martin Kelly <mkelly@xevo.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/sanity: Update minimum bitbake verison to 1.35.0 for server reworkRichard Purdie2017-07-211-1/+1
| | | | | | (From OE-Core rev: b63fcffe8b6a3f94d4812cd03fb974e173eff3e5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distro_alias.inc: update unmap packages to other distroShen Joon Tan2017-07-171-0/+7
| | | | | | | | | | | | | | | Added packages with different names or based on sources that generates multiple binaries eg: python-pycurl source generates python3-pycurl as well. Currently, some of these packages are not displayed as part of other distro due to naming differences on the source rather than the binaries as a single source could produce multiple binaries with different names. (From OE-Core rev: aed3cebdfbd4f483644a8c200f27d52b981728a3) Signed-off-by: Shen Joon Tan <shen.joon.tan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add CCACHE_NOHASHDIR to hash whitelistRoss Burton2017-07-171-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache: don't export CCACHE_DISABLE globallyRoss Burton2017-07-171-4/+1
| | | | | | | | | | | | | | | CCACHE_DISABLE was added to bitbake.conf in oe-core dd2bab (June 2012) because autogen-native exports HOME=/dev/null during the build, which is then used by a host ccache to construct the path to it's cache (/dev/null/.ccache) and this fails. However we now always export CCACHE_DIR to solve the same problem in a more efficient way so CCACHE_DISABLE can be deleted. (From OE-Core rev: ef33a3138384667f819688141086102e6e83ec44) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x86-base: build only hddimg, rather than iso and hddimg, for x86 machinesJoshua Lock2017-07-171-1/+1
| | | | | | | | (From OE-Core rev: 1e05d488f9f09230d2f7cd3f43a385ad206066f8) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* world-broken.inc: Remove packages which are now buildable on muslKhem Raj2017-07-111-25/+0
| | | | | | | | | | | Delete the pinnings which are no longer required during world builds becasue they have been fixed to build on musl (From OE-Core rev: b82bc7f003d2133e818be5bd473e9c640d4b10bf) 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>
* glibc: Upgrade to 2.25.90Khem Raj2017-07-111-1/+1
| | | | | | | | | Eventually it will be released as 2.26 final (From OE-Core rev: 5a58883258206893d15990953c8691b05473eecb) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: Do not build gcc for powerpc with PIE defaultsKhem Raj2017-07-081-0/+1
| | | | | | | | | | | Since we have disabled FPIE from SECURITY_CFLAGS already, we have to ensure the same with gcc, otherwise gcc (on-device) will be built defaulting to PIE, and such binaries will fail to execute (From OE-Core rev: 4f3a9ccdb1d45804f4c094589e69e0bc87dc9c62) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: Delete pinnings for SECURITY_NO_PIE_CFLAGSKhem Raj2017-07-081-61/+22
| | | | | | | | | GCC is configured correctly to pass PIE cflags/ldflags (From OE-Core rev: e93765ffb5718b0fce84f0b8123963176dea95e4) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Introduce a knob to configure gcc to default to PIEKhem Raj2017-07-081-1/+3
| | | | | | | | | | | | GCCPIE flag which is empty by default adds "--enable-default-pie" configure option for harderned distros We do not require to add -fpie -pie flag externally anymore (From OE-Core rev: 1c7e195c94764d680a12a49b870f04cd58860f81) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: support for merged usr with DISTRO_FEATURE usrmergeAmarnath Valluri2017-07-061-4/+6
| | | | | | | | | | | A new configuration variable ${root_prefix} added, which shall be used by all base_{lib,bin,sbin}dir variables. When usrmerge DISTRO_FEATURE is enabled ${root_prefix} points to ${exec_prefix} otherwise to ${base_prefix} (From OE-Core rev: 700848c6ebd03bf3105d09a41d758883ab875618) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* v86d, qemuboot-x86.inc: use KERNEL_MODULE_AUTOLOAD+KERNEL_MODULE_PROBECONF ↵Martin Jansa2017-06-281-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | for uvesafb instead of fbsetup init script * also add UVESA_MODE variable for easier change of resolution and respect it in QB_KERNEL_CMDLINE_APPEND as well * don't use init script just to call modprobe * I wasn't able to test this all the way with runqemu, because runqemu doesn't work on my system, but I've verified that the right params appear there and that I can easily change UVESA_MODE from conf/local.conf, the modules.d and modprobe.d files look OK: OE qemux86@ ~/build/oe-core/tmp-glibc/deploy/images/qemux86/core-image-sato-qemux86-20170427212613.rootfs $ cat etc/modules-load.d/uvesafb.conf uvesafb OE qemux86@ ~/build/oe-core/tmp-glibc/deploy/images/qemux86/core-image-sato-qemux86-20170427212613.rootfs $ cat etc/modprobe.d/uvesafb.conf options uvesafb mode_option=1600x1200-32 so I'll be able to drop this KERNEL_MODULE_AUTOLOAD + KERNEL_MODULE_PROBECONF from my DISTRO conf. (From OE-Core rev: f7ba5b5f76bb5678ca3e6ad51586f25871f7a9fb) 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>
* x86-base.inc: Don't add live to IMAGE_FSTYPES, default insteadCalifornia Sullivan2017-06-281-1/+1
| | | | | | | | | | Using += makes it difficult to remove. Soft-set with ?= instead. (From OE-Core rev: df850ff9e101afcc9983f907570abaf17421ba0f) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/conf/layer.conf: bump layer version for LSB changesRoss Burton2017-06-281-1/+1
| | | | | | | | | | | As oe-core has just dropped a number of recipes that were for LSB conformance, bump the layer version so we can also remove meta-qt4 from the autobuilder. (From OE-Core rev: 179b7ae2511974173ae4aa72dfb49384ff69c2e5) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-flags.inc: do not default to old C++ ABIAlexander Kanavin2017-06-281-6/+0
| | | | | | | | | | | This was needed for interoperability between code compiled with gcc 4 and 5; there should be now a different fix for the issue: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c21cec84886d9c70396e9be0ceb9a8ef300b54be (From OE-Core rev: 80791bd2d58c2e56b0dfbd2f0d43db8c90841ee4) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bdwgc: remove the recipeAlexander Kanavin2017-06-281-1/+0
| | | | | | | | | It will be moved to meta-oe, but nothing needs it in oe-core anymore. (From OE-Core rev: fbee171c29a8ee64fd4db62ab56df0df7b8083c3) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-pycurl: remove the recipeAlexander Kanavin2017-06-281-1/+0
| | | | | | | | | | Nothing is using it in oe-core or meta-oe layers. (From OE-Core rev: 17a65f6a02ef93bfc337dd5f18ecd2201bce1002) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bitbake.conf: Add sdl-config to HOSTTOOLS if using host SDL"Richard Purdie2017-06-271-3/+0
| | | | | | | | This clearly wasn't tested as the correct variable is ASSUME_PROVIDED. This reverts commit 91cee064332969207334cd1ee5c31d02610281fc. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuboot.conf: make cpus match built artifactsMartin Kelly2017-06-231-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | Currently, the qemu CPUs for are specified as generic, but the built artifacts are not. For example, we build x86-64 artifacts targeting core2duo but run them in qemu with generic qemu/kvm CPUs. This causes some packages that take advantage of the host architecture to crash because they try to use CPU features not advertised by qemu. As an example, Qt uses ssse3. When artifacts linked against Qt and built targeting core2duo attempt to run on a generic qemu/kvm CPU, we get the following crash: Incompatible processor. This Qt build requires the following features: ssse3 We could fix this by making packages like Qt not take advantage of CPU features. However, we will probably keep facing similar issues over time, so it's better to resolve them in a more enduring way. Fix this by making the qemu -cpu arguments match the built artifacts. (From OE-Core rev: 20b3574749420a1fef2cb2e0579584453dd4c5c5) Signed-off-by: Martin Kelly <mkelly@xevo.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kconfig-frontends: Remove as only needed for eglibcRichard Purdie2017-06-221-1/+0
| | | | | | | | This was only added for eglibc. That is gone so we can drop this too. (From OE-Core rev: 7c36b4316ad185088c65a4db8a84b5fcba9eef06) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Drop remnants of uclibc supportRichard Purdie2017-06-222-7/+0
| | | | | | | | | | | | | | uclibc support was removed a while ago and musl works much better. Start to remove the various overrides and patches related to uclibc which are no longer needed. uclibc support in a layer would still be possible. I have strong reasons to believe nobody is still using uclibc since patches are missing and I doubt the metadata even parses anymore. (From OE-Core rev: 653704e9cf325cb494eb23facca19e9f05132ffd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bitbake.conf: DISTRO_FEATURES as overrides"Patrick Ohly2017-06-141-16/+1
| | | | | | | | | | | | | | | | This reverts commit 3b3ae91a22d6f685e804df4f32cdeebe1bd6bd88. It turned out that the code which expands DISTRO_FEATURES early during base config parsing can fail because some entries in DISTRO_FEATURES might call Python functions like base_conditional() from base.bbclass which aren't defined yet. A different solution will be needed. (From OE-Core rev: 0c6e4a14ba8d9d9701ec16ffe46d618f41633571) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-18 20:30:30 +0000