Date   

Re: QA notification for completed autobuilder build (yocto-3.1.4.rc1)

Sangeeta Jain
 

Hi all,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.4.rc1 We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. Beaglebone

ETA for completion is next Tuesday, December 01.

Thanks,
Sangeeta

-----Original Message-----
From: Pokybuild User <pokybuild@...>
Sent: Thursday, 26 November, 2020 12:14 PM
To: yocto@...
Cc: otavio@...; yi.zhao@...; Sangal, Apoorv
<apoorv.sangal@...>; Yeoh, Ee Peng <ee.peng.yeoh@...>;
Chan, Aaron Chun Yew <aaron.chun.yew.chan@...>;
richard.purdie@...; akuster808@...;
sjolley.yp.pm@...; Jain, Sangeeta <sangeeta.jain@...>;
steve@...
Subject: QA notification for completed autobuilder build (yocto-3.1.4.rc1)


A build flagged for QA (yocto-3.1.4.rc1) was completed on the autobuilder
and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.1.4.rc1


Build hash information:

bitbake: 89fc9450abefd682266efcbfa031d1ef115ff1a7
meta-arm: e18ee052f75da60655fb434ff24a463a8fb36781
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 541c7256c1b6acba35d1116a1483b6594d189e3a
meta-kernel: f9d30c65d08c9cef20d6487a7aff0fff40acc823
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
oecore: b885888df67eb5cdb3b82f4f0a07369a449e223b
poky: 424296bf9bb4bae27febf91bce0118df09ce5fa1



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...



Re: U-Boot sama5d3 xplained issue

Federico Pellegrin
 


Hi David,
If you change it directly, changes may not be taken into account for the rebuild. And if the package build gets retriggered, then the whole repository is deleted (including your local changes), redownloaded, repatched and so on. So while it may by chance work by modifying locally in certain conditions, it will most likely not.

I would see two ways:
1) Create a patch that does your changes and add it to the recipe (most likely now in a custom layer) as a patch
2) Fork the repository, add all your customizations there, and point the recipe (again most likely now in a custom layer) to that one.

Cheers,
F.



Il giorno ven 27 nov 2020 alle ore 01:35 David Novak <david.novak@...> ha scritto:

We changed the file directly.

Since it's a custom file, I don't think it is being downloaded. What is the easiest way to determine if it's being downloaded?

Thanks,
David




On 11/23/2020 2:16 AM, Federico Pellegrin wrote:

Hi,
I think it would be interesting information to know "how" you change the value inside "u-boot-at91/sama5d3_xplained_nandflash_config".

As every time you rebuild it may be redownloaded, you should do this via a patch to append to the recipe.

Are you doing this? Or just changing it locally?

If you give some more info probably we can better help!

Cheers,
Federico

Il giorno lun 23 nov 2020 alle ore 08:06 Khem Raj <raj.khem@...> ha scritto:
perhaps asking it on https://github.com/linux4sam/u-boot-at91 via
github issues might be helpful too.

On Sat, Nov 21, 2020 at 4:26 AM David Novak <david.novak@...> wrote:
>
> I'm working on this project with Pratham. Let me provide a few more details.
>
> We've defined
>
> UBOOT_MACHINE ?= "sama5d3_xplained_nandflash_config"
>
> Inside
>
> u-boot-at91/sama5d3_xplained_nandflash_config
>
> we change CONFIG_BOOTDELAY, but it has no effect on the newly built image. The boot delay remains the same as it was before we changed it.
>
> Based on the UBOOT_MACHINE, can we be certain we are changing the correct file?
>
> How do we get the build process to include our changes?
>
> Thanks,
> David
>
>
>
> On 11/19/2020 5:37 PM, Prathamesh Ovalekar wrote:
>
> Hello everyone,
>
> System: sama5d3_xplained board
>
> I have a question regarding the configuration and build of u-boot.
> We have a build that was implemented earlier. I am trying to make some changes to it.
>
> Change 1: Change the auto boot delay to 1 second.
> Change 2: Add an auto boot command to set a gpio.
>
> I am aware of the environment variables:  CONFIG_BOOTDELAY and CONFIG_BOOTCOMMAND (needed for the changes above.)
> I tried modifying the  " configs/sama5d3_xplained_nandflash_defconfig "
>
> Question 1: Do I need to create an *.config file using the make menuconfig?
>
> Question 2: How do I create the u-boot.bin . Does this  depend on the Linux build?
>                     I know that there is an environment variable: CONFIG_BOOTARGS that needs to be populated.
>
> --
> Pratham Ovalekar
>
>
>
>
>
>
>





    




