Date   

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
 

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@gmail.com 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@siemens.com>
---
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@siemens.com>
---
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@gmail.com 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@gmail.com> 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@nz.abb.com> 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@linuxfoundation.org


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@siemens.com>
---
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


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

Bruce Ashfield
 



On Wed, Nov 25, 2020 at 11:56 AM Andrej Valek <andrej.valek@...> wrote:
- refactor kernel dummy recipe
 - remove unneeded COPYING.GPL file -> change license to close
 - remove unneeded tasks (fetch, unpack, pack)
 - do not run unneeded tasks, but keep deps (configure, compile, install)
 - 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          |  28 +-
 meta/recipes-kernel/linux/linux-dummy/COPYING.GPL | 339 ----------------------
 2 files changed, 12 insertions(+), 355 deletions(-)
 delete mode 100644 meta/recipes-kernel/linux/linux-dummy/COPYING.GPL

diff --git a/meta/recipes-kernel/linux/linux-dummy.bb b/meta/recipes-kernel/linux/linux-dummy.bb
index 62cf6f5ea6..e98a29d5c6 100644
--- a/meta/recipes-kernel/linux/linux-dummy.bb
+++ b/meta/recipes-kernel/linux/linux-dummy.bb
@@ -4,11 +4,12 @@ provider for virtual/kernel to satisfy dependencies for situations \
 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"
+LICENSE = "CLOSED"

 PROVIDES += "virtual/kernel"

+inherit deploy
+
 PACKAGES_DYNAMIC += "^kernel-module-.*"
 PACKAGES_DYNAMIC += "^kernel-image-.*"
 PACKAGES_DYNAMIC += "^kernel-firmware-.*"
@@ -28,17 +29,8 @@ INHIBIT_DEFAULT_DEPS = "1"

 PR = "r1"

-SRC_URI = "file://COPYING.GPL"
 S = "${WORKDIR}"

-do_configure() {
-       :
-}
-
-do_compile () {
-       :
-}
-
 do_compile_kernelmodules() {
     :
 }
@@ -47,10 +39,6 @@ do_shared_workdir () {
        :
 }

-do_install() {
-       :
-}
-
 do_bundle_initramfs() {
        :
 }
@@ -60,6 +48,14 @@ 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
+
+deltask do_fetch
+deltask do_unpack
+deltask do_patch

I wouldn't recommend this in a core recipe, since there may be task dependencies, or someone, somewhere extending those tasks.

If they aren't triggering the problem you are fixing, I'd leave them as-is. If they are the root cause, that's a different story.

Cheers,

Bruce

 
+
+do_configure[noexec] = "1"
+do_compile[noexec] = "1"
+do_install[noexec] = "1"
diff --git a/meta/recipes-kernel/linux/linux-dummy/COPYING.GPL b/meta/recipes-kernel/linux/linux-dummy/COPYING.GPL
deleted file mode 100644
index d511905c16..0000000000
--- a/meta/recipes-kernel/linux/linux-dummy/COPYING.GPL
+++ /dev/null
@@ -1,339 +0,0 @@
-                   GNU GENERAL PUBLIC LICENSE
-                      Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                           Preamble
-
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it.  (Some other Free Software Foundation software is covered by
-the GNU Lesser General Public License instead.)  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
-  To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  You must make sure that they, too, receive or can get the
-source code.  And you must show them these terms so they know their
-rights.
-
-  We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
-  Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary.  To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                   GNU GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-  0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License.  The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language.  (Hereinafter, translation is included without limitation in
-the term "modification".)  Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
-  1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
-  2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-    a) You must cause the modified files to carry prominent notices
-    stating that you changed the files and the date of any change.
-
-    b) You must cause any work that you distribute or publish, that in
-    whole or in part contains or is derived from the Program or any
-    part thereof, to be licensed as a whole at no charge to all third
-    parties under the terms of this License.
-
-    c) If the modified program normally reads commands interactively
-    when run, you must cause it, when started running for such
-    interactive use in the most ordinary way, to print or display an
-    announcement including an appropriate copyright notice and a
-    notice that there is no warranty (or else, saying that you provide
-    a warranty) and that users may redistribute the program under
-    these conditions, and telling the user how to view a copy of this
-    License.  (Exception: if the Program itself is interactive but
-    does not normally print such an announcement, your work based on
-    the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-  3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
-    a) Accompany it with the complete corresponding machine-readable
-    source code, which must be distributed under the terms of Sections
-    1 and 2 above on a medium customarily used for software interchange; or,
-
-    b) Accompany it with a written offer, valid for at least three
-    years, to give any third party, for a charge no more than your
-    cost of physically performing source distribution, a complete
-    machine-readable copy of the corresponding source code, to be
-    distributed under the terms of Sections 1 and 2 above on a medium
-    customarily used for software interchange; or,
-
-    c) Accompany it with the information you received as to the offer
-    to distribute corresponding source code.  (This alternative is
-    allowed only for noncommercial distribution and only if you
-    received the program in object code or executable form with such
-    an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it.  For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable.  However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-  4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License.  Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-  5. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Program or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
-  6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
-  7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-  8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded.  In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-  9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number.  If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation.  If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
-  10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission.  For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this.  Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-                           NO WARRANTY
-
-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-                    END OF TERMS AND CONDITIONS
-
-           How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software; you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation; either version 2 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
-
-    You should have received a copy of the GNU General Public License along
-    with this program; if not, write to the Free Software Foundation, Inc.,
-    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
-    Gnomovision version 69, Copyright (C) year name of author
-    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary.  Here is a sample; alter the names:
-
-  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
-  `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
-  <signature of Ty Coon>, 1 April 1989
-  Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs.  If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.
--
2.11.0






--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


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

 

On Wed, 25 Nov 2020 at 16:56, Andrej Valek <andrej.valek@siemens.com> wrote:

- refactor kernel dummy recipe
- remove unneeded COPYING.GPL file -> change license to close
- remove unneeded tasks (fetch, unpack, pack)
- do not run unneeded tasks, but keep deps (configure, compile, install)
- save files into sstate
- fix: ERROR: Task linux-dummy.do_fetch attempted to execute unexpectedly

Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
---
meta/recipes-kernel/linux/linux-dummy.bb | 28 +-
meta/recipes-kernel/linux/linux-dummy/COPYING.GPL | 339 ----------------------
2 files changed, 12 insertions(+), 355 deletions(-)
delete mode 100644 meta/recipes-kernel/linux/linux-dummy/COPYING.GPL

diff --git a/meta/recipes-kernel/linux/linux-dummy.bb b/meta/recipes-kernel/linux/linux-dummy.bb
index 62cf6f5ea6..e98a29d5c6 100644
--- a/meta/recipes-kernel/linux/linux-dummy.bb
+++ b/meta/recipes-kernel/linux/linux-dummy.bb
@@ -4,11 +4,12 @@ provider for virtual/kernel to satisfy dependencies for situations \
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"
+LICENSE = "CLOSED"
I don't think "CLOSED" is a good choice to use in the core metadata.
The usual way to handle recipes like this which don't require external
source code is to say that they have the same license as the core
metadata itself (MIT) and reference the license text in
"meta/COPYING.MIT". See for example
meta/recipes-bsp/formfactor/formfactor_0.0.bb.

Thanks,

--
Paul Barker
Konsulko Group

1021 - 1040 of 52576