Re: [yocto] [meta-qt5] How to contribute patches for qtwebengine in meta-qt5?

This patch is already included in 5.13.2 upgrade (ready in zeus-next and master-next branches), so you don't need to do anything. Otherwise like Khem says, submit the change for meta-qt5 repository like any other layer. The meta-qt5/qt* repositories are used to maintain the patches, but usually

Re: [yocto] systemd Version Going Backwards on Warrior

PR server never knows which one is really newer (in git). It just returns max(LOCALCOUNT)+1 when it gets query for hash which isn't stored in the database yet. Either the build in question didn't use PRserv at all or PRserv's cache was deleted between builds or the builds were using the same

Re: [yocto] [meta-security][PATCH] layer.conf: Update for zeus series

Acked-by: Martin Jansa Please merge this to unblock CI. On Wed, Oct 9, 2019 at 12:55 AM Armin Kuster wrote: > Signed-off-by: Armin Kuster > --- > conf/layer.conf | 2 +- > meta-integrity/conf/layer.conf | 2 +- > meta-security-compliance/

Re: [yocto] do_fetch_append: syntax error

On Tue, Oct 01, 2019 at 11:35:21AM +0300, Damien LEFEVRE wrote: > Hi, > > I have the following bbappend > > FILESEXTRAPATHS_prepend := "${THISDIR}/files:" > SRC_URI += " \ > file://tegra186_cti_defconfig \ > " > > do_fetch_append(){ > mv ${WORKDIR}/tegra186_cti_defconfig

Re: [yocto] Alternative to _git.bb convention for unstable versions?

You can easily add .inc file which will set all the PREFERRED_VERSIONs for all components you need and then the users will just add an "require" of this .inc files to their local.conf. "somepackage-unstable.bb" or "somepackage-devel.bb" this will make it 2 different components - not 2 different

Re: [yocto] package_qa fails on copy openssl

On Tue, Sep 10, 2019 at 08:49:35AM -0400, William Durocher wrote: > Currently updating a sumo build to warrior. One of our recipe called config > server uses nodejs which was updated from 8.9 in sumo to 10.5 in warrior. > As an interim solution we decided to keep the version of nodejs to 8.90. >

Re: [yocto] [yocto-docs][PATCH] ref-manual: mention PREPROCESS_RELOCATE_DIRS variable

On Mon, Aug 12, 2019 at 07:51:40PM +, Martin Jansa wrote: > Signed-off-by: Martin Jansa ping > --- > documentation/ref-manual/ref-classes.xml | 5 - > documentation/ref-manual/ref-variables.xml | 21 + > 2 files changed, 25 insertions(+), 1 deleti

Re: [yocto] [PATCH] In Yocto 2.7 powertop package is broken.

See https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg126436.html On Mon, Aug 19, 2019 at 11:35 AM Kaz Kylheku wrote: > Hi all, > > Via a .bbappend file in my own layers, I added the following patch to > build powertop, which is enabled when tools-profile is added to >

[yocto] [meta-security][PATCH] smack: add runtime dependency on python3-core

* fixes: ERROR: QA Issue: /usr/share/smack/smack_rules_gen contained in package smack requires /usr/bin/python3, but no providers found in RDEPENDS_smack? [file-rdeps] Signed-off-by: Martin Jansa --- recipes-mac/smack/smack_1.3.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion

[yocto] [yocto-docs][PATCH] ref-manual: mention PREPROCESS_RELOCATE_DIRS variable

Signed-off-by: Martin Jansa --- documentation/ref-manual/ref-classes.xml | 5 - documentation/ref-manual/ref-variables.xml | 21 + 2 files changed, 25 insertions(+), 1 deletion(-) diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref

Re: [yocto] [meta-integrity][PATCH 1/3] layer.conf: add dependency on meta-security

On Wed, Jul 24, 2019 at 02:23:24PM +0300, Dmitry Eremin-Solenikov wrote: > ima-evm-utils recipe depends on keyutils recipe which is a part of > meta-security layer. > > Signed-off-by: Dmitry Eremin-Solenikov > --- > meta-integrity/conf/layer.conf | 2 ++ > 1 file changed, 2 insertions(+) > >

Re: [yocto] Dealing with line endings

Hi Keith, you can use dos2unix.bbclass: http://git.openembedded.org/openembedded-core/tree/meta/classes/dos2unix.bbclass to convert them before do_patch. Cheers, On Tue, Jun 25, 2019 at 4:57 AM keith.derrick wrote: > I am using an upstream repo with a mix of line endings. > > > In my recipe,

Re: [yocto] [meta-gplv2][warrior][PATCH] bc: use u-a for bc as well

No problem, thanks for quick response. Looks like this patch wasn't merged in master as well (I thought it was), can you please push it as well. Thanks On Fri, Jun 21, 2019 at 2:59 PM Burton, Ross wrote: > Done, sorry. > > Ross > > On Fri, 21 Jun 2019 at 13:53, Mart

Re: [yocto] [meta-gplv2][warrior][PATCH] bc: use u-a for bc as well

ping for warrior On Tue, Jun 11, 2019 at 9:08 AM Martin Jansa wrote: > * bc can be provided by busybox as well (e.g. if you have your own > defconfig and forget to explicitly disable it: > ... > * > * Miscellaneous Utilities > * > adjtimex (4.7 kb) (ADJTIMEX) [

Re: [yocto] cortexa9t2hf instead of cortexa9hf

e of > armv7a. > > My two cent worth thinking, > Zoran > ___ > > > On Tue, Jun 18, 2019 at 7:13 PM Martin Jansa wrote: > > > > On Mon, Jun 17, 2019 at 07:47:36PM +0200, Arno Steffens wrote: > > > Thanks for explaining this. > >

Re: [yocto] cortexa9t2hf instead of cortexa9hf

On Mon, Jun 17, 2019 at 07:47:36PM +0200, Arno Steffens wrote: > Thanks for explaining this. > I take some time to read about thumb/thumb2. The feedback is mixed. It seems > to generate more compact code, but some say it speeds up, others it slows > down because of reduced function set - and it

Re: [yocto] cortexa9t2hf instead of cortexa9hf

See this oe-core commit (from 2.6 Thud): commit c88304a78e528596ca481cabe273749c286c352a Author: Andre McCurdy Date: Fri May 18 15:50:40 2018 -0700 arch-armv7a.inc: default to Thumb2 instruction set for armv7a and above which enabled Thumb2 by default, if you want to disable it as it was

Re: [yocto] YP sstate example conf file

Good question. I've one related to this as well. It would be also good to document (if it isn't somewhere already) what builds populate this mirror. I assume it will be some autobuilder job with DISTRO = poky, but without file listing enabled over http I cannot even guess which MACHINEs were

[yocto] [meta-gplv2][warrior][PATCH] bc: use u-a for bc as well

: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget_${PN} (). Deferring to first boot via 'exit 1' is no longer supported. Signed-off-by: Martin Jansa --- recipes-extended/bc/bc_1.06.bb | 2 +- 1 file

[yocto] [meta-gplv2][PATCH] bc: use u-a for bc as well

: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget_${PN} (). Deferring to first boot via 'exit 1' is no longer supported. Signed-off-by: Martin Jansa --- recipes-extended/bc/bc_1.06.bb | 2 +- 1 file

[yocto] [meta-gplv2][PATCH] elfutils: ignore new error from gcc-9

Signed-off-by: Martin Jansa --- recipes-devtools/elfutils/elfutils_0.148.bb | 4 1 file changed, 4 insertions(+) diff --git a/recipes-devtools/elfutils/elfutils_0.148.bb b/recipes-devtools/elfutils/elfutils_0.148.bb index a03b74e..1f07a28 100644 --- a/recipes-devtools/elfutils

[yocto] [opkg-utils][PATCH] opkg-list-fields: fix to print the fields again

Author: Alejandro del Castillo Date: Wed Dec 19 11:40:15 2018 -0600 opkg-make-index: add sha256sum support which replaced the modified __str__ function with print(self, checksum) Signed-off-by: Martin Jansa --- opkg-list-fields | 3 +-- 1 file changed, 1 insertion(+), 2 deletions

[yocto] [meta-gplv2][PATCH] bc: use u-a for bc as well

: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget_${PN} (). Deferring to first boot via 'exit 1' is no longer supported. Signed-off-by: Martin Jansa --- recipes-extended/bc/bc_1.06.bb | 2 +- 1 file

Re: [yocto] [meta-security][PATCH] keyutils: fix library install path

When you're on it, can you please check if it works with multilib? I think $(USRLIBDIR) doesn't respect ${libdir} from OE, so it always installs the library to /usr/lib instead of e.g. /usr/lib64 with multlilib. e.g. recipes-security/ccs-tools/ccs-tools_1.8.4.bb is setting USRLIBDIR=${libdir}, I

[yocto] [meta-gplv2][warrior][master][PATCH] licenses: restore Elfutils-Exception from oe-core

isted Elfutils-Exception was not in the licenses collected for recipe elfutils Signed-off-by: Martin Jansa --- conf/layer.conf | 2 ++ licenses/Elfutils-Exception | 12 2 files changed, 14 insertions(+) create mode 100644 licenses/Elfutils-Exception diff --git a/conf/lay

[yocto] [meta-gplv2][PATCH] layer.conf: Update to warrior release name series

Signed-off-by: Martin Jansa --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 43d578b..59f6a89 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -14,4 +14,4 @@ LAYERVERSION_gplv2 = "1" LAYERDEPENDS_gpl

Re: [yocto] failed to compile php_7.2.10.bb

On Wed, Oct 10, 2018 at 04:03:55PM -0400, Simon Chamlian wrote: > Hi, > > I tried to bitbake php_7.2.10.bb and I am getting the following error. > > Did anyone tried to compile php_7.2.10.bb ? > > Any clue on what the issue can be ? > > bb.data_smart.ExpansionError: Failure expanding variable

Re: [yocto] [pseudo] Pseudo 1.8+ xattr sqlite corruption

I did the same SRCREV bump locally and can confirm that https://bugzilla.yoctoproject.org/show_bug.cgi?id=12434 pseudo: Incorrect UID/GID in packaged files is still reproducible: ERROR: glibc-locale-2.24-r0 do_package_qa: QA Issue: glibc-locale:

Re: [yocto] coreutils postinstall warning

On Fri, Sep 14, 2018 at 07:38:49AM -0500, Seth Bollinger wrote: > On Mon, Aug 20, 2018 at 8:16 AM Seth Bollinger wrote: > > > Hello All, > > > > We've been seeing the following warning for a while now. Is this expected? > > > > WARNING: manuf-image-1.0-r0 do_rootfs: Intentionally failing

Re: [yocto] Postinstall scriptlets of ['coreutils'] have failed

custom busybox defconfig which enables nice applet? It's not enabled in default config: meta/recipes-core/busybox/busybox/defconfig:# CONFIG_NICE is not set On Mon, Sep 10, 2018 at 8:15 PM Jens Rehsack wrote: > > > Am 09.09.2018 um 20:56 schrieb Martin Jansa : > > Does cor

Re: [yocto] Postinstall scriptlets of ['coreutils'] have failed

s, > Jens > > Am 09.09.2018 um 19:27 schrieb Martin Jansa : > > busybox is most likely the one providing it in ${base_bindir} > > Recent busybox upgrade probably moved this file. > > There is also conflict on /usr/bin/setfattr between busybox and attr now. > > On Sun,

Re: [yocto] Postinstall scriptlets of ['coreutils'] have failed

busybox is most likely the one providing it in ${base_bindir} Recent busybox upgrade probably moved this file. There is also conflict on /usr/bin/setfattr between busybox and attr now. On Sun, Sep 9, 2018 at 7:22 PM Martin Jansa wrote: > There are 2 packages using u-a for nice, but

Re: [yocto] Postinstall scriptlets of ['coreutils'] have failed

There are 2 packages using u-a for nice, but one is using {bindir} and 2nd one is using {base_bindir} coreutils is using bindir, find what's using ${base_bindir} and change one of them to use the same u-a link as the other one. On Sun, Sep 9, 2018 at 5:59 PM Jens Rehsack wrote: > > > Am

Re: [yocto] net-snmp_5.8.bb failed to compile

Follow the READMEs and don't mix layers from different branches. You need to checkout all repositories with layers from the same branch to be compatible. Now you're mixing newer meta-oe branch with older oe-core branch which doesn't have bb.utils.filter function yet. On Tue, Aug 28, 2018 at 5:17

Re: [yocto] Intel machine with 64 Bit kernel and 32 Bit user space

image.bb: > do_image_wic > Summary: There were 3 WARNING messages shown. > Summary: There were 2 ERROR messages shown, returning a non-zero exit code. > > > The ERROR: lib32-my-image-1.0-r0 do_image_wic: The file > /usr/share/gcc-7.3.0/python/libstdcxx/__init__.py is installed by bot

Re: [yocto] Intel machine with 64 Bit kernel and 32 Bit user space

It's not as simple as that in some cases, there are some components which are pulled in 64bit version even when building lib32-foo-image. Some are easy to override from the config e.g.: ROOTFS_PKGMANAGE = "${LIB32_PREFIX}opkg" SPLASH = "${LIB32_PREFIX}psplash" but to prevent building e.g.

Re: [yocto] Error Report Tool Purge

. > > > > -Amanda Brindle > > > > *From:* Martin Jansa [mailto:martin.ja...@gmail.com] > *Sent:* Thursday, July 19, 2018 11:38 AM > *To:* Brindle, Amanda R > *Cc:* Yocto Project > *Subject:* Re: [yocto] Error Report Tool Purge > > > > I'm just curiou

Re: [yocto] Error Report Tool Purge

I'm just curious, how are you tracking which reports were viewed or linked to (and linked from where)? I often use a link to http://errors.yoctoproject.org in the mailing list or the recipes/commit message instead of copy pasting whole build error, because it already shortens the build paths and

Re: [yocto] bbappend extra SRC_URI ignored

mentions until the do_install > > Yet the nvpmodel.conf is never copied to ${WORKDIR} which > is > /home/damien/procbox-pyro/build-jetson-tx2/tmp/work/aarch64_tegra186-poky-linux/tegra-tools/28.2.0-r0 > in my case. > > Could some bitbake options disable this standard behavior?

Re: [yocto] bbappend extra SRC_URI ignored

On Thu, Jun 14, 2018 at 03:16:00PM +0300, Damien LEFEVRE wrote: > HI, > > I'm working on meta-tegra layer and I'd like to append a recipe. The > original recipe looks like this: > https://github.com/madisongh/meta-tegra/blob/rocko-l4t-r28.2/recipes-bsp/tegra-binaries/tegra-tools_28.2.0.bb >

Re: [yocto] [OE-core] [RFT] GCC 8.1

> That leaves only few issues in our internal components and strange failure > with perf which fails to include various header files: > perf/1.0-r9/perf-1.0/tools/perf/util/include/asm/byteorder.h:2:10: fatal > error: ../../../../include/uapi/linux/swab.h: No such file or directory >

Re: [yocto] [OE-core] [RFT] GCC 8.1

On Thu, May 10, 2018 at 09:11:45PM +0200, Martin Jansa wrote: > > > 5) nativesdk-libxcrypt fails to build (not sure which change caused > > > this, it build OK with sumo since the -std=gnu99 addition. > > > ../git/crypt-sunmd5.c:189:13: error: 'snprintf' output may

Re: [yocto] [OE-core] [RFT] GCC 8.1

On Mon, May 14, 2018 at 10:33:41AM -0600, Dan McGregor wrote: > On 10 May 2018 at 12:53, Khem Raj wrote: > > Hi Dan, > > > > Thanks for testing > > > > On 5/10/18 7:34 AM, Dan McGregor wrote: > >> > >> On 4 May 2018 at 18:26, Khem Raj wrote: > >>> > >>> Hi

Re: [yocto] [OE-core] [RFT] GCC 8.1

On Thu, May 10, 2018 at 04:11:00PM -0700, Andre McCurdy wrote: > On Thu, May 10, 2018 at 3:50 PM, Martin Jansa <martin.ja...@gmail.com> wrote: > > On Thu, May 10, 2018 at 03:40:53PM -0700, Andre McCurdy wrote: > >> On Thu, May 10, 2018 at 3:38 PM, Martin Jansa <martin.j

Re: [yocto] [OE-core] [RFT] GCC 8.1

On Thu, May 10, 2018 at 03:40:53PM -0700, Andre McCurdy wrote: > On Thu, May 10, 2018 at 3:38 PM, Martin Jansa <martin.ja...@gmail.com> wrote: > > see > > http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150654.html > > Removing -fno-omit-frame-point

Re: [yocto] [OE-core] [RFT] GCC 8.1

see http://lists.openembedded.org/pipermail/openembedded-core/2018-May/150654.html On Fri, May 11, 2018 at 12:38 AM Andre McCurdy <armccu...@gmail.com> wrote: > On Thu, May 10, 2018 at 3:07 PM, Martin Jansa <martin.ja...@gmail.com> > wrote: > > On Thu, May 10, 2018 at

Re: [yocto] [OE-core] [RFT] GCC 8.1

On Thu, May 10, 2018 at 11:43:25PM +0200, Martin Jansa wrote: > On Thu, May 10, 2018 at 12:27:50PM -0700, Andre McCurdy wrote: > > On Thu, May 10, 2018 at 12:11 PM, Martin Jansa <martin.ja...@gmail.com> > > wrote: > > > On Thu, May 10, 2018 at 11:50:02AM -0700, Kh

Re: [yocto] [OE-core] [RFT] GCC 8.1

On Thu, May 10, 2018 at 12:27:50PM -0700, Andre McCurdy wrote: > On Thu, May 10, 2018 at 12:11 PM, Martin Jansa <martin.ja...@gmail.com> wrote: > > On Thu, May 10, 2018 at 11:50:02AM -0700, Khem Raj wrote: > >> Hi Martin > >> > >> Thanks for testing and

Re: [yocto] [OE-core] [RFT] GCC 8.1

On Thu, May 10, 2018 at 11:50:02AM -0700, Khem Raj wrote: > Hi Martin > > Thanks for testing and reporting back > > On 5/9/18 2:38 AM, Martin Jansa wrote: > > My initial tests show couple issues, but usually caused by other changes > > in that branch, not the gcc-8

Re: [yocto] [OE-core] [RFT] GCC 8.1

My initial tests show couple issues, but usually caused by other changes in that branch, not the gcc-8 itself. 1) strace-4.22 from http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/gcc-8=af33a8b721cc9caebd3f5226b4c5903f666ab654 fails to build with ptest enabled (it builds with

Re: [yocto] Is the a reason for adding the + to SRCPV?

This might help you: https://github.com/webosose/meta-webosose/blob/master/meta-webos/recipes-core/glib-2.0/glib-2.0/0002-gdbus-codegen-also-replace-character-with-underscore.patch On Wed, Apr 11, 2018 at 5:59 PM, Måns Zigher wrote: > Hi, > > Thanks for your help. It is a

Re: [yocto] [meta-qt3][PATCH 1/2] layer: add LAYERSERIES_COMPAT

On Fri, Apr 13, 2018 at 03:41:26PM -0700, Armin Kuster wrote: > Signed-off-by: Armin Kuster > --- > conf/layer.conf | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/conf/layer.conf b/conf/layer.conf > index 84ab5f7..2100ffb 100644 > --- a/conf/layer.conf > +++

Re: [yocto] Getting the version of Yocto that is being used.

Cannot LAYERSERIES_CORENAMES added in rocko be used for that? On Thu, Apr 12, 2018 at 2:47 PM, Burton, Ross wrote: > I think the message here is that we need to embed the oe-core version > in the metadata somewhere... > > On 12 April 2018 at 13:11, Richard Collins >

[yocto] [meta-gplv2][PATCH] layer.conf: add LAYERSERIES_COMPAT

Signed-off-by: Martin Jansa <martin.ja...@gmail.com> --- conf/layer.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/layer.conf b/conf/layer.conf index f5601bb..3d614dc 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -13,3 +13,5 @@ BBFILE_PRIORITY_gplv

Re: [yocto] How to disable module auto-loading

On Tue, Mar 27, 2018 at 10:18:28AM +0200, Nicolas Salmin wrote: > Hello all, > > I would like to know the better way to disable module auto-loading ? > > I tried to create /etc/modprobe.d/blacklist.conf but as /etc/modprobe.d > doesn't exist on my rootfs i think is not a good solution. > > I

[yocto] [meta-gplv2][PATCH] nettle: refresh the patches

From: Martin Jansa <martin.ja...@gmail.com> * fixes: WARNING: nettle-2.7.1-r0 do_patch: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches. The context lines in the patches can be updated with devtool: devtool modify devtool finish -

Re: [yocto] Does PACKAGECONFIG only apply to autotools recipes

It's applied in PACKAGECONFIG_CONFARGS variable and various bbclasses (and also various recipes) use this variable where needed, see git grep: meta/classes/base.bbclass:appendVar('PACKAGECONFIG_CONFARGS', extraconf) meta/classes/autotools.bbclass:EXTRA_OECONF_append = "

Re: [yocto] [meta-raspberrypi][PATCH] recipes: use oe.utils.conditional instead of deprecated base_conditional

t;giz...@gmail.com> > wrote: > >> Hi Martin, > >> > >> On Tue, Jan 30, 2018 at 2:31 PM, Martin Jansa <martin.ja...@gmail.com> > wrote: > >>> Signed-off-by: Martin Jansa <martin.ja...@gmail.com> > >>> --- > >>

[yocto] [meta-raspberrypi][PATCH] recipes: use oe.utils.conditional instead of deprecated base_conditional

Signed-off-by: Martin Jansa <martin.ja...@gmail.com> --- recipes-kernel/linux/linux-raspberrypi.inc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/recipes-kernel/linux/linux-raspberrypi.inc b/recipes-kernel/linux/linux-raspberrypi.inc index df3a3d7..a1c4e52

Re: [yocto] Error do_compile libepoxy

FWIW: here nativesdk-libepoxy fails in do_configure already since meson conversion FileNotFoundError: [Errno 2] No such file or directory: 'TOPDIR/tmp-glibc/work/x86_64-nativesdk-oesdk-linux/nativesdk-libepoxy/1.4.3-r0/build/meson-private/sanitycheckc.exe'

Re: [yocto] Debugging sstate-cache

I'm using oe-core/scripts/sstate-diff-machines.sh script (which calls bitbake -S) to generate "snapshots" of sstate signatures for interesting builds (in our case daily official builds) and then every time I notice something unexpectedly being rebuilt, I can use the same script to create snapshot

Re: [yocto] .kernel-meta/configs folder missing make linux-raspberrypi to fail

I'm seeing the same build errors in linux-raspberrypi with various versions of Gentoo and Ubuntu (mostly tested with 14.04 and 16.04), I doubt that this issue is specific for Fedora 27. On Thu, Dec 14, 2017 at 2:31 PM, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > Also is worth

Re: [yocto] Build error: "u-boot-imx_2017.03.bb:do_compile" failed ( freescale I.MX 6 on Ubuntu 16.04) ?

I don't know what version of Yocto you're using, but if it's older than 2.3 (which does filter what binaries are seen from the host system with HOSTTOOLS), then your build is probably autodetecting swig from host and you can easily disable that with: do_compile_prepend () { sed 's@\(^always

Re: [yocto] buildhistory.bbclass "version-going-backwards" for AUTOINC

I think you can disable version-going-backwards check as any other QA check by removing it from WARN_QA and ERROR_QA variables. Even with AUTOINC you should use PR service to get increasing AUTOINC numbers, so the warning is correct, if you want working upgrade paths on the device then you need

Re: [yocto] rocko: QA issue with glibc-locale

Similar QA issue is shown when you use: LOCALE_GENERATION_WITH_CROSS-LOCALEDEF_forcevariable = "0" which is needed to build glibc-locale with pyro on hosts with glibc-2.26 (with ENABLE_BINARY_LOCALE_GENERATION = "1"). On Fri, Oct 20, 2017 at 11:44 AM, Alexander Kanavin <

Re: [yocto] [pyro][bitbake][PATCH] bitbake: Replace deprecated git branch parameter "--set-upstream"

l: the '--set-upstream' option is no longer supported. Please use > '--track' or '--set-upstream-to' instead. > > ERROR: PACKAGE do_unpack: Function failed: base_do_unpack > > (Bitbake rev: 2ab50074c1a6c56a8a178755de108447d7b7acaf) > > Signed-off-by: Andre Rosa <andre.r.

Re: [yocto] u-boot recipe: Missing dependencies

Be aware that when you provide python-native, it's more likely that swig-native will be detected in sysroot as well and then u-boot will fail to build libfdt python library. To prevent this autodetection you can use something like this: do_compile_prepend () { sed 's@\(^always += $(if

[yocto] [meta-raspberrypi][PATCH] Revert "qtbase: Enable EGLFS support"

* this reverts commit 04b37dbdb79638b17a670280058400ffaf1b6ccb. * this makes qtbase and everything which depends on some qt* recipe to be effectivelly MACHINE_ARCH Signed-off-by: Martin Jansa <martin.ja...@gmail.com> --- dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend | 3 ---

Re: [yocto] "(-)"??

null and nothing can also be matched in MACHINE names, so to make sure people should use: COMPATIBLE_MACHINE = "(^$)" On Thu, Sep 21, 2017 at 8:41 AM, Peter Kjellerstedt < peter.kjellerst...@axis.com> wrote: > > -Original Message- > > From: yocto-boun...@yoctoproject.org [mailto:yocto-

Re: [yocto] [meta-raspberrypi][PATCH 1/3] linux-raspberrypi_4.9.bb: Upgrade to 4.9.50

ve/usr/bin/aarch64-webos-linux/../../ > libexec/aarch64-webos-linux/gcc/aarch64-webos-linux/7.2.0/ld > > gold ? > > On Tue, Sep 19, 2017 at 6:58 AM, Martin Jansa <martin.ja...@gmail.com> > wrote: > > On Mon, Sep 18, 2017 at 12:29:44PM -0700, Khem Raj wrote: > >>

Re: [yocto] [meta-raspberrypi][PATCH 1/3] linux-raspberrypi_4.9.bb: Upgrade to 4.9.50

On Mon, Sep 18, 2017 at 12:29:44PM -0700, Khem Raj wrote: > On Mon, Sep 18, 2017 at 11:48 AM, Martin Jansa <martin.ja...@gmail.com> wrote: > > With these 3 changes included I see following failure with raspberrypi3-64, > > it might be something caused by last oe-core upgrade,

Re: [yocto] [meta-raspberrypi][PATCH 1/3] linux-raspberrypi_4.9.bb: Upgrade to 4.9.50

With these 3 changes included I see following failure with raspberrypi3-64, it might be something caused by last oe-core upgrade, but I haven't noticed anything suspicious there. Looks familiar? | VDSOL arch/arm64/kernel/vdso/vdso.so.dbg |

Re: [yocto] [meta-raspberrypi] ERROR: No recipes available for gstreamer

You're missing incompatible branches, use the same branch for all 3 and it will work. On Wed, Sep 13, 2017 at 4:48 PM, yahia farghaly wrote: > Minutes ago, i pulled the recent commits for poky,meta-oe, meta-raspberry > pi > and when i build this comes. there are

Re: [yocto] cannot re-use shared state cache between build hosts

Why do you use: ";downloadfilename=PATH " ? On Fri, Sep 1, 2017 at 3:54 PM, Andrea Galbusera wrote: > Hi! > > I was trying to share sstate between different hosts, but the consumer > build system seems to be

Re: [yocto] layer.conf on openembedded-core ?

mentation > On Aug 15, 2017 10:11 PM, "Martin Jansa" <martin.ja...@gmail.com> wrote: > > > But it's related to it, in this thread he added oe-core/meta in master > > branch to BBLAYERS in poky build (already including poky/meta) from pyro > > branch. > >

Re: [yocto] ERROR: gcc-source-6.3.0-6.3.0-r0 do_fetch: Fetcher failure for URL: 'file://0002-uclibc-conf.patch'. Unable to fetch URL from any source.

He is mixing poky/pyro with oe-core/master. All recent issues reported by Riko are caused by that. On Tue, Aug 15, 2017 at 5:49 PM, Khem Raj wrote: > > Thanks for sharing your build configuration. It says you are on > pyro release and I see this patch is there. So something

Re: [yocto] layer.conf on openembedded-core ?

But it's related to it, in this thread he added oe-core/meta in master branch to BBLAYERS in poky build (already including poky/meta) from pyro branch. That's why he is seeing 3 strange issues reported in couple threads already (and this is also 3rd time someone telling him that he shouldn't

Re: [yocto] How can I use PREFERRED_VERSION_ ?

and you should start by not including 2 different versions of openembedded-core/meta in your builds. Then you won't need PREFERRED_VERSION for openssl and the issue with wic.vmdk you reported elsewhere will also probably disappear. On Tue, Aug 15, 2017 at 7:31 AM, Khem Raj

Re: [yocto] RFC: Backwards compatibility checking sstate-cache

I haven't tried the patches, but I really like this idea (I was suggesting something like that since 2011 http://permalink.gmane.org/gmane.comp.handhelds.openembedded.core/10327) and I'm glad you weren't discouraged attempting to do this. It also implements 3) b) idea from

[yocto] [PATCH][meta-gplv2] gnutls: make it independent on gnutls.inc from oe-core

ed-off-by: Martin Jansa <martin.ja...@gmail.com> --- recipes-support/gnutls/gnutls.inc | 57 + recipes-support/gnutls/gnutls_3.3.27.bb | 8 + 2 files changed, 58 insertions(+), 7 deletions(-) create mode 100644 recipes-support/gnutls/gnutls.inc

Re: [yocto] [PATCH][meta-gplv2] gnutls: add use-pkg-config-to-locate-zlib.patch

ERROR: gnutls-3.3.27-r0 do_fetch: Fetcher failure for URL: 'file://correct_rpl_gettimeofday_signature.patch'. Unable to fetch URL from any source. On Fri, Jun 23, 2017 at 11:25 AM, Martin Jansa <martin.ja...@gmail.com> wrote: > Probably yes as it got broken again yesterday: > > &

Re: [yocto] [PATCH][meta-gplv2] gnutls: add use-pkg-config-to-locate-zlib.patch

Probably yes as it got broken again yesterday: On Mon, Jun 12, 2017 at 9:13 PM, Burton, Ross wrote: > > On 12 June 2017 at 20:04, Andre McCurdy wrote: > >> Would it be better to just make the meta-gplv2 gnutls recipe self >> contained and stop

Re: [yocto] Compiling meta-browser ==>chromium ? cleaning ?

You didn't say which versions you're using. If you're using latest oe-core with gcc7 then you will need v3 version of this change: http://lists.openembedded.org/pipermail/openembedded-devel/2017-June/113247.html I'll send it later today. > And how can I clean after building it ? It took about

[yocto] [PATCH][meta-gplv2] gnutls: add use-pkg-config-to-locate-zlib.patch

h file. use-pkg-config-to-locate-zlib.patch Signed-off-by: Fan Xin <fan@jp.fujitsu.com> Signed-off-by: Ross Burton <ross.bur...@intel.com> and no longer applies for this version. Signed-off-by: Martin Jansa <martin.ja...@gmail.com> --- .../gnutls/use-pkg-con

Re: [yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

And it's not clear from the diff you send, but like linux-yocto-dev.bb example above, the recipe needs to be renamed from linux-raspberrypi_dev.bb to linux-raspberrypi-dev.bb to make it different provider. On Thu, Jun 1, 2017 at 9:08 AM, Martin Jansa <martin.ja...@gmail.com> wrote: >

Re: [yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

e: > >>> > >>> On Tue, May 30, 2017 at 10:25 AM, Andre McCurdy <armccu...@gmail.com> > >>> wrote: > >>> > On Tue, May 30, 2017 at 10:15 AM, Paul Barker <pbar...@toganlabs.com > > > >>> > wrote: > >>>

[yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

bblayers.conf, that's bad for people who want to be able to build without network access (completely from premirror) Signed-off-by: Martin Jansa <martin.ja...@gmail.com> --- recipes-kernel/linux/linux-raspberrypi_dev.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-

Re: [yocto] webkitgtk2 progress bar

> I have 22 cores here, and it is not a luxury, but an absolute necessity to get anything done as far as oe-core maintenance goes. Webkit's do_compile takes about half an hour - I can almost see that progress bar move :) Heh, you're lucky with "oe-core maintenance". My "bitbake world" builds

Re: [yocto] webkitgtk2 progress bar

You can try to use gold to save a bit of time linking the beast. On Wed, May 24, 2017 at 4:46 PM, Leonardo Sandoval < leonardo.sandoval.gonza...@linux.intel.com> wrote: > On Wed, 2017-05-24 at 16:23 +0200, Gary Thomas wrote: > > I see that the latest master update has brought a progress bar > >

Re: [yocto] Qt 5.8: do_rootfs: File 'qtdeclarative-plugins' not found

No, this won't be added to meta-qt5 layer, because it's not the right fix. If you're happy with empty packages, then you don't need meta-qt5 at all. Empty packages are useless and bitbake is right not to create them. My guess is that you don't have all necessary PACKAGECONFIGs enabled for

[yocto] [PATCHv2][meta-gplv2] gnutls: add older gnutls compatible with nettle

/commit/3fa80cf68919f07b3351b2722278ba463d6e731c * add recipe for last release in 3.3 branch which is compatible with nettle 2.7.1 used in meta-gplv2 Signed-off-by: Martin Jansa <martin.ja...@gmail.com> --- .../gnutls/configure.ac-fix-sed-command.patch | 31 ++ r

Re: [yocto] [RFC][meta-gplv2] layer priority and worth creating branch compatible with morty?

quot;native" recipes-support/gdbm/gdbm_1.8.3.bb:BBCLASSEXTEND = "native nativesdk" recipes-support/nettle/nettle.inc:BBCLASSEXTEND = "native nativesdk" On Fri, Apr 21, 2017 at 11:19 PM, Andre McCurdy <armccu...@gmail.com> wrote: > On Fri, Apr 21, 2017 at 1:59 PM, Martin Jansa &

[yocto] [RFC][meta-gplv2] layer priority and worth creating branch compatible with morty?

1) layer priority, currently it has: BBFILE_PRIORITY_gplv2 = "1" which is lower than oe-core with: BBFILE_PRIORITY_core = "5" so in order to use recipes from meta-gplv2 layer, user has to add couple PREFERRED_VERSIONS. Was this intended use for meta-gplv2? I can see some

Re: [yocto] [PATCH][meta-gplv2] gnutls: add older gnutls compatible with nettle

Thu, Apr 20, 2017 at 7:59 PM, Andre McCurdy <armccu...@gmail.com> wrote: > On Thu, Apr 20, 2017 at 9:20 AM, Martin Jansa <martin.ja...@gmail.com> > wrote: > > * gnutls depends on nettle-3.1* since 3.4.0: > > The requirement for nettle was bumped from 3.0 to 3.1

[yocto] [PATCH][meta-gplv2] gnutls: add older gnutls compatible with nettle

/commit/3fa80cf68919f07b3351b2722278ba463d6e731c * add recipe for last release in 3.3 branch which is compatible with nettle 2.7.1 used in meta-gplv2 Signed-off-by: Martin Jansa <martin.ja...@gmail.com> --- .../gnutls/configure.ac-fix-sed-command.patch | 31 ++ r

[yocto] [PATCH][meta-gplv2] bison: add missing patch from oe-core

* meta-gplv2/recipes-devtools/bison/bison_2.3.bb: Unable to get checksum for bison SRC_URI entry bison-2.3_m4.patch: file could not be found Signed-off-by: Martin Jansa <martin.ja...@gmail.com> --- recipes-devtools/bison/bison/bison-2.3_m4.patch

Re: [yocto] meta-efl build?

On Thu, Feb 16, 2017 at 07:48:33AM +, Takashi Matsuzawa wrote: > Hello. > > Thank you very much for the pointer, but I think this image is x11 based.. > > I can see EFL project has some pages mentioning about booting EFL on > wayland-only environment, but it is not yocto (or oe) based

Re: [yocto] [bitbake-devel] [oe] Infra Full Stop 12/26-12/29

On Sun, Dec 25, 2016 at 08:06:50PM -0800, Michael Halstead wrote: > In preparation for the scheduled maintenance I have moved > git.openembedded.org to a new server temporarily. E-mail and Patchwork > hooks may not work correctly. All other git operations as well as > listings at

Re: [yocto] Can't set march=armv5te

de in ARM mode and never in Thumb mode, correct? > > > > It still bugs me why the architecture name changed (I’ve traced through > the machine include path several times), but if at the end of the day it’ll > be compiling the same code then I’ll move on to some more product

Re: [yocto] Shared state doesn't live up to its name?

Compare the signatures of these 2 native builds. I'm still using sstate-diff-machines.sh to create archives of sstate signatures for interesting builds, so that I can easily compare them with other builds or the same build performed on different builder to see why something wasn't reused form

  1   2   3   4   >