Re: U-Boot sama5d3 xplained issue

David Novak <david.novak@...>
 

We changed the file directly.

Since it's a custom file, I don't think it is being downloaded. What is the easiest way to determine if it's being downloaded?

Thanks,
David




On 11/23/2020 2:16 AM, Federico Pellegrin wrote:

Hi,
I think it would be interesting information to know "how" you change the value inside "u-boot-at91/sama5d3_xplained_nandflash_config".

As every time you rebuild it may be redownloaded, you should do this via a patch to append to the recipe.

Are you doing this? Or just changing it locally?

If you give some more info probably we can better help!

Cheers,
Federico

Il giorno lun 23 nov 2020 alle ore 08:06 Khem Raj <raj.khem@...> ha scritto:
perhaps asking it on https://github.com/linux4sam/u-boot-at91 via
github issues might be helpful too.

On Sat, Nov 21, 2020 at 4:26 AM David Novak <david.novak@...> wrote:
>
> I'm working on this project with Pratham. Let me provide a few more details.
>
> We've defined
>
> UBOOT_MACHINE ?= "sama5d3_xplained_nandflash_config"
>
> Inside
>
> u-boot-at91/sama5d3_xplained_nandflash_config
>
> we change CONFIG_BOOTDELAY, but it has no effect on the newly built image. The boot delay remains the same as it was before we changed it.
>
> Based on the UBOOT_MACHINE, can we be certain we are changing the correct file?
>
> How do we get the build process to include our changes?
>
> Thanks,
> David
>
>
>
> On 11/19/2020 5:37 PM, Prathamesh Ovalekar wrote:
>
> Hello everyone,
>
> System: sama5d3_xplained board
>
> I have a question regarding the configuration and build of u-boot.
> We have a build that was implemented earlier. I am trying to make some changes to it.
>
> Change 1: Change the auto boot delay to 1 second.
> Change 2: Add an auto boot command to set a gpio.
>
> I am aware of the environment variables:  CONFIG_BOOTDELAY and CONFIG_BOOTCOMMAND (needed for the changes above.)
> I tried modifying the  " configs/sama5d3_xplained_nandflash_defconfig "
>
> Question 1: Do I need to create an *.config file using the make menuconfig?
>
> Question 2: How do I create the u-boot.bin . Does this  depend on the Linux build?
>                     I know that there is an environment variable: CONFIG_BOOTARGS that needs to be populated.
>
> --
> Pratham Ovalekar
>
>
>
>
>
>
>







Re: How to Add Packages to Python3

Konrad Weihmann <kweihmann@...>
 

Just add RDEPENDS_${PN] += "python3-json" to the recipe that creates the package, that contains the mentioned python script.

Alternatively add IMAGE_INSTALL += "python3-json" to the image the script is in.

As this is a core module (shipped by python3) the mapping is purely based on the python3-manifest.json

On 26.11.20 12:22, vijayrakeshmunganda@... wrote:
Hi,
I had installed a python file into the rootfs and when I tried to run, it throws an error as "ModuleNotFoundError: No module named 'json'". I tried to find bb file for jsonlib, but I couldn't find at https://layers.openembedded.org/layerindex/branch/master/recipes/?q=python+json. Also some sources suggest to add packages via python3-manifest.json. Kindly please help me in this regard.
Thanks,
VR


