aboutsummaryrefslogtreecommitdiffstats
path: root/meta/conf
AgeCommit message (Collapse)Author
2017-08-30bitbake.conf: add definition for BUILDSDK_CXXFLAGSChang Rebecca Swee Fun
${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] Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-30initramfs-framework: Change recipe to be allarchOtavio Salvador
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. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-27bitbake.conf: Drop usage of build/BUILD_SYS and target/TARGET_SYS conf filesRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-24default-providers: Add entries for pkgconfig (due to pkg-conf being added)Richard Purdie
This silences warnings generated after pkg-conf was added as an alternative pkgconfig provider. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-23meta: move some text from oe-setup-builddir to conf-notes.txtMing Liu
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. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-23qemu: bump default version to 4.12Bruce Ashfield
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. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-23libc-headers: update to 4.12Bruce Ashfield
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. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-23machine-sdk: oldest kernel for x86/x86_64 is 3.2.0 nowRuslan Bilovol
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. Signed-off-by: Ruslan Bilovol <rbilovol@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-19openssl10: rename back to openssl and make it the default via PREFERRED_VERSIONAlexander Kanavin
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. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-19qemu conf: replace deprecated option with new optionChen Qi
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 Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-17bitbake.conf: add VOLATILE_LOG_DIR variableChen Qi
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] Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-16binutils: Upgrade to 2.29Khem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-11openssl: add a 1.1 versionAlexander Kanavin
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. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-08-11glibc: Upgrade to 2.26 final releaseKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-08-09x86-base.inc: enable live image typeEd Bartosh
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] Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-08-08bitbake.conf: whitelist BB_SERVER_TIMEOUT from config hashPaul Eggleton
We don't need to reparse recipes just because BB_SERVER_TIMEOUT changed, so exclude it from the config hash. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-03qemux86 qemux86-64: Enable pciHe Zhe
lspci and some other software require "pci" in MACHINE_FEATURES and PCI is valid in the qemux86* context. Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-03meta: drop do_bootdirectdisk do_vmimg referencesMing Liu
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. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-30uninative: Update to 1.7 uninative releaseRichard Purdie
This updates to a newer glibc and updates patchelf to include a bugfix to work with gold. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-27icu: update to 59.1Alexander Kanavin
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 Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-21licenses.conf: enable CDDLv1 licenseMartin Kelly
The CDDL license is now used by open-vm-tools in meta-openembedded, so we need to add it in order to prevent warnings. Signed-off-by: Martin Kelly <mkelly@xevo.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-07-21conf/sanity: Update minimum bitbake verison to 1.35.0 for server reworkRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-17distro_alias.inc: update unmap packages to other distroShen Joon Tan
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. Signed-off-by: Shen Joon Tan <shen.joon.tan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-07-17bitbake.conf: add CCACHE_NOHASHDIR to hash whitelistRoss Burton
2017-07-17ccache: don't export CCACHE_DISABLE globallyRoss Burton
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. Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-07-17x86-base: build only hddimg, rather than iso and hddimg, for x86 machinesJoshua Lock
Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-07-11world-broken.inc: Remove packages which are now buildable on muslKhem Raj
Delete the pinnings which are no longer required during world builds becasue they have been fixed to build on musl Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-07-11glibc: Upgrade to 2.25.90Khem Raj
Eventually it will be released as 2.26 final Signed-off-by: Khem Raj <raj.khem@gmail.com>
2017-07-08security_flags.inc: Do not build gcc for powerpc with PIE defaultsKhem Raj
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 Signed-off-by: Khem Raj <raj.khem@gmail.com>
2017-07-08security_flags.inc: Delete pinnings for SECURITY_NO_PIE_CFLAGSKhem Raj
GCC is configured correctly to pass PIE cflags/ldflags Signed-off-by: Khem Raj <raj.khem@gmail.com>
2017-07-08gcc: Introduce a knob to configure gcc to default to PIEKhem Raj
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 Signed-off-by: Khem Raj <raj.khem@gmail.com>
2017-07-06bitbake.conf: support for merged usr with DISTRO_FEATURE usrmergeAmarnath Valluri
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} Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-06local.conf.sample: drop image-swab referenceMing Liu
The image swabber had been dropped by commit e18657df: [ meta: Drop swabber ] We need also drop its reference in local.conf. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-06-28v86d, qemuboot-x86.inc: use KERNEL_MODULE_AUTOLOAD+KERNEL_MODULE_PROBECONF ↵Martin Jansa
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. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-06-28x86-base.inc: Don't add live to IMAGE_FSTYPES, default insteadCalifornia Sullivan
Using += makes it difficult to remove. Soft-set with ?= instead. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-06-28meta/conf/layer.conf: bump layer version for LSB changesRoss Burton
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. Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-06-28uninative-flags.inc: do not default to old C++ ABIAlexander Kanavin
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 Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-06-28bdwgc: remove the recipeAlexander Kanavin
It will be moved to meta-oe, but nothing needs it in oe-core anymore. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-06-28python-pycurl: remove the recipeAlexander Kanavin
Nothing is using it in oe-core or meta-oe layers. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-06-27Revert "bitbake.conf: Add sdl-config to HOSTTOOLS if using host SDL"Richard Purdie
This clearly wasn't tested as the correct variable is ASSUME_PROVIDED. This reverts commit 91cee064332969207334cd1ee5c31d02610281fc.
2017-06-23qemuboot.conf: make cpus match built artifactsMartin Kelly
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. 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>
2017-06-22kconfig-frontends: Remove as only needed for eglibcRichard Purdie
This was only added for eglibc. That is gone so we can drop this too. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-16meta: Drop remnants of uclibc supportRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-14Revert "bitbake.conf: DISTRO_FEATURES as overrides"Patrick Ohly
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. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-14gcc: Add recipes for gcc-7Khem Raj
Switch default compiler to gcc 7 Signed-off-by: Khem Raj <raj.khem@gmail.com>
2017-06-14bitbake.conf: Don't exclude MACHINE/MACHINEOVERRIDES from hashesRichard Purdie
A long time ago (6 years), this seemed like a good idea. The reality is that OVERRIDES should not be being added to hashes and if it is, it likely needs excluding in its own right. This was a nice workaround but we need to fix the real underlying issues now. In some cases this means excluding OVERRIDES from the variables dependency using the vardepsexclude flag however caution is needed to ensure this is safe. Variable values used to construct hashes are unexpanded but the values used are computed after the application of OVERRIDES. The important detail is if the end resulting unexpanded value changes, not the value of the OVERRIDES used in the construction of that unexpanded value. This is why dependencies on OVERRIDES itself shouldn't be in the hashes in general. The recent DISTRO_FEATURES changes adding in override mappings for them highlighted this issue. We have some good sstate tests which are effective at highlighting where potential issues arrive with OVERRIDES contamination (oe-selftest -r sstatetests.SStateTests). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-12bitbake.conf: DISTRO_FEATURES as overridesPatrick Ohly
As discussed in "[Openembedded-architecture] Yocto Compatible 2.0 + signature changes", changes in .bbappend must depend on some explicit configuration change, typically selecting a distro feature. For _append and _remove, adding an override that is set only when the corresponding entry is in DISTRO_FEATURES achieves that: In local.conf: DISTRO_FEATURES_append = " my-distro-feature" In layer.conf: DISTRO_FEATURES_OVERRIDES += "my-distro-feature" In a .bbappend: do_install_append_df-my-distro-feature () { ... } The subset of DISTRO_FEATURES that are made available as overrides must be configured explicitly because using them this way should be a conscious decision. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-12bitbake.conf: add BB_CMDLINE to BB_HASHCONFIG_WHITELISTPaul Eggleton
We really don't want the just-introduced BB_CMDLINE influencing the config hash. Part of the fix for [YOCTO #11634]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-06-12gdb: Upgrade to 8.0 releaseKhem Raj
For details on changes see http://lists.gnu.org/archive/html/info-gnu/2017-06/msg00002.html in tcmode-default.inc Pin gdb to 8.0 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-06-09meta*: Add LAYERSERIES_COMPAT and LAYERSERIES_CORENAMES markup to layer.confRichard Purdie
This means mismatched layers are more clearly identified to the user in cases where compatibility has not been tested. This is perhaps not as needed for the core repository (other than CORENAMES) but lets lead by example. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-19 14:03:39 +0000