Date   

Enhancements/Bugs closed WW26!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

timothy.t.orling@...

17

randy.macleod@...

5

akuster808@...

4

richard.purdie@...

4

david.reyna@...

2

JPEWhacker@...

1

bluelightning@...

1

jpuhlman@...

1

ricardo.ribalda@...

1

Grand Total

36

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: Dunfell 3.1.1 gcc-sanitizers build failure

Khem Raj
 

On 6/30/20 2:56 PM, MikeB wrote:
I recently tried upgrading from 3.1.0 to 3.1.1.  I'm not sure if this is a bug or just my problem.  I maintain five different architectures and all five have the same failure in gcc-sanitizers as I'm trying to build the SDK.
| cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
| WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'
| ERROR: Execution of '/data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505' failed with exit code 1:
| cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
| WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'
At first, I thought this may be a dependency issue because I inherit "rm_work" to tidy up; but I tried a build without it - i.e. keeping all work around - and got the same failure.
I've attached the full error log.  Any troubleshooting advice would be appreciated.
try to do a bitbake -ccleansstate on gcc-source-9.3.0


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 342 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.1”, “3.2, "3.99" and "Future", the more pressing/urgent issues being in "3.1" and then “3.2”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.2

Stephen Jolley
 

All,

Below is the list as of top 38 bug owners as of the end of WW26 of who have open medium or higher bugs and enhancements against YP 3.2.   There are 86 possible work days left until the final release candidates for YP 3.2 needs to be released.

Who

Count

david.reyna@...

10

mark.morton@...

9

bluelightning@...

7

ross@...

7

richard.purdie@...

6

Qi.Chen@...

5

michael@...

5

jon.mason@...

3

yi.zhao@...

3

raj.khem@...

3

rpjday@...

3

trevor.gamblin@...

2

alejandro@...

2

ycnakajsph@...

2

kai.kang@...

2

sakib.sajal@...

2

dl9pf@...

2

mark.hatle@...

2

randy.macleod@...

2

mostthingsweb@...

2

timothy.t.orling@...

2

JPEWhacker@...

2

chee.yang.lee@...

2

kergoth@...

2

jaewon@...

2

matthew.zeng@...

1

bruce.ashfield@...

1

hongxu.jia@...

1

Martin.Jansa@...

1

maxime.roussinbelanger@...

1

bunk@...

1

naveen.kumar.saini@...

1

kai.ruhnau@...

1

liu.ming50@...

1

limon.anibal@...

1

denis@...

1

jpuhlman@...

1

changqing.li@...

1

Grand Total

102

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Dunfell 3.1.1 gcc-sanitizers build failure

MikeB
 

I recently tried upgrading from 3.1.0 to 3.1.1.  I'm not sure if this is a bug or just my problem.  I maintain five different architectures and all five have the same failure in gcc-sanitizers as I'm trying to build the SDK.

| cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
| WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'
| ERROR: Execution of '/data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505' failed with exit code 1:
| cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
| WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'
 
At first, I thought this may be a dependency issue because I inherit "rm_work" to tidy up; but I tried a build without it - i.e. keeping all work around - and got the same failure.

I've attached the full error log.  Any troubleshooting advice would be appreciated.


Re: INCOMPATIBLE_LICENSE - how to use it properly?

Khem Raj
 

On 6/30/20 3:07 AM, Mikko Rapeli wrote:
Hi,
On Tue, Jun 30, 2020 at 09:34:39AM +0000, John Ernberg wrote:
Hi,

I have been trying to use INCOMPATIBLE_LICENSE to filter out undesirable
licenses for us from our images. I started simple and picked the
examples from the manual (AGPL-3.0, GPL-3.0 and LGPL-3.0).

Currently we're based on Warrior, but I also did a short test on master
(results later in the message)

Our images use systemd as init system. We use busybox ash as shell on
these images for now.

When setting the INCOMPATIBLE_LICENSE according to the manual example,
systemd cannot be built anymore because bash is being skipped due to
license.

Turns out that because systemd-bash-completion and
systemd-kernel-install both rdepend on bash, we can't build systemd at
all, because bash is not buildable. Even if we're not installing those
features of systemd.

A dive into TaskData suggests that all the rdepends of all packages
provided by a recipe are flattened into depends of the recipe when
testing buildability.

A quick test on master from about 2 weeks ago show the same behavior.

For the test on master all I did was change the DISTRO_FEATURES of
core-image-minimal to include systemd.


