summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
* yocto-uninative: Upgrade to verson 2.3 which includes glibc 2.28Richard Purdie2018-11-071-4/+4
| | | | | | | | | | | | | | | | This allows us to handle distros which contain glibc 2.28 such as Ubuntu 18.10. (From OE-Core rev: 5c7d9abcd611d23d4340f9a0aee2564f72158a0b) (From OE-Core rev: b3d50458fdf8de719030a9d316fc766dc52912af) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> [Fixed up for sumo context] Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Update git.gnome.org addresses after upstream changesRichard Purdie2018-10-181-1/+1
| | | | | | | | | | | | | | | | | | | | git.gnome.org is no more. It has ceased to be. It's an ex-git. Please see here: https://about.gitlab.com/2018/05/31/welcome-gnome-to-gitlab/ Note that gitlab does not support git://, only https:// (and ssh). [Commit message from Alexander Kanavin] (From OE-Core rev: 8382cdc0888ca645a44aacaac1155afb8dcde979) (From OE-Core rev: d40c87b003b290a1739039156b27f194f68f12c2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> [Fixup for sumo context] Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Upgrade to version 2.2Richard Purdie2018-08-151-3/+4
| | | | | | | | | | | | | | | | | | | This version adds nativesdk-libnss-nis to resolve glibc symbol issues We need this to avoid symbol mismatch issues for binaries that use this on newer systems which then won't run on older ones where it isn't present. (From OE-Core rev: 98c7ab9cf32765d604c35dc69bc7bd90e94fc8f3) (From OE-Core rev: 026408c9d90e6241ce1b3d4cadefc48b7aba1734) (From OE-Core rev: 8b861d3c362615011a7004d902193587340a9f8c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Update to version 2.1Richard Purdie2018-08-151-3/+3
| | | | | | | | | | | | This fixes issues with fontforge-native. (From OE-Core rev: cec85a6fcadc24fd266fa34631cb095e0a773c1a) (From OE-Core rev: 462e20dddeb4da278eebe8a2f870f75709dfbe77) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Set and export TZ envvar to UTCRichard Purdie2018-05-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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) (From OE-Core rev: e31f31f81efe4b60938b724bece2a03c7c74a68d) (From OE-Core rev: 2c72aa56e6065100582cb17f281c4c11521712e6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> [Drop simple.bbclass changes] Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Update to version 1.9 (fedora28 compatible)Richard Purdie2018-05-031-3/+3
| | | | | | | | | | | | | | This includes the libxcrypt change which allows uninative to work on fedora28. (From OE-Core rev: 4b27ab6487a54b42a52aa16e98ea4d19fa62b5ae) (From OE-Core rev: 0685eb697f1dfa3b858b6e594cbd8e6070b4fbb8) (From OE-Core rev: 2b462bdc2b9bad40425769ece380e46b52cca095) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add comm to HOSTTOOLSNiko Mauno2018-03-301-1/+1
| | | | | | | | | | | | | | | | | This mitigates following issues during u-boot do_compile() step -- otherwise, if comm is not available, they are quietly ignored: .../scripts/check-config.sh: line 33: comm: command not found .../scripts/check-config.sh: line 39: comm: command not found Since 'comm' is provided by coreutils package, adding it to HOSTTOOLS was considered a lower impact fix compared to adding coreutils-native buildtime dependency to u-boot recipe. (From OE-Core rev: c1b711e265e2ff6ba74b0f6f568f231ddf476f8b) Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-distrovars: don't rename locales for nativesdkRoss Burton2018-03-261-0/+1
| | | | | | | | | | | (From OE-Core rev: 909da982c74b2ed931a65dda248557cb18f773e0) (From OE-Core rev: 652e45b756bb73815f2e1ffd9686106a1c3d2549) (From OE-Core rev: fa13b6f6656ff97aa156854e6d36aa56826b89ad) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: add myself as maintainer for the new busybox-inittabDenys Dmytriyenko2018-03-191-0/+1
| | | | | | | | | | | (From OE-Core rev: ba2eb6237497494e3ec0296485ded61b024c5ba7) (From OE-Core rev: 3718d467be290203e3e9d6a174838a4aa89833c2) Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: add busybox-inittab to SIGGEN_EXCLUDERECIPES_ABISAFEDenys Dmytriyenko2018-03-191-0/+1
| | | | | | | | | | | | | Similar to sysvinit-inittab (From OE-Core rev: a673d5bbf7e4db6de9a5151df041e6c5db7e413e) (From OE-Core rev: e4ec23c7b4f2a9b9783d59075a570651806b6284) Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative: Add compatiblity version checkRichard Purdie2018-03-151-0/+2
| | | | | | | | | | | | | | | | 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. (From OE-Core rev: 7dccdf82d49fb11cb2a7cb205ae08311e5d43291) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Upgrade to 1.8 version with glibc 2.27Richard Purdie2018-03-151-3/+3
| | | | | | | | | 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. (From OE-Core rev: ead79135851c7b01968375bb6f512cb79d2618ca) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unfs3: Fix build with muslKhem Raj2018-03-151-4/+0
| | | | | | | | | | | Should also fix build on new build hosts where with glibc 2.27 rpc support is dropped in favor of libtirpc (From OE-Core rev: 6cc4046bfad12cc95b67a7dc72309c6c8577c655) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: don't use update-alternativesMarkus Lehtonen2018-01-061-0/+1
| | | | | | | | | | | | | | | Stop using update-alternatives for managing /etc/init.d/functions. Also, make the initscripts-functions subpackage to (runtime) conflict with lsbinitscripts. [YOCTO #10944] (From OE-Core rev: 2daffb998585a2f781cbbfb1a959379e01c40f0a) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> (cherry picked from commit cdcebd81c872cb7386c658998e27cf24e1d0447c) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: add install moduleCalifornia Sullivan2018-01-061-0/+4
| | | | | | | | | | | | | | | | The non-EFI counterpart for installation was previously missing for initramfs-framework. This simply puts the normal install script in the correct location for initramfs-framework to make use of it. Partial fix for [YOCTO #12346]. (From OE-Core rev: 236cb8fe6bb9f5826a97f393b22aaae79dec1b84) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> (cherry picked from commit f9d7cf30b12cbc5f642a11c0511dc1dc3ccf1aa5) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu.inc: let linux-yocto-rt also provide nfs server kernel moduleMing Liu2017-12-041-0/+1
| | | | | | | | | | | | In case some users want to use linux-yocto-rt as the preferred kernel. (From OE-Core rev: e0b8eafaf378571a99b07c559d07f9af36db791e) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> (cherry picked from commit bb0e574d3c74b6cd2d7e41933e0e28c91f0a411b) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tclibc-musl.inc: disable ldconfig distro featureAndre McCurdy2017-12-041-0/+2
| | | | | | | | | | | | | Musl has no support for ldconfig, so ensure that the corresponding distro feature is disabled when building with musl. (From OE-Core rev: 73d5475af8c8aa655a80bf38d9fc788078a70883) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> (cherry picked from commit baacd7ea99265f5493d2452b173a12def92f6202) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: add Otavio Salvador for go-depAlexander Kanavin2017-12-041-0/+1
| | | | | | | | (From OE-Core rev: 6e45eac3686cb749a6690149dbfca9925786ab9e) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: add Khem Raj for libmnlAlexander Kanavin2017-12-041-0/+1
| | | | | | | | (From OE-Core rev: ed959f455604975abccb3c2c3ce98f26234dd4f7) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* feature-arm-vfp.inc: drop unnecessary extra space from TUNE_CCARGSAndre McCurdy2017-12-041-2/+2
| | | | | | | | | | | | The trailing space added to TUNE_CCARGS when appending -mfpu=XXX is unnecessary and leads to a double space in the final value. (From OE-Core rev: 0d5bbaf5fe66bd93e8d8cbf78834f562d90d9dca) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: update maintainershipYi Zhao2017-12-041-21/+21
| | | | | | | | | | | Reassign Dengke's recipes to Yi Zhao. (From OE-Core rev: 0c8ef5e4d579ca0d097bb6ab8312ba5b7eb9e213) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Adds ipv6 to DISTRO_FEATURES_NATIVEAlejandro Hernandez2017-10-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Before we introduced DISTRO_FEATURES_NATIVE on commit: db1f1adace58763c35774e3fdfeaac5c3ca646fd ipv6 was enabled by default on DISTRO_FEATURES via DISTRO_FEATURES_LIBC hence for example python-native was built with ipv6 support. After this, ipv6 was automatically disabled on DISTRO_FEATURES. On some packages (python) this may cause errors when they try to download something on their do_compile stage. This patch adds ipv6 to DISTRO_FEATURES_NATIVE leaving it as it was before, to avoid errors like the one mentioned above [YOCTO #11978] (From OE-Core rev: a09184bf47323b63d9548d17cc1e4e694cb605a9) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add ssh to HOSTTOOLS_NONFATALChen Qi2017-10-161-1/+1
| | | | | | | | | | | | | | | We changed to make tools required by testimage to be included conditionally. This resulted in users who use ssh for git fetching having failures. Add ssh to HOSTTOOLS_NONFATAL to make things work for the above situation. [YOCTO #12227] (From OE-Core rev: 50e7619aebae5351e9a41fe1b909a31b9e383f0a) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add tools required by testimage to HOSTTOOLS conditionallyChen Qi2017-10-091-1/+1
| | | | | | | | | | | | | Add tools required by testimage to HOSTTOOLS only when testimage is inherited. These tools, as described in the comment, are only required by the testimage task. So this change should not have negtive effect. This would also solve build error on hosts which miss some tool such as scp. (From OE-Core rev: 8ca61a5464743ff85b6d26886112750d6ddd13e0) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add 'id' to HOSTTOOLSOtavio Salvador2017-10-071-1/+1
| | | | | | | | | | | The 'id' utility is used in 'rootfs_check_host_user_contaminated' rootfs-postcommand so it must be available. (From OE-Core rev: 6c054925d5f80790aea4cce6f8f83edc7da623b9) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-x86: Add x86-x32 to MACHINEOVERRIDESSaul Wold2017-09-261-0/+1
| | | | | | | | | | | | This is needed as an x32 more generic x32 override later in the OVERRIDES, currently linux-gnux32 is the first override, but we need a stronger (later in the list) x32 override to deal with some needed x32 dependency overrides. (From OE-Core rev: 364b3698b78e9fea59d24e3a3a5f4476be95f6d1) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: drop True option to getVar callsMing Liu2017-09-261-1/+1
| | | | | | | | | Search made with the following regex: getVar ?\((.*), True\). (From OE-Core rev: dbc0eaf478feb3f752ae22fd184984494fc85d0a) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* 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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-11 13:40:57 +0000