Re: [OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks

Andrej Valek <andrej.valek@...>
 

No problem, you can keep the deploy task dependency, like it was.

Regards,
Andrej

On Thu, 2020-11-26 at 14:44 +0000, Valek, Andrej wrote:
No it's not a leftover. I've just copied it from kernel.bbclass, where
this task is written correctly. But you can change it to previous
version I guess.
I'm trying to work out why we need the extra dependencies when the tasks are empty.

I can see how adding the inherit would help, I'm less sure how adding the deploy task after the others does though.

Cheers,

Richard


Re: [OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks

Richard Purdie
 

On Thu, 2020-11-26 at 14:44 +0000, Valek, Andrej wrote:
No it's not a leftover. I've just copied it from kernel.bbclass,
where this task is written correctly. But you can change it to
previous version I guess.
I'm trying to work out why we need the extra dependencies when the
tasks are empty.

I can see how adding the inherit would help, I'm less sure how adding
the deploy task after the others does though.

Cheers,

Richard


Re: [OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks

Andrej Valek <andrej.valek@...>
 

Hello Richard,

No it's not a leftover. I've just copied it from kernel.bbclass, where this task is written correctly. But you can change it to previous version I guess.

Regards,
Andrej

On Wed, 2020-11-25 at 18:20 +0100, Andrej Valek wrote:
- correctly save files into sstate
- fix: ERROR: Task linux-dummy.do_fetch attempted to execute
unexpectedly

Signed-off-by: Andrej Valek <andrej.valek@...>
---
meta/recipes-kernel/linux/linux-dummy.bb | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-dummy.bb b/meta/recipes-
kernel/linux/linux-dummy.bb index 62cf6f5ea6..1498da392c 100644
--- a/meta/recipes-kernel/linux/linux-dummy.bb
+++ b/meta/recipes-kernel/linux/linux-dummy.bb
@@ -5,10 +5,12 @@ where you wish to build the kernel externally from
the build system."
SECTION = "kernel"

LICENSE = "GPLv2"
-LIC_FILES_CHKSUM =
"file://${WORKDIR}/COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"
+LIC_FILES_CHKSUM =
"file://COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"

PROVIDES += "virtual/kernel"

+inherit deploy
+
PACKAGES_DYNAMIC += "^kernel-module-.*"
PACKAGES_DYNAMIC += "^kernel-image-.*"
PACKAGES_DYNAMIC += "^kernel-firmware-.*"
@@ -60,6 +62,6 @@ do_deploy() {
}

addtask bundle_initramfs after do_install before do_deploy -addtask
deploy after do_install
+addtask deploy after do_populate_sysroot do_packagedata
Is this a leftover from the previous version of the patch? We don't normally need those constraints?

Cheers,

Richard


Re: [OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks

Richard Purdie
 

On Wed, 2020-11-25 at 18:20 +0100, Andrej Valek wrote:
- correctly save files into sstate
- fix: ERROR: Task linux-dummy.do_fetch attempted to execute
unexpectedly

Signed-off-by: Andrej Valek <andrej.valek@...>
---
meta/recipes-kernel/linux/linux-dummy.bb | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-dummy.bb b/meta/recipes-
kernel/linux/linux-dummy.bb
index 62cf6f5ea6..1498da392c 100644
--- a/meta/recipes-kernel/linux/linux-dummy.bb
+++ b/meta/recipes-kernel/linux/linux-dummy.bb
@@ -5,10 +5,12 @@ where you wish to build the kernel externally from
the build system."
SECTION = "kernel"

LICENSE = "GPLv2"
-LIC_FILES_CHKSUM =
"file://${WORKDIR}/COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"
+LIC_FILES_CHKSUM =
"file://COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"

PROVIDES += "virtual/kernel"

+inherit deploy
+
PACKAGES_DYNAMIC += "^kernel-module-.*"
PACKAGES_DYNAMIC += "^kernel-image-.*"
PACKAGES_DYNAMIC += "^kernel-firmware-.*"
@@ -60,6 +62,6 @@ do_deploy() {
}

addtask bundle_initramfs after do_install before do_deploy
-addtask deploy after do_install
+addtask deploy after do_populate_sysroot do_packagedata
Is this a leftover from the previous version of the patch? We don't
normally need those constraints?

Cheers,

Richard


Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

aloofbynature@...
 

Thanks for the quick response. I started out with a fresh clone of poky and only executed 2 commands:
1) 'source poky-yocto-3.2/oe-init-build-env'
2) in my build directory 'bitbake core-image-minimal'

The output from the console is:
aloof@LAPTOP-AQOIU06O:~/projects/yocto-test$ source poky-yocto-3.2/oe-init-build-env
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to, for
example, select a different MACHINE (target hardware). See conf/local.conf
for more information as common configuration options are commented.

You had no conf/bblayers.conf file. This configuration file has therefore been
created for you with some default values. To add additional metadata layers
into your configuration please add entries to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE including a reference
manual which can be found at:
    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
    http://www.openembedded.org/


### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'

Other commonly useful commands are:
 - 'devtool' and 'recipetool' handle common recipe tasks
 - 'bitbake-layers' handles common layer tasks
 - 'oe-pkgdata-util' handles common target package tasks
aloof@LAPTOP-AQOIU06O:~/projects/yocto-test/build$ bitbake core-image-minimal
WARNING: You are running bitbake under WSLv2, this works properly but you should optimize your VHDX file eventually to avoid running out of storage space
Loading cache: 100% |                                                                                   | ETA:  --:--:--Loaded 0 entries from dependency cache.
Parsing recipes: 100% |##################################################################################| Time: 0:00:15Parsing of 784 .bb files complete (0 cached, 784 parsed). 1353 targets, 42 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.48.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-20.04"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "qemux86-64"
DISTRO               = "poky"
DISTRO_VERSION       = "3.2"
TUNE_FEATURES        = "m64 core2"
TARGET_FPU           = ""
meta
meta-poky
meta-yocto-bsp       = "<unknown>:<unknown>"

NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/2.9/x86_64-nativesdk-libc.tar.xz;sha256sum=d07916b95c419c81541a19c8ef0ed8cbd78ae18437ff28a4c8a60ef40518e423 (will check PREMIRRORS first)
Initialising tasks: 100% |###############################################################################| Time: 0:00:02Sstate summary: Wanted 1279 Found 0 Missed 1279 Current 0 (0% match, 0% complete)
NOTE: Executing Tasks
ERROR: Task (/home/aloof/projects/yocto-test/poky-yocto-3.2/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.8.bb:do_install) failed with exit code '134'
NOTE: Tasks Summary: Attempted 793 tasks of which 0 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/aloof/projects/yocto-test/poky-yocto-3.2/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.8.bb:do_install
Summary: There was 1 WARNING message shown.

I'm not sure which log file. I'm attaching the one I found in the tmp directory. Is there a specific location you can point me to if this isn't the right log.

Thanks,
Ajay


Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

Quentin Schulz
 

Hi,

On Thu, Nov 26, 2020 at 04:26:34AM -0800, aloofbynature@... wrote:
Hello,

I am just starting using Yocto Project and I've been following along with the getting started section of the mega manual. I am working on Ubuntu 20.04 LTS through WSL2 on Windows 10 (not sure if it matters but I'm running OS build 20231) trying to create an image using poky-yocto-3.2.

I've followed all setup steps and made sure the host has all necessary packages before cloning poky (I kept running into an error when trying to clone the repo because the connection was refused so I just extracted the poky-yocto-3.2 tarball). When I try to run 'bitbake core-image-minimal' I get an error saying the following task failed with exit code 134:
'poky-yocto-3.2/meta/recipes- kernel/linux-libc-headers/ linux-libc-headers_5.8.bb:do_ install'
All the other recipes are installed with no problems.
To be able to help you we'd need the logs of this task.
You can either paste the whole output on the console or send us the task
log you can find if you carefully read the console output.

Quentin


Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

 

On Thu, 26 Nov 2020 at 12:26, <aloofbynature@...> wrote:

Hello,

I am just starting using Yocto Project and I've been following along with the getting started section of the mega manual. I am working on Ubuntu 20.04 LTS through WSL2 on Windows 10 (not sure if it matters but I'm running OS build 20231) trying to create an image using poky-yocto-3.2.