Am I using ICOMPATIBLE_LICENSE properly so far?
If so, is being unable to fulfill an rdepend for an unused package meant
to fail the whole build, and how can I avoid it short of including
meta-gplv2 or writing lots of .bbappends to remove the dependencies?
Otherwise, where did I go wrong, and what should I be trying instead?
You need to add exceptions to build a lot GPLv3 components but not let them
be part of product images.
In distro config:
INCOMPATIBLE_LICENSE += "GPLv3 GPLv3+ LGPLv3 LGPLv3+"
...
WHITELIST_GPL-3.0 += "bash"
PACKAGE_EXCLUDE += "bash-ptest bash-dbg bash-staticdev bash-dev bash-doc bash-locale bashbug bash"
...
The PACKAGE_EXCLUDE must be complete list of binary packages produced by the recipe.

I think having two different distro configs is a reliable approach here, we keep adding more refined packaging which means you have to be on your toes all the time in the allowed list above.

I end up enabling a large set of GPLv3 tools for use as development tooling at build
time or in SDK:
$ grep WHITELIST_ distro.conf
WHITELIST_GPL-3.0 += "autoconf"
WHITELIST_GPL-3.0 += "bash"
WHITELIST_GPL-3.0 += "bc"
WHITELIST_GPL-3.0 += "binutils"
WHITELIST_GPL-3.0 += "bison"
WHITELIST_GPL-3.0 += "ccache"
WHITELIST_GPL-3.0 += "coreutils"
WHITELIST_GPL-3.0 += "diffutils"
WHITELIST_GPL-3.0 += "elfutils"
WHITELIST_GPL-3.0 += "findutils"
WHITELIST_GPL-3.0 += "gawk"
WHITELIST_GPL-3.0 += "gdb"
WHITELIST_GPL-3.0 += "gdbm"
WHITELIST_GPL-3.0 += "gettext"
WHITELIST_GPL-3.0 += "gnutls"
WHITELIST_GPL-3.0 += "grep"
WHITELIST_GPL-3.0 += "libevent"
WHITELIST_GPL-3.0 += "libpipeline"
WHITELIST_GPL-3.0 += "libunistring"
WHITELIST_GPL-3.0 += "m4"
WHITELIST_GPL-3.0 += "make"
WHITELIST_GPL-3.0 += "readline"
WHITELIST_GPL-3.0 += "rsync"
WHITELIST_GPL-3.0 += "sed"
WHITELIST_GPL-3.0 += "which"
If one does not do this, alternative is to use a bunch of old and deprecated tool
versions from meta-gplv2.
Hope this helps,
-Mikko


Re: Errors Building openjdk-8 on dunfell

Khem Raj
 

On 6/29/20 10:13 PM, Robert Joslyn wrote:
I'm trying to build openjdk-8 on dunfull and am getting some build errors.
Using an Ubuntu 18.04 host, I get an error building the openjdk-8 recipe:
| g++: error: unrecognized command line option ‘-fmacro-prefix-
map=/mnt/yocto/bionic/poky/build/tmp/work/core2-64-poky-linux/openjdk-
8/252-r0=/usr/src/debug/openjdk-8/252-r0’
This seems to imply I need a newer gcc which supports the -fmacro-prefix-
map option. The README says I need gcc 6 or later on the host, but 18.04
has gcc 7.5.0. Maybe the README is outdated?
I then tried building in an Ubuntu 20.04 container to see if that makes
any difference. It fails in a different way while building icedtea7-
native:
| /usr/include/x86_64-linux-gnu/bits/stdio2.h:100:24: error: ‘%s’
directive argument is null [-Werror=format-overflow=]
I guess compiler on your host is too new for openjdk-8, perhaps you might get through by disabling Werror option to host cflags. You might have to dig the appropriate place to stick the option in.

I'm doing clean builds with both my 18.04 and 20.04 setups starting with
separate, empty sstate-cache directories. Both builds are using poky
defaults:
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.1.1"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "dunfell:93ef4736915090ac9a2402916df8924ac4439490"
meta-oe = "dunfell:8a72d29e0876830ffd96b85d7d0308302eb07a5d"
meta-java = "dunfell:cf9604a4789801d9dfb0cb8ca134ff04b42ae161"
Is there some trick I'm missing to get clean builds out of the box? I can
fix the 20.04 build by adding -Wno-error for that specific warning (and
can send a patch if desired), but has anyone else had these issues? Any
thoughts would be appreciated.
Thanks,
Robert


[meta-mingw][PATCH] mingw-w64: Upgrade to 7.0.0

