[OE-core] [oe-core] package inclusion

Can i install tensorflow and h5py (since they are not there as recipes) using Internet on yocto? (just the way they are installed on ubuntu or other host OS) Thanks -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

Re: [OE-core] [PATCH] distcc: update to 3.3

I will take a look and fix, thanks! Thanks, Jackie From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Wednesday, March 21, 2018 18:44 To: Huang, Jie (Jackie) Cc: OE-core Subject: Re: [OE-core] [PATCH] distcc: update to 3.3 This fails to start under systemd so caused the QA to fail:

Re: [OE-core] [PATCH] oe-selftest: crosstap: add tests for crosstap script

Hi Alex, >From my understanding, oeqa.utils.commands.runqemu will start and stop qemu in >a single call. For crosstap testcase, it require the steps below: - start qemu - call to crosstap to ssh into qemu to use systemtap - stop qemu Therefore, crosstap testcase use the

Re: [OE-core] [yocto] Yocto Project Status WW12’18

On Tue, 2018-03-20 at 20:00 +0200, Alexander Kanavin wrote: > On 03/20/2018 05:59 PM, Richard Purdie wrote: > > > > > > > > > > > > > How long does a single run take, and why not run it every > > > > month? > > > Just a bit longer than a day, maybe 30 hours, if it needs to > > > update > > >

[OE-core] ✗ patchtest: failure for ref-manual: Update SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS

== Series Details == Series: ref-manual: Update SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS Revision: 1 URL : https://patchwork.openembedded.org/series/11518/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have

[OE-core] [PATCH] ref-manual: Update SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS

Describes the new wildcard syntax Signed-off-by: Joshua Watt --- documentation/ref-manual/ref-variables.xml | 17 + 1 file changed, 17 insertions(+) diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index

[OE-core] [PATCH v2 1/1] recipes-core: breakout hwclock.sh from busybox