I've followed all setup steps and made sure the host has all necessary packages before cloning poky (I kept running into an error when trying to clone the repo because the connection was refused so I just extracted the poky-yocto-3.2 tarball). When I try to run 'bitbake core-image-minimal' I get an error saying the following task failed with exit code 134:
'poky-yocto-3.2/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.8.bb:do_install'
All the other recipes are installed with no problems.

The first time I tried this I changed local.conf in my build dir to build for qemuarm and next try I left everything as the default configuration but still got the same result. Any help fixing this issue is appreciated, thanks!
Could you share the command that you executed along with the full
output that was printed? There's not really enough information here to
diagnose the issue.

Thanks,

--
Paul Barker
Konsulko Group


Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

aloofbynature@...
 

Hello,
 
I am just starting using Yocto Project and I've been following along with the getting started section of the mega manual. I am working on Ubuntu 20.04 LTS through WSL2 on Windows 10 (not sure if it matters but I'm running OS build 20231) trying to create an image using poky-yocto-3.2.
 
I've followed all setup steps and made sure the host has all necessary packages before cloning poky (I kept running into an error when trying to clone the repo because the connection was refused so I just extracted the poky-yocto-3.2 tarball). When I try to run 'bitbake core-image-minimal' I get an error saying the following task failed with exit code 134:
'poky-yocto-3.2/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.8.bb:do_install'
All the other recipes are installed with no problems.
 