Joshua Watt
 

Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
recipes-devtools/mingw-w64/mingw-w64.inc | 3 +--
...-headers_6.0.0.bb => nativesdk-mingw-w64-headers_7.0.0.bb} | 4 ----
...-runtime_6.0.0.bb => nativesdk-mingw-w64-runtime_7.0.0.bb} | 0
...eads_6.0.0.bb => nativesdk-mingw-w64-winpthreads_7.0.0.bb} | 0
4 files changed, 1 insertion(+), 6 deletions(-)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-headers_6.0.0.bb => nativesdk-mingw-w64-headers_7.0.0.bb} (82%)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-runtime_6.0.0.bb => nativesdk-mingw-w64-runtime_7.0.0.bb} (100%)
rename recipes-devtools/mingw-w64/{nativesdk-mingw-w64-winpthreads_6.0.0.bb => nativesdk-mingw-w64-winpthreads_7.0.0.bb} (100%)

diff --git a/recipes-devtools/mingw-w64/mingw-w64.inc b/recipes-devtools/mingw-w64/mingw-w64.inc
index 8c68bcc..a435dea 100644
--- a/recipes-devtools/mingw-w64/mingw-w64.inc
+++ b/recipes-devtools/mingw-w64/mingw-w64.inc
@@ -5,8 +5,7 @@ COMPATIBLE_HOST = ".*-mingw.*"

SRC_URI = "${SOURCEFORGE_MIRROR}/project/mingw-w64/mingw-w64/mingw-w64-release/mingw-w64-v${PV}.tar.bz2"

-SRC_URI[md5sum] = "cf5673f6d689bb5e02863e6284cc3d03"
-SRC_URI[sha256sum] = "805e11101e26d7897fce7d49cbb140d7bac15f3e085a91e0001e80b2adaf48f0"
+SRC_URI[sha256sum] = "aa20dfff3596f08a7f427aab74315a6cb80c2b086b4a107ed35af02f9496b628"

UPSTREAM_CHECK_URI = "http://sourceforge.net/projects/mingw-w64/files/mingw-w64/mingw-w64-release/"
UPSTREAM_CHECK_REGEX = "mingw-w64-v(?P<pver>(\d+[\.\-_]*)+)\.tar"
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_6.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_7.0.0.bb
similarity index 82%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_6.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_7.0.0.bb
index 58073d6..292d22b 100644
--- a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_6.0.0.bb
+++ b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-headers_7.0.0.bb
@@ -10,10 +10,6 @@ inherit autotools nativesdk
INHIBIT_DEFAULT_DEPS = "1"
DEPENDS = ""

-PACKAGECONFIG ??= "secure-api"
-
-PACKAGECONFIG[secure-api] = "--enable-secure-api,--disable-secure-api"
-
do_configure() {
oe_runconf
}
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_6.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
similarity index 100%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_6.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_7.0.0.bb
diff --git a/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_6.0.0.bb b/recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_7.0.0.bb
similarity index 100%
rename from recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_6.0.0.bb
rename to recipes-devtools/mingw-w64/nativesdk-mingw-w64-winpthreads_7.0.0.bb
--
2.27.0


[PATCH yocto-autobuilder-helper] config.json: add meta-arm

Ross Burton
 

From: Ross Burton <ross.burton@arm.com>

This builds a small number of images for the N1 SDP and Juno boards.

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
config.json | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)

diff --git a/config.json b/config.json
index b810373..8823c32 100644
--- a/config.json
+++ b/config.json
@@ -273,6 +273,24 @@
"MACHINE" : "qemuarm64",
"TEMPLATE" : "ltp-qemu"
},
+ "meta-arm" : {
+ "NEEDREPOS" : ["poky", "meta-arm"],
+ "ADDLAYER" : [
+ "${BUILDDIR}/../meta-arm/meta-arm",
+ "${BUILDDIR}/../meta-arm/meta-arm-bsp",
+ "${BUILDDIR}/../meta-arm/meta-arm-toolchain"
+ ],
+ "step1": {
+ "MACHINE": "n1sdp",
+ "BBTARGETS": "core-image-minimal core-image-sato core-image-sato:do_populate_sdk",
+ "SANITYTARGETS" : "core-image-sato:do_testsdk"
+ },
+ "step2": {
+ "MACHINE": "juno",
+ "BBTARGETS": "core-image-minimal core-image-sato core-image-sato:do_populate_sdk",
+ "SANITYTARGETS" : "core-image-sato:do_testsdk"
+ }
+ },
"bringup" : {
"BUILDINFO" : true,
"SSTATEDIR" : ["SSTATE_DIR ?= '${HELPERBUILDDIR}/sstate'"],
@@ -964,6 +982,12 @@
"branch" : "master",
"revision" : "HEAD",
"no-layer-add" : true
+ },
+ "meta-arm" : {
+ "url" : "git://git.yoctoproject.org/meta-arm",
+ "branch" : "master",
+ "revision" : "HEAD",
+ "no-layer-add" : true
}

},
--
2.24.3 (Apple Git-128)


