summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* crosstap: replace script with new python based implementationVictor Kamensky2018-04-071-136/+450
| | | | | | | | | | | | | | | | | | New crosstap python implementation is total replacement for crosstap shell script, that has superseding capabilities. New script support cross compiling of SystemTap scripts for user-land, by using supplied image rootfs. Whereas old script could only deal with scripts against kernel. New script has more complex logic and additional capabilities. As invocation interface new script support old "legacy" mode and provides alternative new regular options interface to access additional functionality. (From OE-Core rev: 1cbbcf26e0a9ca6e0b34a89512bf75dbae8bfaf0) Signed-off-by: Victor Kamensky <kamensky@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemtap: support --sysroot option in variety of situations in cross buildVictor Kamensky2018-04-0710-0/+560
| | | | | | | | | | | For details on issues fixed please look at commit message of individual patches. Upstream-Status: Backport [systemtap@sourceware.org] (From OE-Core rev: 5aa93de3a79c8691e74e982d3d4b0099b04f5555) Signed-off-by: Victor Kamensky <kamensky@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemtap: create translator packageconfigVictor Kamensky2018-04-071-4/+11
| | | | | | | | | | | | | | | | | | | | | For cases when systemap module compilation happens on host in cross-compilation mode, and it is desirable to minimize systemtap presense on target we need to have just smallest possible set of utilties that are required to run compiled modules. Introduce new "translator" PACKAGECONFIG, if it is not set it would mean that just minimal set of run-time utilities will be included in the package. For run-time only systemtap build variant use PACKAGECONFIG_pn-systemtap = "" or PACKAGECONFIG_pn-systemtap = "monitor" Suggested-by: Taras Kondratiuk <takondra@cisco.com> (From OE-Core rev: a22b8140c6924eb3b3cd7b5bea66a4d3ed413807) Signed-off-by: Victor Kamensky <kamensky@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image: add image-combined-dbg helper classVictor Kamensky2018-04-071-0/+9
| | | | | | | | | | | | | | | | | | | | | | | There is IMAGE_GEN_DEBUGFS="1" variable that enables build of additional rootfs-dbg and additional archive that contains complimentary symbols files for a given image. But the issue with this resulting directory and tarball that before use it has to be combined with original image content. It is required since all cross debugging tools like gdb, perf, and systemtap need file system that contains both target executables/libraries and their symbols. Those tools need to find executable/library first and through it debuglink note find corresponding symbols file. image-combined-dbg when added to USER_CLASSES just copies final resulting rootfs back into rootfs-dbg creating combined target and debug symbols rootfs that can be used for debugging directly. (From OE-Core rev: 7ccb077f51c9232de70e5c6f9897fd9986e3be9d) Signed-off-by: Victor Kamensky <kamensky@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "systemtap: Cross compilation fix"Victor Kamensky2018-04-072-24/+0
| | | | | | | | | This reverts commit 787bed708676fc04aee2850825e803273152f657. (From OE-Core rev: 08ab022471eff48e6f43ec8cd47e695d575ee2e3) Signed-off-by: Victor Kamensky <kamensky@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* curl: DEPENDS on libidn2 (not libidn)André Draszik2018-04-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since v7.51.0, libidn2 is the only available option, libidn support was dropped. The configure option was renamed as of v7.53.0 Therefore, curl unconditionally tries to build against libidn2, which in particular is a problem for curl-native, as that might or might not build against the build-machine's libidn2 now, which furthermore causes problems when trying to share sstate between multiple build machines. We therefore see the following in the config log: ... checking whether to build with libidn2... (assumed) yes ... checking for libidn2 options with pkg-config... no configure: IDN_LIBS: "-lidn2" configure: IDN_LDFLAGS: "" configure: IDN_CPPFLAGS: "" configure: IDN_DIR: "" checking if idn2_lookup_ul can be linked... yes checking idn2.h usability... yes checking idn2.h presence... yes checking for idn2.h... yes ... IDN support: enabled (libidn2) ... even though this recipe tries to disable that. While libidn2 isn't available in OE, this change at least: * prevents curl-native to silently build against libidn2 if that is installed on build machine, even if not requested * alerts people who use the PACKAGECONFIG option that it's not actually doing what they intend to do (From OE-Core rev: 705eaea991622bdbb2ee83eefa8df8e665e3efe4) Signed-off-by: André Draszik <andre.draszik@jci.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-sdk: update sanitizer listsDan McGregor2018-04-071-3/+0
| | | | | | | | | | aarch64 has been supported since GCC 5.1, sparc has been supported since 4.9, and S390 since 7.1. (From OE-Core rev: a2cbb5dc4c6191ca343dc4211abde693dc1a579a) Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-sanitizers: Update supported architecturesDan McGregor2018-04-071-3/+7
| | | | | | | | | | | | aarch64 has been supported since GCC 5.1, sparc has been supported since 4.9, and S390 since 7.1. Also mark as broken entirely with musl. (From OE-Core rev: 7d90d2a70f0184ad715e9917d3e7aa096cf98f79) Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update LAYERSERIES rocko -> sumoRichard Purdie2018-04-062-2/+2
| | | | | | (From meta-yocto rev: db28e5c97895d2a25098aaac7f0a65d4f2a01866) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cookerdata: Issue warning if layer doesn't set LAYERSERIES_COMPAT_xRichard Purdie2018-04-061-0/+2
| | | | | | | | | | | We'd like layers to set this variable so that we know which layers are compatible with which others, even if the branch is a generic un-updated "master" branch. Start printing a warning to highlight this issue. (Bitbake rev: cca81e33b58c390dcf5cc3a31555a43b79177166) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update LAYERSERIES rocko -> sumoRichard Purdie2018-04-063-4/+5
| | | | | | | | Also set LAYERSERIES_COMPAT for core (we're compatible with ourself). (From OE-Core rev: 4aa43cd844781a07a2dbf17f21ed35c6a0100d02) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: Update to use llvm 6.0Richard Purdie2018-04-051-1/+1
| | | | | | | | Adpat to the upgrade from 5.0 -> 6.0. (From OE-Core rev: dc52f9cf343df4c2d77bee0e47004466321e7edb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* llvm: Upgrade to 6.0 releaseKhem Raj2018-04-053-17/+18
| | | | | | | (From OE-Core rev: 67379117375bcc143f636ccd56e548332b19325f) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* librsvg: remove duplication in inheritMaxin B. John2018-04-051-1/+1
| | | | | | | | | | Since gnomebase class already inherits autotools and pkgconfig, there is no need to repeat it here. (From OE-Core rev: bae5ced6eba78f1903e15d7f9dd7afc3c06e8955) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcr: remove duplication in inheritMaxin B. John2018-04-051-1/+1
| | | | | | | | | | Since gnomebase class already inherits autotools, there is no need to repeat it here. (From OE-Core rev: 9a514311fa062fa3f8bccc4c47e907f88221024a) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcroco: remove duplication in inheritMaxin B. John2018-04-051-1/+1
| | | | | | | | | | Since gnomebase class already inherits autotools and pkgconfig, there is no need to repeat it here. (From OE-Core rev: 301d153781c7ddb6e38178c56f960e18d62788ab) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pygobject: remove duplication in inheritMaxin B. John2018-04-051-1/+1
| | | | | | | | | | Since gnomebase class already inherits autotools and pkgconfig, there is no need to repeat it here. (From OE-Core rev: 2eb7ba6cb68e171c880bcb1fc614f1ae6b300e4f) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: remove obsolete variableMaxin B. John2018-04-051-1/+0
| | | | | | | | | | | | | | | 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 (From OE-Core rev: b15089b014b95a8730f622ca4959b42ed15cb175) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* archiver: Fix archive for linked kernel sourceTom Hochstein2018-04-051-0/+5
| | | | | | | | | | | | When archiving a kernel, if S is ${WORKDIR}/git, then ${WORKDIR}/git is in fact a soft link into work-shared, and the archive contains just the soft link. Fix by archiving the real directory. (From OE-Core rev: 564204dd6b73697ef4b6c17243067892876cc323) Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* archiver: Fix build errors for kernels that don't use kernel-yocto.bbclassTom Hochstein2018-04-051-2/+6
| | | | | | | | | | | Special handling for kernel source in work-shared was incorrectly limited to kernel-yocto.bbclass instead of kernel.bbclass. (From OE-Core rev: b8c5680a67888d43540366a40bd0c501e926ac31) Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0/glib.inc: apply MLPREFIX renaming to all package classesAlexander Kanavin2018-04-051-5/+5
| | | | | | | | | | | | | Now that we have postinst intercept execution working for SDK generation, adding MLPREFIX again makes sense in all cases, as the intercepts do require that it is there. This reverts commit 4ffb728df4bdf21daef31d89cfa5771eaf0d90f8. (From OE-Core rev: 0792540170b6150a0c5fe8586bb8012affc3f90e) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gio-module-cache.bbclass: pass in ${libexecdir}Alexander Kanavin2018-04-051-0/+1
| | | | | | | | | | When it was something else than /usr/libexec (e.g. when installing native SDK packages), things broke down. (From OE-Core rev: d99e819a6cbde6d1116c434ddba4c5f8eca7e6d8) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk.py: run postinst interceptsAlexander Kanavin2018-04-052-1/+13
| | | | | | | | | | | | | | Previously this wasn't done, and so any packages installed from populate_sdk would not have the postinsts fully executed (particularly generation of various caches via running nativesdk or target binaries with qemu wasn't working). [YOCTO #12630] (From OE-Core rev: a484ff072eea3f47de2c3348048201249cefa46b) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager.py: do not hardcode the task name when referring to log filesAlexander Kanavin2018-04-051-4/+4
| | | | | | | | | This can be do_rootfs or do_populate_sdk, or anything else. (From OE-Core rev: e2e05a327e51339d45b53e0276c287ab314e3385) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager.py: move intercept running logic from rootfs class to ↵Alexander Kanavin2018-04-052-63/+59
| | | | | | | | | | | | | PackageManager class This allows running the intercepts when creating SDKs, which previously wasn't possible, as SDK code does not use the rootfs class, and calls into PackageManager methods directly. (From OE-Core rev: f830388c5e9125f385a42acd7365d1235967b57c) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager.py: move postinst_intercept dir initialization from RootFS ↵Alexander Kanavin2018-04-052-18/+20
| | | | | | | | | | | | to PackageManager class This will allow handling postinst_intercepts when populating SDKs (which use PackageManager class directly, and do not utilize RootFS class). (From OE-Core rev: 9454fd328040fd58c981d028a74fcf181bde8e89) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager.py: move target_rootfs property to common ancestor classAlexander Kanavin2018-04-051-9/+7
| | | | | | | | | | This will be useful when also moving postinst_intercept handling to package manager class from rootfs class. (From OE-Core rev: a4cd69bdd5b9dfa1125887f4d9038d41996e39c7) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-postinst-intercept: remove the recipeAlexander Kanavin2018-04-054-21/+0
| | | | | | | | | | | | 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. (From OE-Core rev: 1fbae102fde54c9e7a0d74a4cda9900cd17640d6) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* elfutils: Clean up commentsPeter Kjellerstedt2018-04-051-10/+3
| | | | | | | | | | | | | | The list of patches in SRC_URI was restructured in 49aae1d7, and left a comment about patches from Debian hanging without context. Move and reword it to make it remain useful. There was also a leftover comment that referred to two .h files and do_configure_prepend() that were removed in f960c026. (From OE-Core rev: 80a702db442674e16a450a120972eeee4cbcb29a) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager.py: Skip gpgcheck while using dnf on targetManjukumar Matha2018-04-051-1/+1
| | | | | | | | | | | | | By default, RPM_SIGN_PACKAGES is not defined. Add gpgcheck=0 to oe-remote-repo.repo file, otherwise dnf will complain during install operation on target Note, RPM_SIGN_PACKAGES is set only when you inherit sign_rpm explicitly (From OE-Core rev: 002a71eaa7606828c399972d8fd35e19e7b71929) Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: Upgrade 17.3.7 -> 17.3.8Otavio Salvador2018-04-053-31/+2
| | | | | | | | | | | | | | | This version has been published at April 03, 2018, and it is a bugfix only release. The release includes several important fixes that were made as part of 18.0.1 development cycle. Full list of bug fixes can be see online at: https://www.mesa3d.org/relnotes/17.3.8.html (From OE-Core rev: 782fb864349d4f5c07a38f0e117659bfb841d3c2) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: fix do_unpack[cleandirs] varflag handlingEnrico Jorns2018-04-051-6/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As introduced by a56fb90dc3805494eeaf04c60538425e8d52efc5 ('base.bbclass wipe ${S} before unpacking source') the base.bbclass uses a python anonymous function to set the 'do_unpack' varflag 'cleandirs' to either '${S}' or '${S}/patches' depending on equality of '${S}' and '${WORKDIR}'. Not that this only differs from the way almost all other recipes set or modify a tasks 'cleandirs' flag, it also has a significant impact on the kernel.bbclass (and possibly further ones) and causes incorrect behavior for rebuilds triggered by source modification, e.g. by a change of the defconfig file for a kernel build. The kernel.bbclass tries to extend do_unpack[cleandirs]: | do_unpack[cleandirs] += " ${S} ${STAGING_KERNEL_DIR} ${B} ${STAGING_KERNEL_BUILDDIR}" As python anonymous functions are evaluated at the very end of recipe parsing, the d.setVarFlag('do_unpack', 'cleandirs', '${S}') statement in base.bbclass will overwrite every modification to cleandirs that is done as shown for the kernel class above. As a result of this, a change to a kernels 'defconfig' will lead to an updated defconfig file in ${WORKDIR}, but as ${B} never gets cleaned and ${B}/.config still exists, it will not be copied to ${B}/.config and thus not find its way in the build kernel. This is a severe issue for the kernel development and build process! This patch changes setting of the cleandirs varflag in base.bbclass to a simple variable assignment as almost all other recipes do it. This now again allows overwriting or appending the varflag with common methods such as done in kernel.bbclass. This issue affects morty, pyro, rocko and master. (From OE-Core rev: 20901b9783220aa6e7adae4951c531919c20859b) Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/externalsrc: ensure cleandirs code handles non-absolute pathsPaul Eggleton2018-04-051-1/+2
| | | | | | | | | | | | | | | | It's possible that a trailing or extra slash somewhere in the external source path could result in the directory not being removed from cleandirs; it's also possible that a cleandirs entry is somewhere underneath the source tree and that tree should never have parts of it deleted by the build system. Use oe.path.is_path_parent() (which makes paths absolute before checking them) to find out if any path in cleandirs is anywhere underneath the external source path, and drop it if it is. (From OE-Core rev: 87ec0fb470274d980f8553a85f778809c269c5d7) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/externalsrc: handle if cleandirs contains python expressionsPaul Eggleton2018-04-051-1/+3
| | | | | | | | | | | | | | Use the existing oe.recipeutils.split_var_value() function to split the unexpanded value of the cleandirs varflag, in case it contains python expressions - we don't want to split the expression itself as the chunks will not expand properly individually and we can miss something that expands to the source tree (and thus it can get deleted, the avoidance of which is the whole point of this code). (From OE-Core rev: 611cee69d7300a4746edd752c9557af60e7beecc) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: fix typo in sulogin-path settingChen Qi2018-04-041-1/+1
| | | | | | | | | | Fix typo in sulogin-path setting. It should be ${base_sbindir} instead of just {base_sbindir}. (From OE-Core rev: c168f6fe35ada66f7d6d6b5151fa248230c38676) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative: add variables to the whitelist so that it does not re-triger ↵Cuero Bugot2018-04-031-0/+3
| | | | | | | | | | | | | | | | recipe parsing When uninative is activated (poky's default) internal datastore variables are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) to enable uninative support. This is happening after parsing is done at the beginning of the build. On the next bitbake call the recipe would be parsed if the two variables above were not added to the parsing whitelist BB_HASHCONFIG_WHITELIST. The fix is to add these two variables to the recipe parsing whitelist BB_HASHCONFIG_WHITELIST, this is done at recipe parsing time, only when uninative.bbclass is used. (From OE-Core rev: 75bb95ada98ef129d2fa48568f27dddb078c852c) Signed-off-by: Cuero Bugot <cbugot@sierrawireless.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: Improve logging capabilities for do_create_manifestAlejandro Enedino Hernandez Samaniego2018-04-031-7/+27
| | | | | | | | | | | | | Adds a couple of prints to get a nicer log, and creates a small summary or report after checking every module, it makes it more feasible for adoption, easier to debug why a module ended at a certain package and see how the manifest was created. (From OE-Core rev: 4c2af72f51a7bf187615fc0b3a229d25c3e191e9) Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemtap: Backport a fix for build with gcc8Khem Raj2018-04-032-0/+216
| | | | | | | (From OE-Core rev: b751e865375b325df4083d85af191da4dc3a27ee) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nasm: Fix pure function warningsKhem Raj2018-04-032-1/+30
| | | | | | | (From OE-Core rev: e3c76fd3db928fc487e86325df299f3f02ef369c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x264: Use updated gnu-config artifactsKhem Raj2018-04-031-0/+2
| | | | | | | | | | | | | | It is not using autoconf completely, therefore there is no autoreconf happening, so when we depend on latest gnu-config changes e.g. new architectures like riscv the build does not see them and fails. Installing these files from native sysroot helps (From OE-Core rev: 2624f400af6e51f6f3379f9f119b8f81c75a014b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-core2.inc: add cpu type for qemuRuslan Ruslichenko2018-04-031-0/+3
| | | | | | | | | | | | 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). (From OE-Core rev: 11f4fdcafed1383e5b6c2e634c670d19124e537a) Signed-off-by: Ruslan Ruslichenko <rruslich@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: do not hardcode python2.7 pathRuslan Ruslichenko2018-04-031-1/+1
| | | | | | | | | | | | | It can be installed to some non standard path in which case build will be broken. As python2.7 is specified in HOSTTOOLS we can rely that it is present in the PATH, so no need to hardcode it to /usr/bin. (From OE-Core rev: a200d22b26aded093289cb9150b3f05f76578c83) Signed-off-by: Ruslan Ruslichenko <rruslich@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipetool: create: fix port number parsing issueMing Liu2018-04-031-2/+4
| | | | | | | | | | | | | | | | | A flaw was found when I run: $ recipetool create "ssh://git@xxx.xxx:7999/xxx.git" the url turned out to be: "git://git@xxx.xxx/7999/xxx.git;protocol=ssh" after parsing, the port number was parsed as part of the path, this is definitely wrong and lead to fetching failures. This issue could be fixed in reformat_git_uri, by filtering out port numbers when formatting ":". (From OE-Core rev: 4290e04b69360b5e1da9f37166015e30f66cb335) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: upgrade 3.10.2 -> 3.10.3Otavio Salvador2018-04-033-2/+2
| | | | | | | | | | | | | | | | | | | | | ,----[ Changes in 3.10.3 ] | Brad King (1): | CMake 3.10.3 | | Craig Scott (1): | GoogleTest: Rename TIMEOUT parameter to avoid clash | | Sebastian Holtermann (1): | Autogen: Fix for the empty source file crash in 3.10.2 | | Tianhao Chai (1): | ccmake: fix status line buffer overflow on very wide terminals `---- (From OE-Core rev: ae230e1f858f83d1ff063554b49bd3ee1f880f76) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: Prefer dri3 for x11/openglAndreas Müller2018-04-031-1/+1
| | | | | | | | | | | Adresses [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=12642 (From OE-Core rev: 8509e2e1a87578882b71948ccef3b50ccf1228b3) Signed-off-by: Andreas Müller <schnitzeltony@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: fix unitialized modifier for DRI2Andreas Müller2018-04-032-0/+44
| | | | | | | | | | | | This came up whith disabled DRI3 on Raspi/VC4 [1] but might be important for other drivers: It fixes an improper initialization. [1] https://lists.freedesktop.org/archives/mesa-dev/2018-March/190562.html (From OE-Core rev: bfd5d2cefd56cb60b51b2bed57cb92dcfd5756c9) Signed-off-by: Andreas Müller <schnitzeltony@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass: improve reproducibilityJonathan Liu2018-04-031-0/+1
| | | | | | | | | | | Set KBUILD_BUILD_VERSION=1 to avoid build version being incremented on every build. It is visible in the output of "cat /proc/version" after the hash character. (From OE-Core rev: 7fa32ee42c3320e9e2b24ef747e43484b719f617) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initrdscripts: init-install(-efi).sh: don't assume 20M boot partitionCalifornia Sullivan2018-04-036-8/+30
| | | | | | | | | | | | | | | | | | | | | With multi kernel support in the installer we can exceed this limit. Calculate a sane size by checking the size of the original boot partition minus some objects we know won't be installed, plus some extra space for users. In addition, in the common case where only one small kernel is present to be installed, we actually get a smaller boot partition with less wasted space. Also add VIRTUAL-RUNTIME_base-utils to RDEPENDS where these scripts are used, as they're needed for the du command. [YOCTO #12583]. (From OE-Core rev: 2ca601bef44a07512c93b8452cf9001dce402617) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory_analysis.py: Check if RPROVIDES changed orderAmanda Brindle2018-04-031-1/+13
| | | | | | | | | | | | | | Instead of assuming order has changed if no package has been added or removed, loop through packages to check if order has changed. This will prevent the script from falsely reporting "changed order" if a version has increased. Fixes [YOCTO #12334] (From OE-Core rev: 77d701c5fb5961bd818810a4d4cb3a9bd2432fae) Signed-off-by: Amanda Brindle <amanda.r.brindle@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Upgrade to latest masterRichard Purdie2018-04-031-1/+1
| | | | | | | | | | | | | | | This change includes several bug fixes and improvements, including better path handling (the existance of . and .. for files), handling of the sticky bit, and syscall renameat2 handling and interception through syscall() which was breaking coreutils mv operations on fedora27. [YOCTO #12594] [YOCTO #12379] [YOCTO #11643] (From OE-Core rev: ddbcb88849d5c07a4cbbdc90fa1ab4d369476f8a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-14 15:42:46 +0000