aboutsummaryrefslogtreecommitdiffstats
path: root/meta/conf
AgeCommit message (Collapse)Author
2018-05-11base-files: make root home mode customisabledankm/base-permissionsDan McGregor
Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
2018-05-09maintainers: reassign some Intel maintainersRoss Burton
Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-05-09libnss-nis: Add recipeKhem Raj
This will substitute the glibc nis module which has been removed Skip for non-glibc systems Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-05-09rpcsvc-proto: Add recipeKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-05-09glibc: Drop obsolete rpc and libnslKhem Raj
use libnsl2 and rpcsvc-proto packages Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-05-08tclibc-baremetal: Adds virtual/crypt to ASSUME_PROVIDEDAlejandro Enedino Hernandez Samaniego
When trying to build meta-toolchain using TCLIBC = "baremetal" bitbake throws an error due to a mising dependency: ERROR: Nothing PROVIDES 'virtual/crypt' glibc PROVIDES virtual/crypt but was skipped: PREFERRED_PROVIDER_virtual/libc set to musl, not glibc musl PROVIDES virtual/crypt but was skipped: PREFERRED_PROVIDER_virtual/i586-poky-elf-libc-for-gcc set to baremetal, not musl libxcrypt PROVIDES virtual/crypt but was skipped: Recipe only applies in nativesdk case for now This is caused by the changes on commit: 29f65bda6d2c9fea4adb125c4857ee64f9312b9f nativesdk-glibc: Split glibc and libcrypt to use libxcrypt instead This is where the concept of virtual/crypt was introduced. This patch adds virtual/crypt to ASSUME_PROVIDED on tclibc-baremetal, providing the missing wiring to build meta-toolchain on baremetal correctly. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-05-04libuser: removeRoss Burton
This isn't used by anything in oe-core (or in common use in general, only one package in Debian depends on it), so remove it from oe-core. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-05-04tune-corei7.inc: update TUNE_CCARGS -march CPU type corei7 -> nehalemAndre McCurdy
The gcc "corei7" CPU type was last documented in gcc 4.8.x and has been undocumented from gcc 4.9.x onwards: https://gcc.gnu.org/onlinedocs/gcc-4.8.5/gcc/i386-and-x86-64-Options.html https://gcc.gnu.org/onlinedocs/gcc-4.9.4/gcc/i386-and-x86-64-Options.html Although it still seems to be accepted by gcc 7.x, it's likely to be deprecated and removed at some point. To preempt that, switch the corei7 TUNE_CCARGS -march CPU type to "nehalem", which is the closest replacement (and matches the CPU type already being passed to qemu). Since the tune-corei7.inc include file is intended to cover a range of CPUs from Nehalem onwards, switch the TUNE_CCARGS -mtune option from "corei7" to "generic", which instructs gcc to produce code optimized for the most common IA32/AMD64/EM64T processors. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-05-04beecrypt: removeRoss Burton
This was only in oe-core for RPM5, but RPM4 doesn't use it. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-05-04pixz: removeRoss Burton
Nothing in oe-core is using this now as xz can do multithreaded compression, so remove it. Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-05-04maintainers: update email addressArmin Kuster
Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-05-04xorgproto: Replace individual depreciated xorg proto recipes with xorgprotoArmin Kuster
Xorg upstream have replaced the individual xorg proto repositories with one master repository. This converts to the new system. The only one not included is calibrateproto which was depreciated entirely and replaced be xinput. We can drop this entirely. Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-23bitbake.conf: re-order DEBUG_PREFIX_MAPJuro Bystricky
When specifying several -fdebug-prefix-map command line options to gcc, they are evaluated right to left (last one first). Normally, the order is irrelevant. However, when we try to map both: recipe-sysroot-native recipe-sysroot the order matters. With the original order most of our debug packages contain incorrect debug symbols. Take for example /usr/bin/.debug/setfacl from acl-dbg: $ strings setfacl | grep native ... -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include Reordering the fdebug-prefix-map arguments will give us the correct paths: /usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include Note there may be additional an incorrect paths, such as: /usr/src/debug/glibc/2.27-r0/recipe-sysroot-native/usr/lib/x86_64-poky-linux.gcc-cross-initial-x86_64/gcc/x86_64-poky-linux/7.3.0/include But that one needs to be fixed in the recipe for glibc. Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-04-19bitbake.conf: add scp to HOSTTOOLS_NONFATALJef Driesen
The scp tool is used by the ssh fetcher. Signed-off-by: Jef Driesen <jef.driesen@niko.eu> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-04-18bitbake.conf: Set and export TZ envvar to UTCRichard Purdie
We just ran into an issue where tar failed to build on one server setup but built everywhere else just fine. It was running makeinfo to regenerate some docs files and makeinfo was too old for the host it was running on. There was no dependency on makeinfo-native as it was not meant to be regenerating the docs. It was being regenerated as a date from a timestamp used in the docs was different in Asian timezones than in the other timezones our builds were being tested in. I added an entry to https://wiki.yoctoproject.org/wiki/TipsAndTricks/ about how this was debugged. As such, lets default to setting and exporting TZ to 'UTC' as was already pioneered by the reproducibile builds work. This makes the builds deterministic. [YOCTO #12665] (From OE-Core rev: 2a90ae7a3286724ff9e3615c4dbf56038f703810) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-18yocto-uninative: Update to version 1.9 (fedora28 compatible)Richard Purdie
This includes the libxcrypt change which allows uninative to work on fedora28. (From OE-Core rev: 4b27ab6487a54b42a52aa16e98ea4d19fa62b5ae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-13distro: default: Change Go default version to 1.9Otavio Salvador
For the time being, there is a serious bug[1] in Go 1.10 when it comes to use the shared runtime support which cases problems in multiple projects. 1. https://github.com/golang/go/issues/24640 It is still unclear if the problem arises from a bug inside the compiler itself or it makes a real problem more visible. Either way, using 1.10 as default seems to be a risk so we are changing back to 1.9 for now. Refs: [YOCTO: #12631] Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-04-07nativesdk-glibc: Split glibc and libcrypt to use libxcrypt insteadRichard Purdie
Fedora28[1] has decided to go ahead and use libxcrypt to replace libcrypt from glibc despite the change not having merged into glibc upstream yet. This breaks the use of uninative in OE on fedora28 since binaries there are now using new symbols only found in libxcrypt. libxcrypt is meant to be backwards compatible with libcrypt but not the reverse. Since this will impact OE in the next release cycle, this changes nativesdk only to use this new model and adds libxcrypt to work in that case. This allows us to build a uninative which is compatible with fedora28 and previous other OSes. In order to work, recipes will now need to depend on virtual/crypt where they use libcrypt since its now a separate library and we can't depend on it from glibc to preseve backwards compatibility since glibc needs to build first. For now, only the problematic nativesdk recipes have been fixed up. For target use, the default provider remains glibc for now. Assuming this change is merged into upstream glibc, we will need to roll this change out for the target but we will do this in the next release cycle when we can better deal with the resulting bugs. [1] https://fedoraproject.org/wiki/Changes/Replace_glibc_libcrypt_with_libxcrypt Original patch from Charles-Antoine Couret <charles-antoine.couret@essensium.com>, tweaked by RP to add virtual provides, SkipRecipe for libxcrypt and other minor tweaks. Signed-off-by: Charles-Antoine Couret <charles-antoine.couret@essensium.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-06layer.conf: Update LAYERSERIES rocko -> sumoRichard Purdie
Also set LAYERSERIES_COMPAT for core (we're compatible with ourself). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-05documentation.conf: remove obsolete variableMaxin B. John
PRINC is no longer used and removed from documentation: commit 7baadd86ee1386756e3bc3ef7fd02d5d1367068f Author: Scott Rifenbark <scott.m.rifenbark@intel.com> Date: Mon May 18 09:25:51 2015 -0600 ref-manual: Removed PRINC entry from the glossary Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-05nativesdk-postinst-intercept: remove the recipeAlexander Kanavin
Its use required a script from an external repo which hasn't been updated in 4 years, the recipe itself is out of date (doesn't install all intercepts), and there is no oe-selftest or documentation for this. If anyone still wants this, please do it in a separate layer. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-03tune-core2.inc: add cpu type for qemuRuslan Ruslichenko
Define cpu type for Qemu in QEMU_EXTRAOPTIONS. Otherways Qemu will emulate some virtual qemu32/64 processor, which has very basic set of features, and programs built for later CPU may crash, due to lack of new features (e.g. SSSE3). Signed-off-by: Ruslan Ruslichenko <rruslich@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-30default-distrovars: set default KERNEL_IMAGETYPE(S)California Sullivan
With the change from assuming kernels will be named "vmlinuz" everywhere, to instead using KERNEL_IMAGETYPE, we require that KERNEL_IMAGETYPE is set to something. Instead of setting the default in multiple individual files, set it in default-distrovars.inc. x86(-64) arches get bzImage as the default. Others get zImage as per meta/conf/documentation.conf. Also set KERNEL_IMAGETYPES, as we will eventually be switching away from KERNEL_IMAGETYPE. Thanks to Andre McCurdy <armccurdy@gmail.com> for the arch defaults part. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-25maintainers.inc: drop lsb4 perl modules no longer in coreTim Orling
The following perl module packages were removed from oe-core with commit: 30fb4c8f329fe3aa3c528ffeba60ee7d702e873e - libclass-isa-perl - libenv-perl - libdumpvalue-perl - libfile-checktree-perl - libi18n-collate-perl - libpod-plainer-perl Remove these from the maintainers list Fixes: [Yocto #12582] Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-25maintainers: remove obsolete entriesMaxin B. John
Delete entries of removed packages. Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-15maintainers: add maintainer for make-mod-scriptsBruce Ashfield
I introduced the recipe, so I get to fix any bugs! Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-15maintainers: remove obsolete entryRoss Burton
Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-15risc-v: Pin oldest kernel to 4.15 for the new kidKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-15tcmode-default.inc: Define QEMUVERSION and softly pin itKhem Raj
This provides ability to surgically override qemu for certain machines which are provided by external layers. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-14uninative: Add compatiblity version checkRichard Purdie
If glibc is newer on the host than in uninative, the failure mode is pretty nasty for clusters where the sstate is shared, including the Yocto Project autobuilder. This check aborts the use of uninative in such scenarios where a newer glibc version appears and avoids corruption of sstate caches. We use ldd to check the glibc version since that is included in libc-bin (or equivalent) which locales use so it should always be present. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-12unfs3: Fix build with muslKhem Raj
Should also fix build on new build hosts where with glibc 2.27 rpc support is dropped in favor of libtirpc Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-11yocto-uninative: Upgrade to 1.8 version with glibc 2.27Richard Purdie
Now distros are starting to ship glibc 2.27 we need a uninatve version which contains glibc 2.27 which is in the 1.8 version. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-06tcmode-default.inc: add settings for goMatt Madison
to allow GOVERSION to be set for using an older go toolchain. Signed-off-by: Matt Madison <matt@madison.systems> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-06maintainers.inc: add myself as -bootconf recipe maintainerCalifornia Sullivan
Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-06layer.conf: add -bootconf recipes to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPSCalifornia Sullivan
The bootloaders depend on these to be functional in the non-deploy case, but changes in them don't require rebuilding of the packages. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-06maintainers.inc: self-assign recipes from recipes-extended/perlTim Orling
In prior round, the perl module recipes in recipes-extended/perl were inadvertantly overlooked. Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-06maintainers: self-assign perl module maintainershipTim Orling
Also, take over the other recipes that were just enabled for ptest: - liberror-perl - liburi-perl - libxml-parser-perl - libxml-perl - libxml-simple-perl Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-04maintainers.inc: add myself as maintainer for the new busybox-inittabDenys Dmytriyenko
Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-04layer.conf: add busybox-inittab to SIGGEN_EXCLUDERECIPES_ABISAFEDenys Dmytriyenko
Similar to sysvinit-inittab Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-04tclibc-musl.inc: Add needed libc deps for musl for on-device SDKKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-04maintainers: Add myself for musl-utilsKhem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-03latencytop: remove recipeAlexander Kanavin
Last commit and release were in 2009; website is down; it's a dead project. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-03maintainers: Change icecc-create-env maintainerJoshua Watt
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-03-01glibc: Enable static PIE support when security_flags are enabledKhem Raj
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-03-01default-distrovars: don't rename locales for nativesdkRoss Burton
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-01glibc: Upgrade to 2.27 releaseRoss Burton
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-03-01sstatesig: Move hardcoded native toolsJoshua Watt
Now that SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS supports the wildcard syntax, these exclusions no longer need to be hardcoded Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-24binutils: Upgrade to 2.30 releaseKhem Raj
Additionally cherry-pick 5ffeba4a09 Revert "PowerPC PLT speculative execution barriers" b01452b1d4 [PR22764][LD][AARCH64]Allow R_AARCH64_ABS16 and R_AARCH64_ABS32 against absolution symbol or undefine symbol in shared object. a985e9b9de Import patch from mainline to remove PROVODE qualifiers around definitions of __CTOR_LIST__ and __DTOR_LIST__ in PE linker scripts. eec4607fc5 Add support for DWARF-4 line number tables. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24maintainers: update for change to icecc-create-env recipe nameRoss Burton
Signed-off-by: Ross Burton <ross.burton@intel.com>
2018-02-24image-live.bbclass: drop support for compressed ISO imagesAlexander Kanavin
While modern Linux kernels still support it, the userspace tools haven't been updated in over a decade. Also, squashfs provides both better performance, and better compression ratio: https://elinux.org/Squash_Fs_Comparisons Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-18 16:14:00 +0000