Re: #yocto #python #python #yocto

Khem Raj
 

On 6/26/20 4:15 AM, valentin.duee@weidmueller.com wrote:
Hi,
if I try to add a layer like this:
bitbake-layers add-layer ../layers/meta-openembedded/meta-oe
(also for other layers)
I get following error:
The following required tools (as specified by HOSTTOOLS) appear to be unavailable in PATH, please install them in order to proceed:
  python
But I do have installed python in all possible versions. I don't know what to do currently and would appreciate your help a lot. Thanks in Advance.
which release of yocto are you on ? secondly which OS is on the host?
you might want to install python2 perhaps on it.

BR


Yocto Project Status WW26'20

Stephen Jolley
 

Current Dev Position: YP 3.2 M2

Next Deadline: YP 3.2 M2 build date 2020/7/27

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.2 M1 was released.
  • We’ve updated to a new version of the buildtools tarball for master and dunfell
  • We continue to be concerned about autobuilder stability, we’re continuing to see high numbers of intermittent failures. You can see the list of failures we’re seeing by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

Help is urgently needed to bring these to a manageable level.

  • We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
  • If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area.
  • It is ELC this week, please stop by the booth and/or ELC #2-track-yocto-project slack channel and say hi. There are still places available on our virtual Developer Day: https://events.linuxfoundation.org/yocto-dev-day-north-america/
  • Another way to help the project is to help us with bugs that are currently unassigned but ideally needed during 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • We’re pleased to announce we have a new manual in the Yocto Project documentation ‘bookshelf’ which covers the project’s testing processes and infrastructure including the autobuilder and resulttool. A work-in-progress version of this can be viewed here: https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html. So far, it contains basic information in key areas, we’re happy to take feedback on areas that are missing or need more information and/or take contributions to further extend this work.

 

YP 3.2 Milestone Dates:

  • YP 3.2 M1 is released.
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

 

Planned upcoming dot releases:

  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: Need help understanding #devtool flow to library #devtool

Quentin Schulz
 

Hi Stephan,

On Tue, Jun 30, 2020 at 04:26:01AM -0700, tobies@synopsys.com wrote:
Hello!

I am new to yocto, so I might be missing something obvious, but I have trouble getting the devtool flow to work for me. It seems that the library that ends up in the image is not the one with my modifications but instead the altered one.

Here is what I have done:

devtool modify <libname>

This has successfully checked out the sources of the library that I want to modify and I could make my modifications and build the changed version with "devtool build vsomeip" . Now when I build an image with "devtool build-image <img-name>", devtool reports that it would build the image with addtional package "vsomeip".

But the library that ends up in the generated image does not seem to have the modified code. I do not find my additional symbols when I do an objdump on the library in

./tmp/work/qemux86-poky-linux/<img-name>/1.0-r0/rootfs/usr/lib/libvsomeip...

On the other hand, the library built in ./tmp/work/i586-poky-linux/vsomeip/2.10.21-r0/vsomeip-2.10.21/libvsomeip.so.2.10.21 does have these symbols.

The disconnect seems to happen already within the vsomeip library build process. The library present at ./tmp/work/i586-poky-linux/vsomeip/2.10.21-r0/package/usr/lib/libvsomeip.so.2.10.21 is one _without_ my changes present (and identical in size to the one on the rootfs folder of the image).

It feels like I am missing a step of the devtool flow, or at least the starting point to debug the deployment process.

Any hints of pointers to relevant documentation would be very appreciated!
Libraries and binaries are stripped of the debug symbols before adding
them to the "normal" package. The version with the debug symbols are
usually in the -dbg package of your recipe.

You can disable this behavior with INHIBIT_PACKAGE_STRIP in your recipe (c.f.
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-INHIBIT_PACKAGE_STRIP)

This is Yocto's default behavior, not sure if there is anything specific
to devtool in what you described.

(BTW, until you have run devtool reset <recipe>, bitbake takes the
sources from your devtool workspace. I don't know exactly what's the
difference with bitbake build-image <img-name> and bitbake <img-name>)

Let us know if that helps,
Quentin


Re: License reporting for golang (and rust)

Irving ST
 

Hi,

For anyone else having the same problem, here's what I eventually did
for my go stuff:

