summaryrefslogtreecommitdiffstats
path: root/meta/conf
AgeCommit message (Collapse)Author
2019-11-21distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, ↵Denys Dmytriyenko
rename Besides checking DISTRO_FEATURES for required or conflicting features, being able to check MACHINE_FEATURES and/or COMBINED_FEATURES may also be useful at times. Temporarily support the old class name with a warning about future deprecation. Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-11-10pseudo: Drop static linking to sqlite3Richard Purdie
Back in 2010[1] we made pseudo statically link against sqlite3. Since then the world has changed, pseudo now has separate processes for the database in the server and the client and they have separate linking commands. Also, whilst there were concerns about needing specific versions of sqlite3, in the OE environment, this is always the case. [1] http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ad0ac0ecd38fc77daf42485489fccc10a5e1e3e7 The static sqlite3-native is causing us problems, in particular: tmp/work/x86_64-linux/pseudo-native/1.9.0+gitAUTOINC+060058bb29-r0/recipe-sysroot-native/usr/lib/libsqlite3.a(sqlite3.o):(.data.rel+0xb0): undefined reference to `fcntl64' which occurs if sqlite3-native was built on a machine with glibc 2.28 or later and pseudo-native is being built on glibc before that. With dyanmical linking, libc is backwards compatible and works but with static linking it does not. There appears to be no easy way to avoid this other than adding a copy of sqlite3 into the pseudo recipe. Given the static linking doesn't seem to be required any longer due to the separate processes, drop that to fix those issues. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-11-10tune-cortexa32: Fix libgcc-initial build issue for cortex-a32Jagadeesh Krishnanjanappa
When we try to build images for machine which is tuned for cortex-a32, then libgcc-initial recipe fails to build with below error message. -- snip -- configure:3529: aarch64-poky-linux-gcc -mcpu=cortex-a32+crc -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=.../tmp/work/aarch64-poky-linux/libgcc-initial/9.2.0-r0/recipe-sysroot -o conftest -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=.../tmp/work/aarch64-poky-linux/libgcc-initial/9.2.0-r0=/usr/src/debug/libgcc-initial/9.2.0-r0 -fdebug-prefix-map=.../tmp/work/aarch64-poky-linux/libgcc-initial/9.2.0-r0=/usr/src/debug/libgcc-initial/9.2.0-r0 -fdebug-prefix-map=.../tmp/work/aarch64-poky-linux/libgcc-initial/9.2.0-r0/recipe-sysroot= -fdebug-prefix-map=.../tmp/work/aarch64-poky-linux/libgcc-initial/9.2.0-r0/recipe-sysroot-native= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong -Wl,-z,relro,-z,now conftest.c >&5 aarch64-poky-linux-gcc: fatal error: unknown value 'cortex-a32+crc' for '-mcpu' -- snip -- - Replacing TUNE_FEATURES from aarch64 to armv8a will solve the above build issue. - Changed BASE_LIB to 'lib', as cortex-a32 is a 32bit ARMv8a architecture. The sample machine config file (qemuarma32.conf) used to reproduce the error looks like: -- snip -- require conf/machine/include/tune-cortexa32.inc require conf/machine/include/qemu.inc KERNEL_IMAGETYPE = "Image" SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0" KMACHINE_qemuarma32 = "qemuarm64" -- snip -- Signed-off-by: Jagadeesh Krishnanjanappa <workjagadeesh@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-15qemuriscv64: Build smode U-BootAlistair Francis
Signed-off-by: Alistair Francis <alistair.francis@wdc.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-15llvm: Update to 9.0.0Khem Raj
libOptRemarks has been renamed as libRemarks RISC-V backend is now supported Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-15libmodulemd: remove the recipeAlexander Kanavin
Version 2 of the recipe is not actually required by anything; the lidmodulemd dependency in createrepo-c is optional, and the libmodulemd feature is not used in YP. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-15libmodulemd-v1: introduce the recipeAlexander Kanavin
Upstream has split version 1 of the libmodulemd recipe into its own branch and removed version 1 from the master branch and 2.x releases; as libdnf requires v1 of libmodulemd, this commit introduces a v1-specific revipe. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-08layer.conf: Update for zeus seriesRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-07uninative: Update to 2.7 releaseMichael Halstead
The 2.7 release updates glibc to version 2.30. Recently added to openSUSE Tumbleweed and needed for Fedora Core 31. Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-02sanity.conf: Bump minimum bitbake versionRichard Purdie
We need SignatureGeneratorUniHashMixIn from newer bitbake so bump the minimum version. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-10-02core-image-sato-sdk-ptest: Remove valgrind ptests for riscvKhem Raj
valgrind is not yet ported to riscv Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-10-02local.conf.sample: Add Hash EquivalenceJoshua Watt
Updates the local.conf sample file to reference the variables required to enable a local hash equivalence server. Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-27qemuriscv: Do not blacklist clang anymoreKhem Raj
clang 9.x ( which is now default in meta-clang ) supports riscv Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-19layer.conf: Remove weston-conf from SIGGEN_EXCLUDE_SAFE_RECIPE_DEPSKhem Raj
This recipe is gone Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-19weston-init: Add possibility to run weston as non-root userKhem Raj
These changes are from meta-96boards primarily Launch the session via a udev rule based on what kind of display device is available delete weston-conf and move the fuctionality into weston-init other layers are doing same weston-init installs machine specific weston.ini therefore mark is machine specific now Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-19image-uefi.conf: add config file holding configuration for UEFI imagesDmitry Eremin-Solenikov
Create new config file defining common variables for all UEFI-related packages (bootloaders, test applications, etc). Signed-off-by: Dmitry Eremin-Solenikov <dmitry_eremin-solenikov@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-18Remove SSTATE_HASHEQUIV_SERVERJoshua Watt
Removes all references to the SSTATE_HASHEQUIV_SERVER variable. This variable is redundant now that BB_HASHSERVE is present. Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-16tune-cortexa57-cortexa53: add tunes for ARM Cortex-A53-Cortex-A57Limeng
commit 3613b2780a6b5d5d70ea6802be5060a8214cbdb5 from git://github.com/renesas-rcar/meta-renesas The renesas rcar SoC H3/M3 is big.LITTLE architecture(cortex-a57.cortex-a53). In order to optimize the performance of the code running on SoC H3/M3, add a tune file for ARM Cortex-A53-Cortex-A57. Create this tune file by refering GCC doc, 3.18.5 ARM Options. Signed-off-by: Meng Li <Meng.Li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-09-16conf/multilib.conf: Add ovmf to NON_MULTILIB_RECIPESRobert Yang
Fixed: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake ovmf lib32-ovmf [snip] ERROR: ovmf-edk2-stable201905-r0 do_deploy_setscene: The recipe ovmf is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /buildarea1/lyang1/rebase-work/test_cc/tmp-glibc/deploy/images/qemux86-64/OvmfPkKek1.key (matched in manifest-qemux86_64-lib32-ovmf.deploy) [snip] Add it NON_MULTILIB_RECIPES to fix the problem since it is a firmware, build multilib for it doens't make much sense. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-09-07feature-arm-thumb.inc: fix ARM_THUMB_SUFFIXAndre McCurdy
Since TUNE_FEATURES now either contains a CPU or an architecture (but not both) we can't rely on finding the architecture in TUNE_FEATURES. Use architecture specific over-rides instead. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-06security_flags.inc: Add overrides for glibc-testsuite to match glibcNathan Rossi
Ensure glibc-testsuite has the same flags as glibc. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-06glibc-testsuite: Create a recipe to implement glibc test suiteNathan Rossi
A recipe needs to be created for the test suite due to the dependency chain between libgcc -> glibc -> libgcc-initial, and the requirements of the test suite to have libgcc for compilation and execution. The glibc test suite does not use dejagnu like the gcc test suites do. Instead a test wrapper script is used along with the assumed dependency of having the same filesystem available on build host and target. For qemu linux-user the same filesystem is inherently available, for remote targets NFS is used. Separate test wrapper scripts are created for qemu linux-user or ssh targets, with the same TOOLCHAIN_TEST_* variables used for configuration. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-06binutils-cross-testsuite: Create recipe for test suite executionNathan Rossi
Create the do_check task in a new recipe 'binutils-cross-testsuite'. This recipe is built within a target recipe (not -cross) to ensure correct testing against target specific libraries/etc. The do_check task is used to execute the binutils test suite for the cross target binutils. By default this executes tests for binutils, gas and ld. This can however be changed by setting CHECK_TARGETS to the desired test suite target (e.g. 'gas'). The binutils test suites do not require any target execution, as such the check task can be run without QEMU or a target device. However since the binutils tests do rely on a C compiler there is dependence on both gcc and libc in order to run the tests. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-06dejagnu: Add dejagnu for binutils/gcc test suitesNathan Rossi
The binutils and gcc test suites use dejagnu for execution. Copy the dejagnu recipe from meta-oe, and update it to 1.6.2. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-06Remove leftovers from the eglinfo removalAdrian Bunk
Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-06Clean up remnants of glibc-initialNathan Rossi
Remove remnants of the glibc-initial recipe. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-01qemuriscv: Generate a wic rootFS with a larger filesystemAlistair Francis
This allows us to generate a rootFS with a large filesystem for use with QEMU. Signed-off-by: Alistair Francis <alistair.francis@wdc.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-01tune-riscv: Drop littleendian and introduce bigendian tuneKhem Raj
Default riscv is little-endian moreover most of other arches define bigendian as tune and treats absense as litteendian, this make risc-v fall in line Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-01powerpc-tunes: Introduce bigendian tuneKhem Raj
This helps in defining LE tunes and at the same time specifies endianness on compiler cmdline clearly, clang e.g. defaults to little-endian always, so unless specified with -mbig-endian won't compile the code right Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-09-01default-providers.inc: set mesa as the provider for native(sdk) virtual/libglAlexander Kanavin
native/nativesdk libepoxy and libsdl2 require this to be set, when they have the respective opengl features enabled. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-30qemu: switch to '-vga std' emulated hardware from vmware/cirrus for x86/mipsAlexander Kanavin
This is the qemu default since qemu 2.2, is generally supported better, and is recommended by upstream. It also has already been in use for arm/risc and ovmf. Additional information: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13466 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/ '-vga virtio' emulated hardware remains in use when virgl is enabled via a runqemu override. Also, adjust the error whitelist, as there is a number of new messages coming from the drivers that are not actual errors. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-30qemu: bump linux-yocto preferred version to 5.2Bruce Ashfield
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-30linux-libc-headers: update to v5.2 headersBruce Ashfield
We drop the patch 0001-arm64-sve-uapi-asm-ptrace.h-should-not-depend-on-uap.patch since it was a backport and is already part of the 5.2 headers Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-30mesa: disable gallium swrast driver on x86 x32Alexander Kanavin
It was found to crash the X server on startup under qemu. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-29qemu: set default RAM to 256M for all machinesAlexander Kanavin
There was a discussion about what amount of RAM is appropriate for a default; the outcome was that for now it is still 256M. Some qemu machine definitions have however set this to 512M so for the sake of treating all architectures fairly, they are reset back to 256M. Also runqemu is adjusted to use 256M if QB_MEM is not set at all. http://lists.openembedded.org/pipermail/openembedded-core/2019-August/285900.html Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-29Remove LSB supportAdrian Bunk
LSB as a standard isn't current and isn't well suited to embedded anyway. Its putting artifical constraints on the system and with modern layer technology, would now be better off as its own layer. As such its time to split it out. The only part with some (marginal) usage is lsb_release, which is split from the lsb package into an own lsb-release package. Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-27tune-ep9312.inc: fix TUNEVALID descriptionAndre McCurdy
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-27tune-arm1176jz-s.inc: add support for arm1176jz-s CPU specific tuningAndre McCurdy
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-27tune-arm1136jf-s.inc: add hardfloat supportAndre McCurdy
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-27bitbake.conf: drop FETCHCMD, GITDIR, etc fetcher over-ridesAndre McCurdy
This completes cleanup originally proposed in 2012: http://lists.openembedded.org/pipermail/openembedded-core/2012-July/064224.html Current versions of bitbake have "sane" default fetcher commands so it's no longer necessary for bitbake.conf to over-ride them. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-27world-broken.inc: RemoveAdrian Bunk
Move still required entries as COMPATIBLE_HOST_libc-musl = 'null' to individual recipes. This also gives users a proper error message when trying to build a known non-building package. Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-22qemumips/qemumips64: move QB_SYSTEM_NAME to corresponding confChangqing Li
Configuration: MACHINE = qemumips64 bitbake lib32-core-image-minimal runqemu slirp nographic qemumips64 ext4 Error: ERROR - Failed to run qemu: qemu-system-mips: unable to find CPU model 'MIPS64R2-generic' Fixed by moving QB_SYSTEM_NAME to Respective configuration file Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-08-21conf/conf-notes.txt: add a mention of common toolsAlexander Kanavin
They remain not as widely known as they should be; perhaps mentioning them in the environment init banner could help. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-21bitbake.conf: fix XORG_MIRROR URLOleksandr Kravchuk
Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2019-08-21qemuriscv64: Specify the firmware as a bios instead of kernelAlistair Francis
Now that we have a -bios option for the RISC-V virt machine in QEMU we can pass OpenSBI in via -bios and the kernel in via -kernel. We no longer need to pass the kernel in via -device loader so let's remove that. Signed-off-by: Alistair Francis <alistair.francis@wdc.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-21qemu: Upgrade to version 4.1Alistair Francis
Signed-off-by: Alistair Francis <alistair.francis@wdc.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-16gcc-9: Upgrade to 9.2Khem Raj
BugFix only release see [1] for details [1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=9.2 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-12python-nose: remove the python 2.x version of the recipeAlexander Kanavin
With removal of python 2.x numpy, nothing needs it anymore. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-12python-scons: remove the python 2.x version of the recipeAlexander Kanavin
Nothing in oe-core or meta-oe is using it (scons.bbclass is set to use 3.x version). Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-08-09python-numpy: remove the python 2.x version of the recipeAlexander Kanavin
The 1.17.0 release of NumPy no longer supports Python 2.x. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-22 18:21:17 +0000