The first time I tried this I changed local.conf in my build dir to build for qemuarm and next try I left everything as the default configuration but still got the same result. Any help fixing this issue is appreciated, thanks!


How to Add Packages to Python3

Vijay Rakesh Munganda
 

Hi,

I had installed a python file into the rootfs and when I tried to run, it throws an error as "ModuleNotFoundError: No module named 'json'". I tried to find bb file for jsonlib, but I couldn't find at https://layers.openembedded.org/layerindex/branch/master/recipes/?q=python+json. Also some sources suggest to add packages via python3-manifest.json. Kindly please help me in this regard.

Thanks,
VR


Re: Use of USERADD_PACKAGES with out recipe package files

 

On Thu, 26 Nov 2020 at 03:21, <andrew.loader@...> wrote:

I have for an image append which I would like to add some users to but I do not want to add any files as part of the package
so I have a layer which contains a recipe called user-config-0.1.bb which has a useradd package USERADD_PACKAGES = " ${PN}-user-sys " . then I have a USERADD_PARAM_${PN}-user-sys = " .."
which adds some users not shown and I also have an add group param as well not shown
I declare the package as PACKAGES += "${PN}-user-sys" but do not set the package files because i do not want any
and in my image bbappend file I install the package IMAGE_INSTALL_append += "user-config-user-sys"
The recipe builds but does not create a package and the do-rootfs cannot find the package and fails with

No match for argument: user-config-user-sys
Error: Unable to find a match

well that seems to be the meaningful part I guess

How do i get yocto to generate a package which only contains user group creation part which can then be installed in my image
I have added uses and groups before with files with out a problem, also this is greatly simplified but still shows the core problem
You probably need to set `ALLOW_EMPTY_${PN}-user-sys`. See
https://docs.yoctoproject.org/ref-manual/ref-variables.html?highlight=allow_empty#term-ALLOW_EMPTY.

Thanks,

--
Paul Barker
Konsulko Group


QA notification for completed autobuilder build (yocto-3.1.4.rc1)

pokybuild@...
 

A build flagged for QA (yocto-3.1.4.rc1) was completed on the autobuilder and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.1.4.rc1


Build hash information:

bitbake: 89fc9450abefd682266efcbfa031d1ef115ff1a7
meta-arm: e18ee052f75da60655fb434ff24a463a8fb36781
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 541c7256c1b6acba35d1116a1483b6594d189e3a
meta-kernel: f9d30c65d08c9cef20d6487a7aff0fff40acc823
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
oecore: b885888df67eb5cdb3b82f4f0a07369a449e223b
poky: 424296bf9bb4bae27febf91bce0118df09ce5fa1



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...


Use of USERADD_PACKAGES with out recipe package files

Andrew Loader
 

I have for an image append which I would like to add some users to but I do not want to add any files as part of the package
so I  have a layer which contains a recipe called user-config-0.1.bb which has a useradd package USERADD_PACKAGES = " ${PN}-user-sys "  . then I have a USERADD_PARAM_${PN}-user-sys = " .."
which adds some users not shown and I also have an add group param as well not shown
I declare the package as  PACKAGES += "${PN}-user-sys" but do not set the package files because i do not want any 
and in my image bbappend file I install the package  IMAGE_INSTALL_append += "user-config-user-sys" 
The recipe builds but does not create a package and the do-rootfs cannot find the package  and fails with

No match for argument: user-config-user-sys
Error: Unable to find a match

well that seems to be the meaningful part I guess

How do i get yocto to generate a package which only contains user group creation part which can then be installed in my image
I have added uses and groups before with files with out a problem, also this is greatly simplified but still shows the core problem 


Re: [OE-core] OpenEmbedded Happy Hour November 25 9pm/2100 UTC

Denys Dmytriyenko
 

Just a reminder, Happy Hour is in 1 hour.

9pm UTC, 4pm EST (not EDT) or use time conversion link below for your
location. See you there!

--
Denys

On Thu, Nov 19, 2020 at 01:12:35PM -0500, Denys Dmytriyenko wrote:
Hi,