I created a bbclass containing a task that gets inherited by all
packages, but the task only does some work when it detects that it is
inherited by a golang recipe.
The task basically sets up GOPATH and calls
https://github.com/rancher/trash - this tool populates all the source
dependencies and generate a trash.lock file in the repository.
Then I used https://github.com/pivotal/LicenseFinder to generate a
json report that can be postprocessed with python.

To me it seems that Go used the vendor directory approach in the past,
and there are multiple tools that can be used for this; and nowadays
go seems to have switched to a different approach called go modules.
With this multiple tools and methods of managing dependencies, I am
not sure whether it is feasible to integrate this in Yocto at all -
though I think I have seen mailing list posts on meta-virtualization
adding vendor information to their recipes, so maybe some progress is
happening there.

Best regards,
Irving Tjiptowarsono

On Tue, Jun 30, 2020 at 7:32 AM Robert Berger@yocto.user
<robert.berger.yocto.user@gmail.com> wrote:

Hi,

My comments are in-line

On 22/06/2020 11:53, Irving ST wrote:
Hello,

I am building a device that uses some Go (and Rust) dependencies. This
is on Yocto 2.7 / Warrior.

I noticed that after building an image, the generated license.manifest
and package.manifest (in tmp/deploy/licenses/) does not contain any
mention of go packages or rust crates. The go packages seem to
generate directories in tmp/deploy/licenses/ but they do not seem to
be reported in the final image.
On dunfell 3.1.1 I see this:

licenses/
└── github.com-influxdata-influxdb
├── generic_MIT
├── LICENSE
└── recipeinfo

which is wrong, since I would need to add all the licenses of all the
dependencies golang pulls in as well to the recipe. It's shows only the
top level license.

In my license manifest I do have the influxdb:

tmp/deploy/licenses/image-influxdb-from-source-container-x86-64-20200629205620/license.manifest

PACKAGE NAME: github.com-influxdata-influxdb
PACKAGE VERSION: 1.8.0
RECIPE NAME: github.com-influxdata-influxdb
LICENSE: MIT

Regards,

Robert



Need help understanding #devtool flow to library #devtool

tobies@...
 

Hello!

I am new to yocto, so I might be missing something obvious, but I have trouble getting the devtool flow to work for me. It seems that the library that ends up in the image is not the one with my modifications but instead the altered one. 

Here is what I have done:

devtool modify <libname>

This has successfully checked out the sources of the library that I want to modify and I could make my modifications and build the changed version with "devtool build vsomeip" . Now when I build an image with "devtool build-image <img-name>", devtool reports that it would build the image with addtional package "vsomeip".

But the library that ends up in the generated image does not seem to have the modified code. I do not find my additional symbols when I do an objdump on the library in 

./tmp/work/qemux86-poky-linux/<img-name>/1.0-r0/rootfs/usr/lib/libvsomeip...

On the other hand, the library built in ./tmp/work/i586-poky-linux/vsomeip/2.10.21-r0/vsomeip-2.10.21/libvsomeip.so.2.10.21 does have these symbols.

The disconnect seems to happen already within the vsomeip library build process. The library present at ./tmp/work/i586-poky-linux/vsomeip/2.10.21-r0/package/usr/lib/libvsomeip.so.2.10.21 is one _without_ my changes present (and identical in size to the one on the rootfs folder of the image).

It feels like I am missing a step of the devtool flow, or at least the starting point to debug the deployment process.

Any hints of pointers to relevant documentation would be very appreciated!

Thanks a lot!

Stephan


Re: INCOMPATIBLE_LICENSE - how to use it properly?

Alexander Kanavin
 

It goes over a list of packages installed into their image, and checks their licensing. If something was directly built into something else, it will not produce a separate package, and therefore you need to handle that separately: perhaps by setting the package license appropriately in respective recipes (they needs to carry the licenses of items coming directly as headers from other recipes).

Alex


On Tue, 30 Jun 2020 at 12:01, John Ernberg <john.ernberg@...> wrote:
Hi Alex,

I will give this a try on master.

One question though, will this still catch build-only libraries? (i.e. a
library that consists only of headers). I don't think we have such
recipes right now, it's more to understand how this feature works.

Thank you.

Best regards // John Ernberg

