summaryrefslogtreecommitdiff
path: root/meta/conf
AgeCommit message (Collapse)AuthorFiles
2015-02-07Revert "bitbake.conf: don't remove WARN_QA and ERROR_QA from hashes"Ross Burton1
It turns out that changing WARN_QA and ERROR_QA results in do_configure's QA postfunc re-executing, so changing a QA test results in a complete rebuild. This is just too much and the lesser evil of needing to do a full rebuild to verify changed QA flags is preferable to an enforced full rebuild. This reverts commit daecfc3438122b5d146a59a5053e57006d55ccc4. Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-02-03opkg-arch-config: Renamed from opkg-config-basePaul Barker1
The name 'opkg-arch-config' is much more descriptive. Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
2015-02-03bitbake.conf: don't remove WARN_QA and ERROR_QA from hashesRoss Burton1
Changing WARN_QA and ERROR_QA should cause do_package_qa to re-execute, so removing them from the sstate hashes is harmful. They were added back when sanity testing was part of packaging and this was the lesser evil, compared to changing sanity tests causing a re-package of everything. Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-01-29security_flags: disable PIE on expectRoss Burton1
Disable PIE in expect as otherwise it tries to link the shared library as an executable. Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-01-29bitbake.conf: add PKGDATA_DIR to BB_HASHBASE_WHITELISTTing Liu1
In meta/conf/bitbake.conf, PKGDATA_DIR is default to: PKGDATA_DIR = "${STAGING_DIR_HOST}/pkgdata" But in meta/conf/multilib.conf, PKGDATA_DIR is set as: PKGDATA_DIR = "${STAGING_DIR}/${MACHINE}/pkgdata" When multilib enabled, linux-libc-headers cache will be machine specific: $ bitbake-diffsigs sstate-cache/1a/sstate:linux-libc-headers:ppce6500-poky-linux:3.17.7:r0:ppce6500:3:1a0c3934d91479fd7242a5b1d407d155_package.tgz.siginfo sstate-cache/28/sstate:linux-libc-headers:ppce6500-poky-linux:3.17.7:r0:ppce6500:3:28c918e8f9f4a4cfceb3a38b258f7501_package.tgz.siginfo basehash changed from 8d3158bbddcee612fa30badd05f47b8e to 68ac258fc6c8e489f360fde3123a5894 Variable MACHINE value changed from 'b4420qds' to 'b4860qds' Signed-off-by: Ting Liu <ting.liu@freescale.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-01-29arch-mips.inc: Change definition of TRANSLATED_TARGET_ARCHMark Hatle2
[YOCTO #7230] In certain system configurations TRANSLATED_TARGET_ARCH will not expand in the right order for gcc-cross-candian-mips64n32 to be generated properly. This will cause SDKs to fail to generate properly. Changing the global definition of TRANSLATED_TARGET_ARCH always expands the ABIEXTENSION, which causes the OVERRIDES to pick it up as well. This effectively defines a new class of overrides for the 'n32'. The side effect is that we need to duplicate some mips64 overrides, and redefine others that were previously 'n32' or 'mips64' exclusive to have the correct semantics. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2015-01-29feature-arm-thumb.inc: Remove extra space on thumb overrideMark Hatle1
The extra space makes the overrides look like "foo:bar: thumb:foobar". This may prevent thumb from working properly, and the space was never intended in the original fix. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2015-01-28gcc-sanitizers: fix licensingDan McGregor1
The sanitizer runtime library is dual-licensed under the NCSA and MIT licenses. Also make nativesdk-gcc-sanitizers use SDKGCCVERSION by default instead of GCCVERSION Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-01-23elfutils: upgrade to 1.161Hongxu Jia1
Drop PREFERRED_VERSION_elfutils in meta/conf/distro/include/ tcmode-default.inc, it builds the latest version by default. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2015-01-23gcc-sanitizers: Enable GCC sanitizersDan McGregor2
AddressSanitizer is a fast memory error detector. ThreadSanitizer detects data races. UBSanitizer detectes undefined behaviour. All consist of compiler instrumentation and a run-time library. The compiler instrumentation was already enabled, this builds the run-time library component. Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
2015-01-21arch-mips.inc: Add the MIPS ABIEXTENSION to toolchain nameMark Hatle1
[YOCTO #7143] When the system is configured for a multilib SDK, such as: require conf/multilib.conf MULTILIBS = "multilib:lib32 multilib:lib64" DEFAULTTUNE = "mips32r2" DEFAULTTUNE_virtclass-multilib-lib32 = "mips64-n32" DEFAULTTUNE_virtclass-multilib-lib64 = "mips64" Only one of the mips64-n32 or mips64 toolchains is built. Causing the other to be unavailable. This is due to both recipes ending up with the same PN. The toolchain uses the TRANSLATED_TARGET_ARCH in it's name, however the target for mips64 and mips64 n32 were the same, causing the conflict. Avoid this conflict by adding the ABIEXTENSION to the name. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-01-16security_flags: disable pie support for libaio, blktrace and ltpSaul Wold1
libaio when built with pie and fpie does not link correctly with blktrace or ltp so we need to disable those flags until a better solution comes along. Signed-off-by: Saul Wold <sgw@linux.intel.com>
2015-01-16BAD_RECOMMENDATIONS also works for RPM packaging.Robert P. J. Day1
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-01-16kernel: move source and build output to work-sharedBruce Ashfield1
commit 3b3f7e785e279 [kernel: Rearrange for 1.8] began the process of moving the kernel source and build artefacts out of sstate control and into a shared location. This changed triggered some workflow issues, as well as bugs related to the kernel source containing build output, and hence being dirty and breaking kernel rebuilds. To solve these issues, and to make it clear that the kernel is not under sstate control, we move the source and build outputs to: work-shared/MACHINE/kernel-source work-shared/MACHINE/kernel-build-artifacts Where kernel-build-artifacts is the kernel build output and kernel-source is kept "pristine". The build-artifacts contain everything that is required to build external modules against the kernel source, and includes the defconfig, the kernel-abiversion, System.map files and output from "make scripts". External module builds should either pass O= on the command line, or set KBUILD_OUTPUT to point to the build-artifacts. module-base.bbclass takes care of setting KBUILD_OUTPUT, so most existing external module recipes are transparently adapted to the new source/build layout. recipes that depend on the kernel source must have a depedency on the do_shared_workdir task: do_configure[depends] += "virtual/kernel:do_shared_workdir" With this dependency added, the STAGING_KERNEL_DIR will be populated and available to the rest of the build. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-30local.conf.sample: Add qemuarm64Mark Hatle1
Add an example machine configuration for qemuarm64. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-25elfutils: Update PREFERRED_VERSION after upgradeSaul Wold1
Since we normally fix the version of elfutils in tcmode-default, this needs to be updated after we upgrade the recipe itself. Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-22aarch-arm64: Update tune filesMark Hatle3
arch-arm64 is the base tune file for aarch64. Update this to allow the system to work with both aarch32 and aarch64 (multilib). arch-armv8 is for compatibility, it simply uses the base config for now. feature-arm-thumb was updated, since aarch64 mode does NOT have thumb support. We should only be processing warnings and additional arguments if thumb support is enabled on the processor core. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-21Add machine qemuarm64Kai Kang2
Add machine qemuarm64. The configure files are derived from linaro. Update: * rename genericarmv8 to qemuarm64 for coordination in oe-core * include qemu.inc then remove common part of config * disable using autoserial * move arch-armv8.inc from machine/include/arm64 to machine/include/arm [YOCTO #6487] Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20linux-libc-headers: Upgrade 3.17 -> 3.17.7Richard Purdie1
Whilst we don't usually take linux-libc-headers point release, 3.17.3 fixes a userspace header issue which caused gdb to fail to build on mips. We therefore may as well upgrade to the latest point release. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20linux-libc-headers: update to 3.17Bruce Ashfield1
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-20sanity: TMPDIR ABI change for kernel processRichard Purdie1
The kernel source is being moved into the sysroot, to do this and preserve previous builds, we need to change the TMPDIR ABI and provide a function to uninstall all kernels from the sysroot. This change adds code to do that and increases the ABI number. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-19security_flags: Fix typo for cupsRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-19default-versions.inc: let INCOMPATIBLE_LICENSE supports wildcardHongxu Jia1
While wildcard in INCOMPATIBLE_LICENSE, such as INCOMPATIBLE_LICENSE = "*GPL-3", PREFERRED_VERSION_db-native could have the correct value "5.%" [YOCTO #5592] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2014-12-19base/license.bbclass: expand wildcards in INCOMPATIBLE_LICENSEHongxu Jia1
The whitelist processing in code in base.bbclass does not play well with wildcards in INCOMPATIBLE_LICENSES. The code expects bad_licenses to contain actual license names, not wildcards. Add incompatible_license_contains to replace bb.utils.contains( "INCOMPATIBLE_LICENSE", **, **, **, d) [YOCTO #5592] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
2014-12-11bluez-hcidump: select provider as bluez4 or bluez5Peter A. Bigot1
bluez-hcidump was a separate package in bluez4, but was integrated into bluez5. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2014-12-05tcmode-default.inc: use GCCVERSION for gcc-sourceKoen Kooi1
This was missing leading to gcc-source-<foo> being built when using gcc-cross-<bar> with GCCVERSION=bar. Signed-off-by: Koen Kooi <koen.kooi@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-12-05default-distrovars: add gcc-source recipe to the GPLv3 whitelistRoss Burton1
gcc-source is a convenience recipe to save duplicate copies of the GCC source tree and should be whitelisted for GPLv3 avoidance along with the rest of GCC. Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-12-03bitbake.conf: remove internal flags from BB_SIGNATURE_EXCLUDE_FLAGSRoss Burton1
As the code that uses BB_SIGNATURE_EXCLUDE_FLAGS uses d.getVarFlags() so doesn't get to see the internal flags, remove _append and _prepend. Also defaultval is now _defaultval and thus internal, so remove that too. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-03sanity.conf: Update to require bitbake 1.25.0 as minimum versionRichard Purdie1
This allows us to merge in the _defaultval changes. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-11-28toaster: naming and description changesBelen Barros Pena1
Some minor changes to the names and descriptions used in the Toaster configuration file: * Change the name of the local layer source from Local OE-Core to Local OpenEmbedded * Change the imported layer source name from User Imported Layers to just Imported layers. It is shorter, which helps table display * Change the description of the master release from OE-Core master to OpenEmbedded master * Change the description of the dizzy release from OE-Core dizzy to OpenEmbedded Dizzy * Change the helptext of the dizzy release to remove the "latest" reference, which can make maintenance hard * Change the name of the Local Yocto Project release to Local OpenEmbedded Signed-off-by: Belen Barros Pena <belen.barros.pena@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-11-25bitbake.conf: pseudo fall back to last-resort passwd filesPeter A. Bigot1
Recipe packaging for the target requires permissions that are consistent with meta/files/fs-perms.txt which specifies certain user and group names. In the early parts of a target build base-passwd is not yet available to provide the target /etc files used for user/group lookup. Allow pseudo to fall-back to the last-resort files it installs if the target ones aren't there yet. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2014-11-21toaster: add toaster layer configuration filesAlexandru DAMIAN1
In managed mode, Toaster creates project configurations based on the layers that are being checked-out on disk. The defaults are set through a JSON configuration file that contains layer-specific specific information. This patch adds toasterconf.json files for the oe core layer, that make Toaster work with a standalone OpenEmbedded-Core checkout. The toasterconf.json files describe basic configuration for Toaster projects, including default layers, default configuration variable values, toaster-compatible branches, and the layerindex URL where the base layer and compatible layers. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-11-20default-providers.inc: define VIRTUAL-RUNTIME_getoptRichard Tollerton1
getopt can be provided by either util-linux or busybox. Allow the distro to control which implementation is used, and default it to util-linux. Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Acked-by: Ken Sharp <ken.sharp@ni.com> Acked-by: Ben Shelton <ben.shelton@ni.com Acked-by: Brad Mouring <brad.mouring@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-11-12documentation.conf: add missing tasks / variablesPaul Eggleton1
Document some recently added tasks and variables. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-30multilib.conf: set MULTILIB_GLOBAL_VARIANTS conditionallyPeter Seebach1
It is not entirely obvious that all reasonable configurations will have multilib.conf strictly before the file which might want to set MULTILIB_GLOBAL_VARIANTS. The x86-ish values here look like reasonable default guesses, but shouldn't override an explicit setting. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-24local.conf.sample.extended: update for RPM_PREFER_ELF_ARCHRobert Yang1
Updated as the rpm upstream suggested: - RPM_PREFER_COLOR -> RPM_PREFER_ELF_ARCH - 3 -> 4 Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-24native.bbclass: use BUILD_* variablesRoss Burton1
Instead of replicating the logic for the host compiler naming from bitbake.conf, use the BUILD_* variables directly. Also change BUILD_CPP to use gcc -E (which native.bbclass previously used), as some recipes (e.g. grub-efi) use ${CPP} with multiple input files, which gcc -E can handle but cpp can't. Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24spdx.bbclass: improved stability, fixed SPDX compliance issues. Changes are ↵Tobias Olausson1
reflected in licenses.conf. The previous version could crash on dead links in the rootfs, or if the manifest directory did not exist. The generated files were also not compliant with the SPDX specification, for example file entries did not always start with the FileName tag, time stamps were incorrectly formatted etc. Stability issues are addressed by added checks, originally written by Johan Thelin <johan.thelin@pelagicore.com>, who never upstreamed them. I've also added an option for getting full SPDX output from FOSSology, i.e. not only for all files, but for the package as well, including license references. License refs are required in order to process the output by SPDXTools. For that reason, this option defaults to true. Signed-off-by: Tobias Olausson <tobias.olausson@pelagicore.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24default-versions.inc: match version of db and db-native while "AGPL-3.0" in ↵Hongxu Jia1
${INCOMPATIBLE_LICENSE} The db 6.0.30's LICENSE is 'AGPL-3.0', and db 5.3.28 LICENSE is 'Sleepycat' While building rpm image with "AGPL-3.0" in ${INCOMPATIBLE_LICENSE}, db 6.0.30 and db-native 5.3.28 were built, the different versions caused the rpm doesn't work on target. ... root@qemux86-64:~# rpm -qa |rpmdb: BDB2531 Unacceptable log file /var/lib/rpm/./log/log.0000000001: unsupported log version 21 |rpmdb: BDB2527 Invalid log file: log.0000000001: Invalid argument |rpmdb: BDB0061 PANIC: Invalid argument |==> rpmdbe_event_notify(0x623f40, PANIC(0), 0x7fffee0fbc0c) app_private (nil) |rpmdb: BDB1546 unable to join the environment |error: db_init:tmp/work/core2-64-poky-linux/rpm/5.4.14-r0/rpm-5.4.14/ rpmdb/db3.c:1144: dbenv->open(-30973): BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery ... [YOCTO #6858] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-09-30local.conf.sample.extended: Document RPM4 setupSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-29tcmode-default: Define PREFERRED_VERSION for binutils-nativeKhem Raj1
When using other toolchain layers, it does not pick the OE-Core version eventhough not specified, its because we did not pin it. Change-Id: Ic47fd607a2a6535dd157d8afdd004197d2a6f60b Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-29licenses.conf: remove link to deleted License_Audit wiki pageJonathan Liu1
Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-09-23sanity.conf: Update minimum bitbake version to 1.23.2 due to event changesRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-23layer.conf: Mark opkg-utils as ABISAFE for update-alternatives usageRichard Purdie1
Currently linux-firmware rebuilds for each machine due to its usage of update-alternatives which in turn means a dependency on opkg-utils. Marking opkg-utils as ABISAFE is the only option we have right now to avoid this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-23layer.conf: Add in useradd dependencies as ABISAFE dependenciesRichard Purdie1
Currently allarch recipes using useradd rebuild each time MACHINE changes which is not desireable. Adding the useradd dependencies to this list ensures they do not change under these circumstances. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-23documentation.conf: document IMAGE_BOOT_FILESMaciej Borzecki1
Document IMAGE_BOOT_FILES variable. Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-10bitbake.conf: use ??= for IMAGE_ROOTFS_SIZEChen Qi1
Previously, when building core-image-minimal, the rootfs size would default to 64M because we use '?=' in bitbake.conf and also '?=' in core-image-minimal.bb. The thing is, we'd like to have a default value for all images set in bitbake.conf but still allow each image recipe to set its own default value which could be overridden by users in local.conf. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-09-01bitbake.conf: Use 2.6.32 for oldest supported kernelKhem Raj1
glibc 2.20+ wont support any older than that Signed-off-by: Khem Raj <raj.khem@gmail.com>
2014-09-01conf: Account for eglibc->glibc moveKhem Raj3
Change references in documentation appropriately Signed-off-by: Khem Raj <raj.khem@gmail.com>
2014-09-01distro: TCLIBC now defines glibc instead of eglibcKhem Raj7
Adjust naming conventions to reflect eglibc->glibc move Signed-off-by: Khem Raj <raj.khem@gmail.com>