Just a reminder about our upcoming OpenEmbedded Happy Hour on November 25 for
Oceania/Asia timezones @ 2100/9pm UTC (4pm EDT):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+November+25&iso=20201125T21

--
Denys


Re: Parsing recipes: 0% | - hangs for a while

Khem Raj
 

On 11/25/20 3:13 AM, Sergey Ivanov wrote:
Since today i encountered issue in the topic.
I had this issue before when i forgot to turn on vpn (somehow parsing depends on it). But today is everything is OK and i wonder what went wrong. More precisely, i'm interested in two points:
1) at which stage parsing of receipts is interested in remote resources?
2) how to disable remote resource usage during parsing in some sophisticated way?
perhaps you can try setting BB_NO_NETWORK = "1" in your local.conf and perhaps disabling local mirrors would be needed too if you have then enabled

P.S. after waiting for a while bitbake continues but it is annoying anyway.
--
Kind regards,
Sergey Ivanov


Re: Problem with recipe that depends on a binary that is generated during its build

Khem Raj
 

On 11/25/20 12:37 AM, Matteo Iervasi wrote:
Ok I've found a solution by myself. Basically I just used the trick showed in the Technical FAQ and put a bunch of install commands in the do_install task.
Now the only problem I have is that the do_install task for target complains that needs administrative privileges (maybe I'm just doing it wrong, I'm still not that experienced with Yocto).
| [100%] Built target boosttest-test-livestatus
| make[1]: Leaving directory '/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build'
| /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/recipe-sysroot-native/usr/bin/cmake -E cmake_progress_start /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build/CMakeFiles 0
| make -f CMakeFiles/Makefile2 preinstall
| make[1]: Entering directory '/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build'
| make[1]: Nothing to be done for 'preinstall'.
| make[1]: Leaving directory '/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build'
| Install the project...
| /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/recipe-sysroot-native/usr/bin/cmake -P cmake_install.cmake
| -- Install configuration: "Release"
| CMake Error at cmake_install.cmake:36 (file):
|   file cannot create directory: /usr/share/doc/icinga2.  Maybe need
|   administrative privileges.
|
this just means that its not able to relocate the install location to ${D} which is what default do_install should do. So the package needs some work to respect an option to relocate the installation directory once you have that then you can specify that vi OE_EXTRACMAKE += "-D...=${D}" or some such. That could be a fix sent to upstream as well otherwise your fix it ok too for your needs.

|
| Makefile:74: recipe for target 'install' failed
| make: *** [install] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_install (log file is located at /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/temp/log.do_install.25788)
ERROR: Task (/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/../layers/meta-boxio-colibri-imx6ull/recipes-extended/icinga-core/icinga-core_2.12.0.bb:do_install) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3457 tasks of which 3447 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
The recipe that now compiles ok is attached here.
Thanks
Matteo Iervasi


[OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks

Andrej Valek <andrej.valek@...>
 

- correctly save files into sstate
- fix: ERROR: Task linux-dummy.do_fetch attempted to execute unexpectedly

Signed-off-by: Andrej Valek <andrej.valek@...>
---
meta/recipes-kernel/linux/linux-dummy.bb | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-dummy.bb b/meta/recipes-kernel/linux/linux-dummy.bb
index 62cf6f5ea6..1498da392c 100644
--- a/meta/recipes-kernel/linux/linux-dummy.bb
+++ b/meta/recipes-kernel/linux/linux-dummy.bb
@@ -5,10 +5,12 @@ where you wish to build the kernel externally from the build system."
SECTION = "kernel"

LICENSE = "GPLv2"
-LIC_FILES_CHKSUM = "file://${WORKDIR}/COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"
+LIC_FILES_CHKSUM = "file://COPYING.GPL;md5=751419260aa954499f7abaabaa882bbe"

PROVIDES += "virtual/kernel"

+inherit deploy
+
PACKAGES_DYNAMIC += "^kernel-module-.*"
PACKAGES_DYNAMIC += "^kernel-image-.*"
PACKAGES_DYNAMIC += "^kernel-firmware-.*"
@@ -60,6 +62,6 @@ do_deploy() {
}

addtask bundle_initramfs after do_install before do_deploy
-addtask deploy after do_install
+addtask deploy after do_populate_sysroot do_packagedata
addtask shared_workdir after do_compile before do_install
addtask compile_kernelmodules
--
2.11.0

5841 - 5860 of 57398