On 6/30/20 11:55 AM, Alexander Kanavin wrote:
> On master, you can set INCOMPATIBLE_LICENSE in the image recipe, rather
> than globally, then the check would only be performed on items that
> actually go into that image.
>
> Warrior does not have that feature yet, I think, so your only option
> there is meta-gpl2.
>
> Alex
>
> On Tue, 30 Jun 2020 at 11:34, John Ernberg <john.ernberg@...
> <mailto:john.ernberg@...>> wrote:
>
>     Hi,
>
>     I have been trying to use INCOMPATIBLE_LICENSE to filter out
>     undesirable
>     licenses for us from our images. I started simple and picked the
>     examples from the manual (AGPL-3.0, GPL-3.0 and LGPL-3.0).
>
>     Currently we're based on Warrior, but I also did a short test on master
>     (results later in the message)
>
>     Our images use systemd as init system. We use busybox ash as shell on
>     these images for now.
>
>     When setting the INCOMPATIBLE_LICENSE according to the manual example,
>     systemd cannot be built anymore because bash is being skipped due to
>     license.
>
>     Turns out that because systemd-bash-completion and
>     systemd-kernel-install both rdepend on bash, we can't build systemd at
>     all, because bash is not buildable. Even if we're not installing those
>     features of systemd.
>
>     A dive into TaskData suggests that all the rdepends of all packages
>     provided by a recipe are flattened into depends of the recipe when
>     testing buildability.
>
>     A quick test on master from about 2 weeks ago show the same behavior.
>
>     For the test on master all I did was change the DISTRO_FEATURES of
>     core-image-minimal to include systemd.
>
>
>     Am I using ICOMPATIBLE_LICENSE properly so far?
>     If so, is being unable to fulfill an rdepend for an unused package
>     meant
>     to fail the whole build, and how can I avoid it short of including
>     meta-gplv2 or writing lots of .bbappends to remove the dependencies?
>     Otherwise, where did I go wrong, and what should I be trying instead?
>
>     Thank you.
>
>     Best regards // John Ernberg
>     
>


Re: INCOMPATIBLE_LICENSE - how to use it properly?

Mikko Rapeli
 

Hi,

On Tue, Jun 30, 2020 at 09:34:39AM +0000, John Ernberg wrote:
Hi,

I have been trying to use INCOMPATIBLE_LICENSE to filter out undesirable
licenses for us from our images. I started simple and picked the
examples from the manual (AGPL-3.0, GPL-3.0 and LGPL-3.0).

Currently we're based on Warrior, but I also did a short test on master
(results later in the message)

Our images use systemd as init system. We use busybox ash as shell on
these images for now.

When setting the INCOMPATIBLE_LICENSE according to the manual example,
systemd cannot be built anymore because bash is being skipped due to
license.

Turns out that because systemd-bash-completion and
systemd-kernel-install both rdepend on bash, we can't build systemd at
all, because bash is not buildable. Even if we're not installing those
features of systemd.

A dive into TaskData suggests that all the rdepends of all packages
provided by a recipe are flattened into depends of the recipe when
testing buildability.

A quick test on master from about 2 weeks ago show the same behavior.

For the test on master all I did was change the DISTRO_FEATURES of
core-image-minimal to include systemd.


Am I using ICOMPATIBLE_LICENSE properly so far?
If so, is being unable to fulfill an rdepend for an unused package meant
to fail the whole build, and how can I avoid it short of including
meta-gplv2 or writing lots of .bbappends to remove the dependencies?
Otherwise, where did I go wrong, and what should I be trying instead?
You need to add exceptions to build a lot GPLv3 components but not let them
be part of product images.

In distro config:

INCOMPATIBLE_LICENSE += "GPLv3 GPLv3+ LGPLv3 LGPLv3+"
...
WHITELIST_GPL-3.0 += "bash"
PACKAGE_EXCLUDE += "bash-ptest bash-dbg bash-staticdev bash-dev bash-doc bash-locale bashbug bash"
...

The PACKAGE_EXCLUDE must be complete list of binary packages produced by the recipe.

I end up enabling a large set of GPLv3 tools for use as development tooling at build
time or in SDK:

$ grep WHITELIST_ distro.conf
WHITELIST_GPL-3.0 += "autoconf"
WHITELIST_GPL-3.0 += "bash"
WHITELIST_GPL-3.0 += "bc"
WHITELIST_GPL-3.0 += "binutils"
WHITELIST_GPL-3.0 += "bison"
WHITELIST_GPL-3.0 += "ccache"
WHITELIST_GPL-3.0 += "coreutils"
WHITELIST_GPL-3.0 += "diffutils"
WHITELIST_GPL-3.0 += "elfutils"
WHITELIST_GPL-3.0 += "findutils"
WHITELIST_GPL-3.0 += "gawk"
WHITELIST_GPL-3.0 += "gdb"
WHITELIST_GPL-3.0 += "gdbm"
WHITELIST_GPL-3.0 += "gettext"
WHITELIST_GPL-3.0 += "gnutls"
WHITELIST_GPL-3.0 += "grep"
WHITELIST_GPL-3.0 += "libevent"
WHITELIST_GPL-3.0 += "libpipeline"
WHITELIST_GPL-3.0 += "libunistring"
WHITELIST_GPL-3.0 += "m4"
WHITELIST_GPL-3.0 += "make"
WHITELIST_GPL-3.0 += "readline"
WHITELIST_GPL-3.0 += "rsync"
WHITELIST_GPL-3.0 += "sed"
WHITELIST_GPL-3.0 += "which"