* Move the hwclock.sh initscript from busybox into its own package and recipe (hwclock-init). This script is generally useful for distros that get their hwclock implementation from sources other than busybox (like util-linux). :busybox/* * Remove the busybox-hwclock package, as it no longer

[OE-core] [oe-core] Disable post install script during build time.

Hello, I see that there is a post install script in "meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb" which needs to be run on target. However, it is run on the host every time I make a build and the scriptlet fails since it is checking for /proc/consoles and bitbake gives this

[OE-core] [PATCH v2 0/1] recipes-core: breakout hwclock.sh from busybox

This is a resubmission of the previous patch by the same name submitted ~1 month ago, plus a fixup suggested by Andre McCurdy (calling getVar without `expand=True`). Otherwise, I have rebased to the latest master and revalidated that hwclock-init, busybox, and util-linux build as expected from

Re: [OE-core] [PATCH] librepo: disable building of tests and docs

No, they were not installed. Ross On 21 March 2018 at 18:25, Khem Raj wrote: > On Wed, Mar 21, 2018 at 12:27 AM, Anuj Mittal wrote: >> Also remove libcheck dependency which was required only for tests. >> > > Does this affect ptest converge ? > >>

[OE-core] [PATCH] mesa: Upgrade 17.3.6 -> 17.3.7

This version has been published at March 21, 2018, and it is a bugfix only release. It includes several important fixes that were made as part of 18.0.0 development cycle. Full list of bug fixes can be see online at: https://www.mesa3d.org/relnotes/17.3.7.html Signed-off-by: Otavio Salvador

[OE-core] Disable post install script during build time.

Hello, I see that there is a post install script in "meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb" which needs to be run on target. However, it is run on the host every time I make a build and the scriptlet fails since it is checking for /proc/consoles and bitbake gives this

Re: [OE-core] [PATCH] librepo: disable building of tests and docs

On Wed, Mar 21, 2018 at 12:27 AM, Anuj Mittal wrote: > Also remove libcheck dependency which was required only for tests. > Does this affect ptest converge ? > Signed-off-by: Anuj Mittal > --- > meta/recipes-devtools/librepo/librepo_1.8.1.bb | 4

[OE-core] [morty][PATCH] e2fsprogs: fix compatibility with glibc 2.27

glibc 2.27 added function copy_file_range(), and e2fsprogs happens to have a different function with the same name. The conflict made e2fsprogs-native build fail. Here's a backport of a fix from upstream, the fix was released in e2fsprogs 1.43.8. The master branch doesn't need this fix, since it

[OE-core] [pyro][PATCH] e2fsprogs: fix compatibility with glibc 2.27

glibc 2.27 added function copy_file_range(), and e2fsprogs happens to have a different function with the same name. The conflict made e2fsprogs-native build fail. Here's a backport of a fix from upstream, the fix was released in e2fsprogs 1.43.8. The master branch doesn't need this fix, since it

[OE-core] [rocko][PATCH] e2fsprogs: fix compatibility with glibc 2.27

glibc 2.27 added function copy_file_range(), and e2fsprogs happens to have a different function with the same name. The conflict made e2fsprogs-native build fail. Here's a backport of a fix from upstream, the fix was released in e2fsprogs 1.43.8. The master branch doesn't need this fix, since it

[OE-core] [PATCH] gtk-doc: don't regenerate gtk-doc in do_install

In out-of-tree builds gtk-doc's setup-build target copies all the content from $srcdir to $builddir. However, if some of this content is regenerated at configure time this can happen: 1) configure writes new build/version.xml 2) make compile copies content, including the tarball's src/version.xml

[OE-core] [PATCH v2] rootfs-postcommands: put image testdata under sstate control

From: André Draszik The testdata.json is being written to DEPLOY_DIR_IMAGE directly, thus bypassing sstate, which results in an ever growing list of files. Write them to IMGDEPLOYDIR instead, so as to benefit from the automatic management via sstate. Signed-off-by: André

[OE-core] [oe-core] package installation

i am to install h5py on yocto's image poky , the below is the repo of it https://github.com/h5py/h5py i'd like to know if there is its respective recipe avialble? Thanks -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org

Re: [OE-core] [yocto] Yocto Project Status WW12’18

Monthly seems like a good enough cadence to give everyone time to review the mails, send the mails, get reviewed on the list, go through the autobuilder, and eventually reach master. Too fast and AUH will be sending nagging mails for a patch which is shortly being merged. Can we stop

Re: [OE-core] [yocto] Yocto Project Status WW12’18

On 03/21/2018 04:24 PM, Philip Balister wrote:     Which brings me to a question: what is a good schedule and cadence     for AUH runs? Currently it's run on the 15th of every odd-numbered     month (so January, March, and so on), but I thought of shifting it     one month forward, so it

Re: [OE-core] [meta-openembeded] bug in adding network layer

Cool, thanks! So should I add connman to local.conf of poky to get WiFi connection? On Wed, 21 Mar 2018, 17:10 Burton, Ross, wrote: > The Yocto kernel, as that is the kernel which is running. > > On 21 March 2018 at 11:36, Rajath C S wrote: > >>

Re: [OE-core] [yocto] Yocto Project Status WW12’18

On 03/20/2018 05:26 AM, Alexander Kanavin wrote: > On 03/20/2018 12:52 PM, Burton, Ross wrote: >>     Which brings me to a question: what is a good schedule and cadence >>     for AUH runs? Currently it's run on the 15th of every odd-numbered >>     month (so January, March, and so on), but I

Re: [OE-core] [PATCH] oe-selftest: crosstap: add tests for crosstap script

On 03/20/2018 01:59 AM, Yeoh Ee Peng wrote: +def start_qemu_with_image(self, recipe, fstypes, cmd, targetlogger): +tinfoil = bb.tinfoil.Tinfoil() +tinfoil.prepare(config_only=False, quiet=True) +try: +tinfoil.logger.setLevel(logging.WARNING) +

[OE-core] [PATCH] externalsrc: do not call make clean for recipes with CLEANBROKEN = "1" set

ERROR: distrho-ports-0.0.0+git999-r0 do_buildclean: oe_runmake failed ERROR: distrho-ports-0.0.0+git999-r0 do_buildclean: Function failed: do_buildclean ERROR: Logfile of failure stored in: <...>/temp/log.do_buildclean.17285 Log data follows: | DEBUG: Executing shell function do_buildclean |

Re: [OE-core] Openembedded-core Digest, Vol 86, Issue 203

On 03/21/2018 10:02 AM, Yeoh, Ee Peng wrote: In order to convert this to runtime/testimage, we will need to perform below 1) Modify existing crosstap script to inverse the dependency on bitbake -e, provide environment variables required as argument 2) Add additional step outside of testimage

Re: [OE-core] [meta-openembeded] bug in adding network layer

The Yocto kernel, as that is the kernel which is running. On 21 March 2018 at 11:36, Rajath C S wrote: > By kernel are you referring to the yocto's kernel or my host machine > kernel? > > if it is host machine kernel then i have the drivers > and , what should i do with

Re: [OE-core] [meta-openembeded] bug in adding network layer

By kernel are you referring to the yocto's kernel or my host machine kernel? if it is host machine kernel then i have the drivers and , what should i do with connman? thanks Rajath C S, 9964182112, Bangalore - 560060 On Wed, Mar 21, 2018 at 5:02 PM, Burton, Ross wrote:

Re: [OE-core] [meta-openembeded] bug in adding network layer

I never mentioned glib-networking and it wont help at all. If connman can't see your wifi then your kernel is missing the drivers you need. Ross On 21 March 2018 at 10:53, Rajath C S wrote: > yes, when clicked on it. it says Ethernet connection > > so, inside oe-core

Re: [OE-core] [oe-core] meta data error while building

If you made that change during a build, it's because you made a change during a build. Don't worry about it, it will go away on the next build. (its telling you that the hash of the recipe state changed from first parse to execution, which happened because you changed it) Ross On 21 March 2018

[OE-core] [oe-core] meta data error while building

The below is the error while building core-image-sato, this error popped after i including the line : PACKAGECONFIG_pn-opencv = "python2" Please help me with the solution ERROR: When reparsing /home/jarvis/poky/meta/recipes-sato/images/core-image-sato.bb.do_configure, the basehash

Re: [OE-core] [meta-openembeded] bug in adding network layer

yes, when clicked on it. it says Ethernet connection so, inside oe-core there is a folder and file called : glib-networking_2.54.1.bb; so now acording to your second msg to enable wifi should i include this file in MAGE_INSTALL_append command of local.conf? Rajath C S, 9964182112, Bangalore -

Re: [OE-core] [meta-openembeded] bug in adding network layer

Then you have a nice button in the top right to setup wifi already. Ross On 21 March 2018 at 10:42, Rajath C S wrote: > sure, i will look into that, thanks. > and , i am actually using core-image-sato > > regards, > Rajath C S > > Rajath C S, > 9964182112, > Bangalore

Re: [OE-core] [PATCH] distcc: update to 3.3

This fails to start under systemd so caused the QA to fail: https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/882/steps/Running%20Sanity%20Tests_7/logs/stdio Ross On 15 March 2018 at 08:24, wrote: > From: Jackie Huang > > *

Re: [OE-core] [meta-openembeded] bug in adding network layer

sure, i will look into that, thanks. and , i am actually using core-image-sato regards, Rajath C S Rajath C S, 9964182112, Bangalore - 560060 On Wed, Mar 21, 2018 at 4:11 PM, Burton, Ross wrote: > Ideally in an image of your own creation, as local.conf tweaking is for >

Re: [OE-core] [meta-openembeded] bug in adding network layer

Ideally in an image of your own creation, as local.conf tweaking is for experimentation only. There's a section in the manual about customising images, and I recommend that you start from an image with functionality instead of starting from a minimal image and trying to discover how to do basics

Re: [OE-core] [meta-openembeded] bug in adding network layer

so the connman / ifupdown and wireless-tools have to be placed in the local.conf file right? Rajath C S, 9964182112, Bangalore - 560060 On Wed, Mar 21, 2018 at 3:57 PM, Burton, Ross wrote: > ifupdown and wireless-tools will give you the basics to configure it by > hand,

Re: [OE-core] [meta-openembeded] bug in adding network layer

ifupdown and wireless-tools will give you the basics to configure it by hand, or use connman. Or network-manager, in meta-oe. core-image-sato includes both connman and a UI to join to wifi. Ross On 21 March 2018 at 10:25, Rajath C S wrote: > > thanks, > > i will

[OE-core] Fwd: [meta-openembeded] bug in adding network layer

thanks, i will follow the said things, but as of now my situation is as such : " sure, i will have one other question that is how to establish internet connection on to poky? that is , i have placed the meta-networking layer in bblayer.conf file so after that which recipe should i add to

Re: [OE-core] [PATCH] python-setuptools: 38.5.2 -> 39.0.1

The 39.0.0 upgrade has already been merged, and this will break python3-setuptools. On 21 March 2018 at 03:33, Huang Qiyu wrote: > Upgrade python-setuptools from 38.5.2 to 39.0.1. > > Signed-off-by: Huang Qiyu > --- >

Re: [OE-core] [meta-openembeded] bug in adding network layer

First, you don't need meta-networking to make networking "work", because oe-core has the basics. Second, you need to match the release of layers. You're using meta-networking master, and a previous release of poky. Checkout the corresponding release branch of meta-networking. Ross On 21 March

Re: [OE-core] [oe-core] package inclusion error

Hi, With "oe-pkgdata-util list-pkgs -p opencv" command, you can check every packages made from opencv recipe. One of them is python3-opencv, did you add it to IMAGE_INSTALL as well as opencv? Best regards, Vincent 2018-03-21 8:18 GMT+01:00 Rajath C S : > opencv recipe

[OE-core] [PATCH 1/3] logrotate: update to 3.14.0

Signed-off-by: Yi Zhao --- .../logrotate/{logrotate_3.13.0.bb => logrotate_3.14.0.bb}| 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/logrotate/{logrotate_3.13.0.bb => logrotate_3.14.0.bb} (95%) diff --git

[OE-core] [PATCH 2/3] less: update to 530

Signed-off-by: Yi Zhao --- meta/recipes-extended/less/{less_529.bb => less_530.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-extended/less/{less_529.bb => less_530.bb} (89%) diff --git a/meta/recipes-extended/less/less_529.bb

[OE-core] [PATCH 3/3] libcap-ng: update to 0.7.9

Rebase python.patch. Signed-off-by: Yi Zhao --- .../libcap-ng/libcap-ng/python.patch | 28 -- .../{libcap-ng_0.7.8.bb => libcap-ng_0.7.9.bb} | 4 ++-- 2 files changed, 18 insertions(+), 14 deletions(-) rename

Re: [OE-core] Openembedded-core Digest, Vol 86, Issue 203

Hi Alex, I had gathered additional information related to this oe-selftest testcase for crosstap. 1) Dependencies of crosstap script a) bitbake -e virtual/kernel & bitbake -e systemtap-native to gather the environment variables ( STAGING_BINDIR_TOOLCHAIN, TARGET_PREFIX,

[OE-core] [meta-openembeded] bug in adding network layer

I am tryiing to add meta-networking layer (to get Internet connection to poky)and i have included the following line of code in bbconfig file /home/jarvis/poky/meta-openembedded/meta-networking \ but while building i get this below error ERROR: ExpansionError during parsing

[OE-core] [PATCH] librepo: disable building of tests and docs

Also remove libcheck dependency which was required only for tests. Signed-off-by: Anuj Mittal --- meta/recipes-devtools/librepo/librepo_1.8.1.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-devtools/librepo/librepo_1.8.1.bb

[OE-core] [oe-core] package inclusion error

opencv recipe is in meta-oe layer, i have included meta-oe path in bblayer.config file and i have also included open cv in IMAGE_INSTALL and have successfully built the target using bitbake but still when i am doing 'import cv2' on python terminal on yocto's poky it says 'no moudle named cv2'.