If one does not do this, alternative is to use a bunch of old and deprecated tool
versions from meta-gplv2.

Hope this helps,

-Mikko


Re: INCOMPATIBLE_LICENSE - how to use it properly?

John Ernberg
 

Hi Alex,

I will give this a try on master.

One question though, will this still catch build-only libraries? (i.e. a
library that consists only of headers). I don't think we have such
recipes right now, it's more to understand how this feature works.

Thank you.

Best regards // John Ernberg

On 6/30/20 11:55 AM, Alexander Kanavin wrote:
On master, you can set INCOMPATIBLE_LICENSE in the image recipe, rather
than globally, then the check would only be performed on items that
actually go into that image.

Warrior does not have that feature yet, I think, so your only option
there is meta-gpl2.

Alex

On Tue, 30 Jun 2020 at 11:34, John Ernberg <john.ernberg@actia.se
<mailto:john.ernberg@actia.se>> wrote:

Hi,

I have been trying to use INCOMPATIBLE_LICENSE to filter out
undesirable
licenses for us from our images. I started simple and picked the
examples from the manual (AGPL-3.0, GPL-3.0 and LGPL-3.0).

Currently we're based on Warrior, but I also did a short test on master
(results later in the message)

Our images use systemd as init system. We use busybox ash as shell on
these images for now.

When setting the INCOMPATIBLE_LICENSE according to the manual example,
systemd cannot be built anymore because bash is being skipped due to
license.

Turns out that because systemd-bash-completion and
systemd-kernel-install both rdepend on bash, we can't build systemd at
all, because bash is not buildable. Even if we're not installing those
features of systemd.

A dive into TaskData suggests that all the rdepends of all packages
provided by a recipe are flattened into depends of the recipe when
testing buildability.

A quick test on master from about 2 weeks ago show the same behavior.

For the test on master all I did was change the DISTRO_FEATURES of
core-image-minimal to include systemd.


Am I using ICOMPATIBLE_LICENSE properly so far?
If so, is being unable to fulfill an rdepend for an unused package
meant
to fail the whole build, and how can I avoid it short of including
meta-gplv2 or writing lots of .bbappends to remove the dependencies?
Otherwise, where did I go wrong, and what should I be trying instead?

Thank you.

Best regards // John Ernberg


Re: INCOMPATIBLE_LICENSE - how to use it properly?

Alexander Kanavin
 

On master, you can set INCOMPATIBLE_LICENSE in the image recipe, rather than globally, then the check would only be performed on items that actually go into that image.

Warrior does not have that feature yet, I think, so your only option there is meta-gpl2.

Alex


On Tue, 30 Jun 2020 at 11:34, John Ernberg <john.ernberg@...> wrote:
Hi,

I have been trying to use INCOMPATIBLE_LICENSE to filter out undesirable
licenses for us from our images. I started simple and picked the
examples from the manual (AGPL-3.0, GPL-3.0 and LGPL-3.0).

Currently we're based on Warrior, but I also did a short test on master
(results later in the message)

Our images use systemd as init system. We use busybox ash as shell on
these images for now.

When setting the INCOMPATIBLE_LICENSE according to the manual example,
systemd cannot be built anymore because bash is being skipped due to
license.

Turns out that because systemd-bash-completion and
systemd-kernel-install both rdepend on bash, we can't build systemd at
all, because bash is not buildable. Even if we're not installing those
features of systemd.

A dive into TaskData suggests that all the rdepends of all packages
provided by a recipe are flattened into depends of the recipe when
testing buildability.

A quick test on master from about 2 weeks ago show the same behavior.

For the test on master all I did was change the DISTRO_FEATURES of
core-image-minimal to include systemd.


Am I using ICOMPATIBLE_LICENSE properly so far?
If so, is being unable to fulfill an rdepend for an unused package meant
to fail the whole build, and how can I avoid it short of including
meta-gplv2 or writing lots of .bbappends to remove the dependencies?
Otherwise, where did I go wrong, and what should I be trying instead?

Thank you.

Best regards // John Ernberg


INCOMPATIBLE_LICENSE - how to use it properly?

John Ernberg
 

Hi,

I have been trying to use INCOMPATIBLE_LICENSE to filter out undesirable
licenses for us from our images. I started simple and picked the
examples from the manual (AGPL-3.0, GPL-3.0 and LGPL-3.0).

Currently we're based on Warrior, but I also did a short test on master
(results later in the message)

Our images use systemd as init system. We use busybox ash as shell on
these images for now.

When setting the INCOMPATIBLE_LICENSE according to the manual example,
systemd cannot be built anymore because bash is being skipped due to
license.

Turns out that because systemd-bash-completion and
systemd-kernel-install both rdepend on bash, we can't build systemd at
all, because bash is not buildable. Even if we're not installing those
features of systemd.

A dive into TaskData suggests that all the rdepends of all packages
provided by a recipe are flattened into depends of the recipe when
testing buildability.

A quick test on master from about 2 weeks ago show the same behavior.

For the test on master all I did was change the DISTRO_FEATURES of
core-image-minimal to include systemd.


Am I using ICOMPATIBLE_LICENSE properly so far?
If so, is being unable to fulfill an rdepend for an unused package meant
to fail the whole build, and how can I avoid it short of including
meta-gplv2 or writing lots of .bbappends to remove the dependencies?
Otherwise, where did I go wrong, and what should I be trying instead?

Thank you.

Best regards // John Ernberg


Re: Error building openjdk-8 on zeus

srijan.nandi@...
 

So here is what I have done so far:.

# Added meta-java layer in bblayers.conf and then did a bitbake -c cleanall glibc followed by bitbake glibc. Everything builds successfully.

# As soon as I try to build bitbake core-image-full-cmdline, I get the following errors:

ERROR: linux-yocto-5.2.17+gitAUTOINC+bb2776d6be_25b14cdf96-r0 do_package: Error executing a python function in exec_python_func() autogenerated:
 
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
     0001:
 *** 0002:split_kernel_module_packages(d)
     0003:
File: '/opt/graylog-poky/meta/classes/kernel-module-split.bbclass', lineno: 171, function: split_kernel_module_packages
     0167:    # avoid warnings. removedirs only raises an OSError if an empty
     0168:    # directory cannot be removed.
     0169:    dvar = d.getVar('PKGD')
     0170:    for dir in ["%s/etc/modprobe.d" % (dvar), "%s/etc/modules-load.d" % (dvar), "%s/etc" % (dvar)]:
 *** 0171:        if len(os.listdir(dir)) == 0:
     0172:            os.rmdir(dir)
     0173:}
     0174:
     0175:do_package[vardeps] += '${@" ".join(map(lambda s: "module_conf_" + s, (d.getVar("KERNEL_MODULE_PROBECONF") or "").split()))}'
Exception: FileNotFoundError: [Errno 2] No such file or directory: '/opt/graylog-poky/build/tmp/work/genericx86_64-poky-linux/linux-yocto/5.2.17+gitAUTOINC+bb2776d6be_25b14cdf96-r0/package/etc/modprobe.d'
 
ERROR: Logfile of failure stored in: /opt/graylog-poky/build/tmp/work/genericx86_64-poky-linux/linux-yocto/5.2.17+gitAUTOINC+bb2776d6be_25b14cdf96-r0/temp/log.do_package.29306
ERROR: Task (/opt/graylog-poky/meta/recipes-kernel/linux/linux-yocto_5.2.bb:do_package) failed with exit code '1'
ERROR: volatile-binds-1.0-r0 do_package: SYSTEMD_SERVICE_volatile-binds value var-volatile-lib.service does not exist
ERROR: Logfile of failure stored in: /opt/graylog-poky/build/tmp/work/all-poky-linux/volatile-binds/1.0-r0/temp/log.do_package.29309
ERROR: Task (/opt/graylog-poky/meta/recipes-core/volatile-binds/volatile-binds.bb:do_package) failed with exit code '1'
ERROR: run-postinsts-1.0-r10 do_package: SYSTEMD_SERVICE_run-postinsts value run-postinsts.service does not exist
ERROR: Logfile of failure stored in: /opt/graylog-poky/build/tmp/work/all-poky-linux/run-postinsts/1.0-r10/temp/log.do_package.29316
ERROR: Task (/opt/graylog-poky/meta/recipes-devtools/run-postinsts/run-postinsts_1.0.bb:do_package) failed with exit code '1'

# If I remove the meta-java layer from bblayers.conf, everything builds successfully.

-=Srijan

3701 - 3720 of 53484