[OE-core][kirkstone 00/23] Pull request (cover letter only)

[Steve Sakoman]

The following changes since commit a4bfb5ceb5cf8c0c6d27225b27ef10c0b9dceccb:

  libsoup: upgrade 3.0.6 -> 3.0.7 (2022-07-13 11:54:16 -1000)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-next

Bruce Ashfield (19):
  linux-yocto/5.10: update to v5.10.121
  linux-yocto/5.10: update to v5.10.123
  linux-yocto/5.10: update to v5.10.128
  linux-yocto/5.10: fix build_OID_registry/conmakehash buildpaths
warning
  linux-yocto/5.10: fix buildpaths issue with gen-mach-types
  linux-yocto/5.10: update to v5.10.130
  linux-yocto/5.10: fix buildpaths issue with pnmtologo
  linux-yocto/5.15: update to v5.15.46
  linux-yocto/5.15: update to v5.15.48
  linux-yocto/5.15: drop obselete GPIO sysfs ABI
  linux-yocto/5.15: update to v5.15.52
  linux-yocto/5.15: fix qemuppc buildpaths warning
  linux-yocto/5.15: fix build_OID_registry buildpaths warning
  linux-yocto/5.15: fix buildpaths issue with gen-mach-types
  linux-yocto/5.15: update to v5.15.54
  linux-yocto/5.15: fix buildpaths issue with pnmtologo
  kernel-devsrc: fix reproducibility and buildpaths QA warning
  kernel-devsrc: ppc32: fix reproducibility
  perf: fix reproducibility in 5.19+

Richard Purdie (4):
  qemu: Fix slirp determinism issue
  qemu: Add PACKAGECONFIG for brlapi
  gperf: Add a patch to work around reproducibility issues
  gperf: Switch to upstream patch

 .../qemu/qemu-system-native_6.2.0.bb  |   2 +-
 meta/recipes-devtools/qemu/qemu.inc   |   2 +
 meta/recipes-devtools/qemu/qemu_6.2.0.bb  |   4 +-
 ...c6e57a308a05889c80c048dbc58bdc378dcb.patch | 181 ++
 meta/recipes-extended/gperf/gperf_3.1.bb  |   2 +
 meta/recipes-kernel/linux/kernel-devsrc.bb|   8 +-
 .../linux/linux-yocto-rt_5.10.bb  |   6 +-
 .../linux/linux-yocto-rt_5.15.bb  |   6 +-
 .../linux/linux-yocto-tiny_5.10.bb|   8 +-
 .../linux/linux-yocto-tiny_5.15.bb|   6 +-
 meta/recipes-kernel/linux/linux-yocto_5.10.bb |  24 +--
 meta/recipes-kernel/linux/linux-yocto_5.15.bb |  26 +--
 meta/recipes-kernel/perf/perf.bb  |   6 +
 13 files changed, 238 insertions(+), 43 deletions(-)
 create mode 100644 
meta/recipes-extended/gperf/gperf/1862c6e57a308a05889c80c048dbc58bdc378dcb.patch

-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168292): 
https://lists.openembedded.org/g/openembedded-core/message/168292
Mute This Topic: https://lists.openembedded.org/mt/92497480/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.1_M2.rc1)

[Teoh, Jay Shen]

Hello everyone,

Intel and WR YP QA is planning for QA execution for YP build yocto-4.1_M2.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. NUC 7
3. NUC 6
4. Edgerouter
5. Beaglebone

ETA for completion next Monday, July 25.

Thanks,
Jay

> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Wednesday, 20 July, 2022 3:23 AM
> To: yo...@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-4.1_M2.rc1)
> 
> 
> A build flagged for QA (yocto-4.1_M2.rc1) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-4.1_M2.rc1
> 
> 
> Build hash information:
> 
> bitbake: b171aa45fb8518dcfbba315b303a4fe9bf2180c6
> meta-agl: b5044156fc318a4881e766513871611a560170be
> meta-arm: 6481a473d84f84530e0c48d56acdc185919869b6
> meta-aws: 2f5075673489ee2d3fc318f6626d45145f65d5ea
> meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a
> meta-intel: de5851890f9a268621515193d2ad84f8359fbe24
> meta-mingw: 205e9d942bc8ea1643a8d27b79e773625d173c00
> meta-openembedded: 0c2e416567351d55ae45e67513be6f20aa754d4b
> meta-virtualization: 7ec4b4746d9d76062a868ea77818a150ddd53c54
> oecore: b4f1b78aef77198f26a8ef9e105fa690cc12e836
> poky: 899979696f68ff4414cebf7782b37d7bae27144b
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168291): 
https://lists.openembedded.org/g/openembedded-core/message/168291
Mute This Topic: https://lists.openembedded.org/mt/92497297/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] systemd: Added base_bindir into pkg_postinst:udev-hwdb.

[leimaohui]

Otherwise in sdk environment, the base_bindir is empty and the path of 
UDEVADM="${base_bindir}/udevadm" is not correct.

Signed-off-by: Lei Maohui 
---
 meta/recipes-core/systemd/systemd_251.2.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/systemd/systemd_251.2.bb 
b/meta/recipes-core/systemd/systemd_251.2.bb
index bb3c59f418..2d0d21a69a 100644
--- a/meta/recipes-core/systemd/systemd_251.2.bb
+++ b/meta/recipes-core/systemd/systemd_251.2.bb
@@ -786,7 +786,7 @@ pkg_prerm:${PN}:libc-glibc () {
 PACKAGE_WRITE_DEPS += "qemu-native"
 pkg_postinst:udev-hwdb () {
if test -n "$D"; then
-   $INTERCEPT_DIR/postinst_intercept update_udev_hwdb ${PKG} 
mlprefix=${MLPREFIX} binprefix=${MLPREFIX} rootlibexecdir="${rootlibexecdir}" 
PREFERRED_PROVIDER_udev="${PREFERRED_PROVIDER_udev}"
+   $INTERCEPT_DIR/postinst_intercept update_udev_hwdb ${PKG} 
mlprefix=${MLPREFIX} binprefix=${MLPREFIX} rootlibexecdir="${rootlibexecdir}" 
PREFERRED_PROVIDER_udev="${PREFERRED_PROVIDER_udev}" 
base_bindir="${base_bindir}"
else
udevadm hwdb --update
fi
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168290): 
https://lists.openembedded.org/g/openembedded-core/message/168290
Mute This Topic: https://lists.openembedded.org/mt/92496522/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core][PATCH v2] package_manager/ipk: do not pipe stderr to stdout

[Shruthi Ravichandran]

Some opkg commands print an error during cleanup when the tmp_dir
does not exist and an attempt is made to delete it. The error messages
are harmless and the opkg commands eventually succeed.
When these commands are run and stderr is piped to stdout, the error
messages may clobber the stdout and cause unexpected results while
parsing the output of the command. Therefore, when parsing the output
of a command, do not pipe stderr to stdout. Instead, capture stderr
and stdout separately, and upon success, send stderr to bb.note().

Signed-off-by: Shruthi Ravichandran 
---
 meta/lib/oe/package_manager/ipk/__init__.py | 30 ++---
 1 file changed, 20 insertions(+), 10 deletions(-)

diff --git a/meta/lib/oe/package_manager/ipk/__init__.py 
b/meta/lib/oe/package_manager/ipk/__init__.py
index 6fd2f021b6..a768de5c30 100644
--- a/meta/lib/oe/package_manager/ipk/__init__.py
+++ b/meta/lib/oe/package_manager/ipk/__init__.py
@@ -102,12 +102,17 @@ class OpkgDpkgPM(PackageManager):
 This method extracts the common parts for Opkg and Dpkg
 """

-try:
-output = subprocess.check_output(cmd, stderr=subprocess.STDOUT, 
shell=True).decode("utf-8")
-except subprocess.CalledProcessError as e:
+proc = subprocess.Popen(cmd, stdout=subprocess.PIPE, 
stderr=subprocess.PIPE, shell=True)
+cmd_stdout, cmd_stderr = proc.communicate()
+cmd_stdout = cmd_stdout.decode("utf-8")
+cmd_stderr = cmd_stderr.decode("utf-8")
+if proc.returncode:
 bb.fatal("Unable to list available packages. Command '%s' "
- "returned %d:\n%s" % (cmd, e.returncode, 
e.output.decode("utf-8")))
-return opkg_query(output)
+"returned %d:\n%s" % (cmd, proc.returncode, cmd_stderr))
+elif cmd_stderr:
+bb.note("Command '%s' returned stderr: %s" % (cmd, cmd_stderr))
+
+return opkg_query(cmd_stdout)

 def extract(self, pkg, pkg_info):
 """
@@ -445,15 +450,20 @@ class OpkgPM(OpkgDpkgPM):
 cmd = "%s %s --noaction install %s " % (self.opkg_cmd,
 opkg_args,
 ' '.join(pkgs))
-try:
-output = subprocess.check_output(cmd, stderr=subprocess.STDOUT, 
shell=True)
-except subprocess.CalledProcessError as e:
+
+proc = subprocess.Popen(cmd, stdout=subprocess.PIPE, 
stderr=subprocess.PIPE, shell=True)
+cmd_stdout, cmd_stderr = proc.communicate()
+cmd_stdout = cmd_stdout.decode("utf-8")
+cmd_stderr = cmd_stderr.decode("utf-8")
+if proc.returncode:
 bb.fatal("Unable to dummy install packages. Command '%s' "
- "returned %d:\n%s" % (cmd, e.returncode, 
e.output.decode("utf-8")))
+ "returned %d:\n%s" % (cmd, proc.returncode, cmd_stderr))
+elif cmd_stderr:
+bb.note("Command '%s' returned stderr: %s" % (cmd, cmd_stderr))

 bb.utils.remove(temp_rootfs, True)

-return output
+return cmd_stdout

 def backup_packaging_data(self):
 # Save the opkglib for increment ipk image generation
--
2.20.1


> -Original Message-
> From: Alexander Kanavin 
> Sent: Friday, July 1, 2022 5:26 AM
> To: Shruthi Ravichandran 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core][PATCH] package_manager/ipk: do not pipe stderr to 
> stdout
>
> Yes, certainly.
>
> Alex
>
> On Fri, 1 Jul 2022 at 00:30, Shruthi Ravichandran
>  wrote:
> >
> > The change currently does discard everything in stderr. I can update
> > it to capture stderr and push it to bb.note on command success and
> > bb.fatal on command failure. In fact, I can make those changes to the
> > several other instances in this file where stderr is piped to stdout
> > too. Would that be acceptable?
> >
> > Shruthi
> >
> > > -Original Message-
> > > From: Alexander Kanavin 
> > > Sent: Thursday, June 30, 2022 1:47 AM
> > > To: Shruthi Ravichandran 
> > > Cc: openembedded-core@lists.openembedded.org
> > > Subject: Re: [OE-core][PATCH] package_manager/ipk: do not pipe stderr to 
> > > stdout
> > >
> > > Thanks for the information - perhaps this should be added to the commit 
> > > message?
> > >
> > > Does this change discard things that appear on stderr completely, or
> > > does it still go somewhere where it can be seen later?
> > >
> > > Alex
> > >
> > > On Wed, 29 Jun 2022 at 21:22, Shruthi Ravichandran
> > >  wrote:
> > > >
> > > > Hi Alex,
> > > >
> > > > I've found that some OE commands print an error during cleanup when
> > > > the tmp_dir does not exist and an attempt is made to delete it. I've
> > > > submitted a patch to opkg to fix that.
> > > > Link:
> > >
> https://urldefense.com/v3/__https://git.yoctoproject.org/opkg/commit/?id=8dfdda86afd407a66e3dc00a077bdcc8b53d54ea__;!!FbZ0ZwI
> > > 3Qg!omDrJfbrjlLbY2OMgsAgQrIcnap222jrjZJAhJX_BWhVJfMi09419QAHH1bVf1Va

Re: [OE-core] Forced password change in first login

[Livius]

I got this "feature" on Yocto project of Xilinx ( 
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841883/Yocto ) 
rel-v2022.1 (honister). It seems to me my Linux kernel uses SHA-512 in default 
because after my first password change i could se the ident number of this 
encryption in /etc/shadow ( 
https://www.cyberciti.biz/faq/understanding-etcshadow-file/ ). For all of my 
pre-made users from Yocto recipes if they had SHA-256 password hash, in first 
login it was forced to change. I could solve it after that i realizedm my Linux 
build likes to generate SHA-512 password has in run-time.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168288): 
https://lists.openembedded.org/g/openembedded-core/message/168288
Mute This Topic: https://lists.openembedded.org/mt/91308780/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Hash Equivalence Server Domain Change

[Michael Halstead]

We are moving the hash equivalence server to dedicated servers. As part of
the change we need to change the domain.

Please update any BB_HASHSERVE_UPSTREAM

variables
from "typhoon.yocto.io:8687" to "hashserv.yocto.io:8687" at your
earliest convenience.

We plan to make the switch during the next maintenance window on Friday
July 22nd. The previous server will quickly fall out of date and be taken
offline next week.

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168287): 
https://lists.openembedded.org/g/openembedded-core/message/168287
Mute This Topic: https://lists.openembedded.org/mt/92489530/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][master][kirkstone][PATCH] cve-check.bbclass: Add anonymous function to get patched CVEs from recipe

[Marta Rybczynska]

On Tue, Jul 12, 2022 at 12:28 PM akash hadke via
lists.openembedded.org 
wrote:
>
> Add an anonymous function to get patched CVEs from the recipe
> and set the value to 'CVE_PATCHED' variable
> This variable later can be used to do CVE data processing
> outside of bitbake
>
> Also, introduce a new variable 'CVE_CHECK_WITH_DB' default set
> to '0', when it is set to non zero value it avoids CVE scan for
> unpatched CVEs from NVD DB.
> It will work as the second operational mode for cve-check.bbclass
> which only exports the data.
>
> Signed-off-by: Akash Hadke 
> ---
>  meta/classes/cve-check.bbclass | 15 +--
>  1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
> index da7f93371c..b7f7ca73e5 100644
> --- a/meta/classes/cve-check.bbclass
> +++ b/meta/classes/cve-check.bbclass
> @@ -82,6 +82,12 @@ CVE_CHECK_LAYER_INCLUDELIST ??= ""
>  # set to "alphabetical" for version using single alphabetical character as 
> increment release
>  CVE_VERSION_SUFFIX ??= ""
>
> +# set to "1" for avoiding full scan for unpatched CVEs
> +CVE_CHECK_WITH_DB ??= "0"

The default behavior is now to check with the database, so this should be at "1"
by default.

> +
> +# Patched CVEs from recipe will be assigned to this variable
> +CVE_PATCHED ??= ""
> +
>  def generate_json_report(d, out_path, link_path):
>  if os.path.exists(d.getVar("CVE_CHECK_SUMMARY_INDEX_PATH")):
>  import json
> @@ -133,13 +139,18 @@ python cve_save_summary_handler () {
>  addhandler cve_save_summary_handler
>  cve_save_summary_handler[eventmask] = "bb.event.BuildCompleted"
>
> +python() {
> +from oe.cve_check import get_patched_cves
> +d.setVar('CVE_PATCHED', " ".join(get_patched_cves(d)))
> +}
> +
>  python do_cve_check () {
>  """
>  Check recipe for patched and unpatched CVEs
>  """
>  from oe.cve_check import get_patched_cves
>
> -if os.path.exists(d.getVar("CVE_CHECK_DB_FILE")):
> +if os.path.exists(d.getVar("CVE_CHECK_DB_FILE")) and 
> d.getVar("CVE_CHECK_WITH_DB") == "0":
>  try:
>  patched_cves = get_patched_cves(d)
>  except FileNotFoundError:

Instead of the anonymous function, you could add a condition here.


Regards,
Marta

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168286): 
https://lists.openembedded.org/g/openembedded-core/message/168286
Mute This Topic: https://lists.openembedded.org/mt/92329911/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH][dunfell] linux-yocto-rt/5.4: fixup -rt build breakage

[Steve Sakoman]

On Mon, Jul 18, 2022 at 6:04 PM Bruce Ashfield  wrote:
>
> On Tue, Jul 19, 2022 at 12:01 AM Denys Dmytriyenko  wrote:
> >
> > On Mon, Jul 18, 2022 at 11:44:56PM -0400, Bruce Ashfield wrote:
> > > From: Bruce Ashfield 
> > >
> > > Integrating the following commit(s) to linux-yocto/5.4:
> > >
> > > cc478e363cc3 rt: fixup random and irq/manage merge issues
> > >
> > > Signed-off-by: Bruce Ashfield 
> > > ---
> > >  meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb 
> > > b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
> > > index 5bc1993cf2..fe75aee4da 100644
> > > --- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
> > > +++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
> > > @@ -11,7 +11,7 @@ python () {
> > >  raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel 
> > > to linux-yocto-rt to enable it")
> > >  }
> > >
> > > -SRCREV_machine ?= "086bb7f7d2b47d654922e5cc526cc6274b28e319"
> >
> > This does not match to what is currently in dunfell, so it won't apply:
> > https://git.openembedded.org/openembedded-core/tree/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb?h=dunfell#n14
> >
>
> right. I have another -stable update pending for dunfell, that need to
> be applied first. In my rush to get this change out, I forgot that!
>
> I'll resend everything later this week, I'm off to other things for a few 
> days.

Perfect, the 3.1.18 build is scheduled for next Monday and I'd really
like to get this fix in.

Steve

> > > +SRCREV_machine ?= "cc478e363cc35064b58a871a4cc535aa973c5891"
> > >  SRCREV_meta ?= "aaaf9f090dfb3160154b24fbc2f9a6e669babc87"
> > >
> > >  SRC_URI = 
> > > "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine
> > >  \
> > > --
> > > 2.19.1
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168285): 
https://lists.openembedded.org/g/openembedded-core/message/168285
Mute This Topic: https://lists.openembedded.org/mt/92476074/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] gcc-runtime: Pass -nostartfiles when building dummy libstdc++.so

[Jon Mason]

On Mon, Jul 18, 2022 at 11:00 PM Khem Raj  wrote:
>
> This is a dummy shared object therefore reduce dependencies further by
> not requiring the C startup files, we wont use this shared library for
> anything useful anyway
>
> Signed-off-by: Khem Raj 
> ---

This resolved the build break I was seeing in zephyr of
 
/builder/meta-arm/build/tmp/work/cortexm0-poky-eabi/gcc-runtime/12.1.0-r0/recipe-sysroot-native/usr/bin/arm-poky-eabi/../../libexec/arm-poky-eabi/gcc/arm-poky-eabi/12.1.0/ld:
cannot find crt0.o: No such file or directory

Thanks for getting this out so quickly Khem!


>  meta/recipes-devtools/gcc/gcc-runtime.inc | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc 
> b/meta/recipes-devtools/gcc/gcc-runtime.inc
> index 5d74e4494d1..3e1c799ba13 100644
> --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
> +++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
> @@ -68,8 +68,7 @@ do_configure () {
> # libstdc++ isn't built yet so CXX would error not able to find it 
> which breaks stdc++'s configure
> # tests. Create a dummy empty lib for the purposes of configure.
> mkdir -p ${WORKDIR}/dummylib
> -   touch ${WORKDIR}/dummylib/dummylib.c
> -   ${CC} ${WORKDIR}/dummylib/dummylib.c -shared -o 
> ${WORKDIR}/dummylib/libstdc++.so
> +   ${CC} -x c /dev/null -nostartfiles -shared -o 
> ${WORKDIR}/dummylib/libstdc++.so
> for d in libgcc ${RUNTIMETARGET}; do
> echo "Configuring $d"
> rm -rf ${B}/${TARGET_SYS}/$d/
> --
> 2.37.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168284): 
https://lists.openembedded.org/g/openembedded-core/message/168284
Mute This Topic: https://lists.openembedded.org/mt/92475659/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [oe] [meta-zephyr] build broken with current oe-core master

[Khem Raj]

On Tue, Jul 19, 2022 at 10:48 AM Bartosz Golaszewski  wrote:
>
> On Tue, Jul 19, 2022 at 2:54 PM Khem Raj  wrote:
> >
> >
> >
> > On Tue, Jul 19, 2022 at 3:40 AM Bartosz Golaszewski  wrote:
> >>
> >> On Tue, Jul 19, 2022 at 12:10 AM Jon Mason  wrote:
> >> >
> >> > On Mon, Jul 18, 2022 at 4:06 PM Khem Raj  wrote:
> >> > >
> >> > > Can you try something like this
> >> > >
> >> > > diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc
> >> > > b/meta/recipes-devtools/gcc/gcc-runtime.inc
> >> > > index 5d74e4494d..61d5bf6058 100644
> >> > > --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
> >> > > +++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
> >> > > @@ -68,8 +68,7 @@ do_configure () {
> >> > > # libstdc++ isn't built yet so CXX would error not able to find it
> >> > > which breaks stdc++'s configure
> >> > > # tests. Create a dummy empty lib for the purposes of configure.
> >> > > mkdir -p ${WORKDIR}/dummylib
> >> > > -   touch ${WORKDIR}/dummylib/dummylib.c
> >> > > -   ${CC} ${WORKDIR}/dummylib/dummylib.c -shared -o
> >> > > ${WORKDIR}/dummylib/libstdc++.so
> >> > > +   ${CC} -nostartfiles -shared -x c /dev/null -o
> >> > > ${WORKDIR}/dummylib/libstdc++.so
> >> > > for d in libgcc ${RUNTIMETARGET}; do
> >> > > echo "Configuring $d"
> >> > > rm -rf ${B}/${TARGET_SYS}/$d/
> >> > >
> >> > >
> >> > > and see if it helps ?
> >> >
> >> > That appears to work for the 2 zephyr machines in meta-arm
> >> >
> >>
> >> This still fails for arduino nano 33 ble:
> >>
> >> | checking for dirent.h... no
> >> | checking sys/statvfs.h usability... no
> >> | checking sys/statvfs.h presence... no
> >> | checking for sys/statvfs.h... no
> >> | checking utime.h usability... yes
> >> | checking utime.h presence... yes
> >> | checking for utime.h... yes
> >> | checking whether to build Filesystem TS support... no
> >> | checking for struct dirent.d_type... no
> >> | checking for realpath... no
> >> | checking for utimensat... no
> >> | checking for utime... no
> >> | checking for lstat... no
> >> | checking for struct stat.st_mtim.tv_nsec... yes
> >> | checking for fchmod... yes
> >> | checking for fchmodat... yes
> >> | checking for sendfile that can copy files... no
> >> | checking for link... yes
> >> | checking for readlink... yes
> >> | checking for symlink... yes
> >> | checking for truncate... yes
> >> | checking for fdopendir... no
> >> | checking for dirfd... no
> >> | checking for unlinkat... yes
> >> | checking __sync extensions... yes
> >> | checking link.h usability... no
> >> | checking link.h presence... no
> >> | checking for link.h... no
> >> | checking for fcntl... configure: error: Link tests are not allowed
> >> after GCC_NO_EXECUTABLES.
> >
> >
> >
> > Can you post config.log from this component
> >
>
> Here you go: https://pastebin.com/6KMD9PhX

this one has succeeded. I guess there are multiple config.log files in
your build tree. Perhaps the one which shows exit 1 at the end is one
I am interested in.

>
> Bart

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168283): 
https://lists.openembedded.org/g/openembedded-core/message/168283
Mute This Topic: https://lists.openembedded.org/mt/92467688/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Yocto Project Status 19 July 2022 (WW29)

[Neal Caidin]

Current Dev Position: YP 4.1 M3

Next Deadline: 22nd August 2022 YP 4.1 M3 Build

Next Team Meetings:

   -

   Bug Triage meeting Thursday July 21st 7:30 am PDT (
   https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
   -

   Weekly Project Engineering Sync Tuesday July 19th  at 8 am PDT (
   https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
   
   -

   Twitch -  See https://www.twitch.tv/theyoctojester


Key Status/Updates:

   -

   YP 4.1 M2 has a build in progress and then will go into QA
   -

   Last week there seemed to be a large number of autobuilder issues
   including many non-deterministic dependencies for qemu, as well as a lot of
   intermittent buildpaths issues. These have now mostly been resolved.
   -

   The help received in resolving buildpaths issues was appreciated,
   particularly with the kernel where we seemed to uncover several
   unexpectedly.
   -

   We have enabled buildpaths in WARN_QA by default. This takes our
   reproducibility to a new level but there is some fallout in layers which
   will need to be fixed.
   -

   meta-gplv2 builds have been dropped from master and the layer will no
   longer be maintained.
   -

   We’ve noticed that debug information is still not being processed by
   package.bbclass entirely correctly and it is missing a large chunk of the
   kernel sources for example. RP is trying to debug this.
   -

   There are continued reports of issues with the rust SDK compiler. Sadly
   we just have patches to make x86_64 work rather than getting to the root of
   the issues and cross compile it correctly, which is a concern.
   -

   Work is continuing on the /proc/pressure monitoring code. Initial
   averaging wasn’t working so well but we have an improved approach which
   seems to regulate builds better.
   -

   Help is very much welcome in trying to resolve our autobuilder
   intermittent issues. You can see the list of failures we’re continuing to
   see by searching for the “AB-INT” tag in bugzilla:
   https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT


Ways to contribute:

   -

   There are bugs identified as possible for newcomers to the project:
   https://wiki.yoctoproject.org/wiki/Newcomers
   -

   There are bugs that are currently unassigned for YP 4.1. See:
   
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enhancements.2FBugs
   -

   We’d welcome new maintainers for recipes in OE-Core. Please see the list
   at:
   
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
   and discuss with the existing maintainer, or ask on the OE-Core mailing
   list. We will likely move a chunk of these to “Unassigned” soon to help
   facilitate this.
   -

   Help us resolve CVE issues: CVE metrics
   




YP 4.1 Milestone Dates:

   -

   YP 4.1 M2 Release date 2022/07/22
   -

   YP 4.1 M3 build date 2022/08/22
   -

   YP 4.1 M3 Release date 2022/09/02
   -

   YP 4.1 M4 build date 2022/10/03
   -

   YP 4.1 M4 Release date 2022/10/28


Upcoming dot releases:

   -

   YP 3.1.18 build date 2022/07/27
   -

   YP 3.1.18 Release date 2022/08/05
   -

   YP 4.0.3 build date 2022/08/08
   -

   YP 4.0.3 Release date 2022/08/19
   -

   YP 3.1.19 build date 2022/08/29
   -

   YP 3.1.19 Release date 2022/09/09
   -

   YP 4.0.4 build date 2022/09/19
   -

   YP 4.0.4 Release date 2022/09/30
   -

   YP 3.1.20 build date 2022/10/10
   -

   YP 3.1.20 Release date 2022/10/21
   -

   YP 4.0.5 build date 2022/10/31
   -

   YP 4.0.5 Release date 2022/11/11


Tracking Metrics:

   -

   WDD 2414 (last week 2397) (
   https://wiki.yoctoproject.org/charts/combo.html)
   -

   OE-Core/Poky Patch Metrics
   -

  Total patches found: 1159 (last week 1155)
  -

  Patches in the Pending State: 327 (28%) [last week 327 (28%)]
  -

   https://autobuilder.yocto.io/pub/non-release/patchmetrics/


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!]


*Neal Caidin*
Program Manager, Program Management & Operations
The Linux Foundation
+1 (919) 238-9104 (w/h)
+1 (919) 949-1861 (m)
ncai...@linuxfoundation.org

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168282): 
https://lists.openembedded.org/g/openembedded-core/message/168282
Mute This Topic: https://lists.openembedded.org/mt/92484013/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.o

Re: [OE-core] [oe] [meta-zephyr] build broken with current oe-core master

[Bartosz Golaszewski]

On Tue, Jul 19, 2022 at 2:54 PM Khem Raj  wrote:
>
>
>
> On Tue, Jul 19, 2022 at 3:40 AM Bartosz Golaszewski  wrote:
>>
>> On Tue, Jul 19, 2022 at 12:10 AM Jon Mason  wrote:
>> >
>> > On Mon, Jul 18, 2022 at 4:06 PM Khem Raj  wrote:
>> > >
>> > > Can you try something like this
>> > >
>> > > diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc
>> > > b/meta/recipes-devtools/gcc/gcc-runtime.inc
>> > > index 5d74e4494d..61d5bf6058 100644
>> > > --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
>> > > +++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
>> > > @@ -68,8 +68,7 @@ do_configure () {
>> > > # libstdc++ isn't built yet so CXX would error not able to find it
>> > > which breaks stdc++'s configure
>> > > # tests. Create a dummy empty lib for the purposes of configure.
>> > > mkdir -p ${WORKDIR}/dummylib
>> > > -   touch ${WORKDIR}/dummylib/dummylib.c
>> > > -   ${CC} ${WORKDIR}/dummylib/dummylib.c -shared -o
>> > > ${WORKDIR}/dummylib/libstdc++.so
>> > > +   ${CC} -nostartfiles -shared -x c /dev/null -o
>> > > ${WORKDIR}/dummylib/libstdc++.so
>> > > for d in libgcc ${RUNTIMETARGET}; do
>> > > echo "Configuring $d"
>> > > rm -rf ${B}/${TARGET_SYS}/$d/
>> > >
>> > >
>> > > and see if it helps ?
>> >
>> > That appears to work for the 2 zephyr machines in meta-arm
>> >
>>
>> This still fails for arduino nano 33 ble:
>>
>> | checking for dirent.h... no
>> | checking sys/statvfs.h usability... no
>> | checking sys/statvfs.h presence... no
>> | checking for sys/statvfs.h... no
>> | checking utime.h usability... yes
>> | checking utime.h presence... yes
>> | checking for utime.h... yes
>> | checking whether to build Filesystem TS support... no
>> | checking for struct dirent.d_type... no
>> | checking for realpath... no
>> | checking for utimensat... no
>> | checking for utime... no
>> | checking for lstat... no
>> | checking for struct stat.st_mtim.tv_nsec... yes
>> | checking for fchmod... yes
>> | checking for fchmodat... yes
>> | checking for sendfile that can copy files... no
>> | checking for link... yes
>> | checking for readlink... yes
>> | checking for symlink... yes
>> | checking for truncate... yes
>> | checking for fdopendir... no
>> | checking for dirfd... no
>> | checking for unlinkat... yes
>> | checking __sync extensions... yes
>> | checking link.h usability... no
>> | checking link.h presence... no
>> | checking for link.h... no
>> | checking for fcntl... configure: error: Link tests are not allowed
>> after GCC_NO_EXECUTABLES.
>
>
>
> Can you post config.log from this component
>

Here you go: https://pastebin.com/6KMD9PhX

Bart

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168281): 
https://lists.openembedded.org/g/openembedded-core/message/168281
Mute This Topic: https://lists.openembedded.org/mt/92467688/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Forced password change in first login

[Quentin Schulz]

Hi Livius,

On 7/18/22 23:48, Livius wrote:

In Yocto Honister if i use sha256crypt for my password hash my finished Linux 
image can not like it, and at first boot it forces to me to change it. If i use 
sha512crypt for my hash everything is ok at Linux first boot.



Just tested on top of honister branch (fd00d74f47 yocto-bsps: update to 
v5.10.113) with the same process/diff as given in yesterday's mail. I 
couldn't reproduce what you experienced.


Is there some minimal reproducer you could give us so that we can make 
sure this is fixed? I don't want to fix the docs if the issue is 
actually in the code elsewhere :)


Cheers,
Quentin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168280): 
https://lists.openembedded.org/g/openembedded-core/message/168280
Mute This Topic: https://lists.openembedded.org/mt/91308780/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [oe] [meta-zephyr] build broken with current oe-core master

[Khem Raj]

On Tue, Jul 19, 2022 at 3:40 AM Bartosz Golaszewski  wrote:

> On Tue, Jul 19, 2022 at 12:10 AM Jon Mason  wrote:
> >
> > On Mon, Jul 18, 2022 at 4:06 PM Khem Raj  wrote:
> > >
> > > Can you try something like this
> > >
> > > diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc
> > > b/meta/recipes-devtools/gcc/gcc-runtime.inc
> > > index 5d74e4494d..61d5bf6058 100644
> > > --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
> > > +++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
> > > @@ -68,8 +68,7 @@ do_configure () {
> > > # libstdc++ isn't built yet so CXX would error not able to find it
> > > which breaks stdc++'s configure
> > > # tests. Create a dummy empty lib for the purposes of configure.
> > > mkdir -p ${WORKDIR}/dummylib
> > > -   touch ${WORKDIR}/dummylib/dummylib.c
> > > -   ${CC} ${WORKDIR}/dummylib/dummylib.c -shared -o
> > > ${WORKDIR}/dummylib/libstdc++.so
> > > +   ${CC} -nostartfiles -shared -x c /dev/null -o
> > > ${WORKDIR}/dummylib/libstdc++.so
> > > for d in libgcc ${RUNTIMETARGET}; do
> > > echo "Configuring $d"
> > > rm -rf ${B}/${TARGET_SYS}/$d/
> > >
> > >
> > > and see if it helps ?
> >
> > That appears to work for the 2 zephyr machines in meta-arm
> >
>
> This still fails for arduino nano 33 ble:
>
> | checking for dirent.h... no
> | checking sys/statvfs.h usability... no
> | checking sys/statvfs.h presence... no
> | checking for sys/statvfs.h... no
> | checking utime.h usability... yes
> | checking utime.h presence... yes
> | checking for utime.h... yes
> | checking whether to build Filesystem TS support... no
> | checking for struct dirent.d_type... no
> | checking for realpath... no
> | checking for utimensat... no
> | checking for utime... no
> | checking for lstat... no
> | checking for struct stat.st_mtim.tv_nsec... yes
> | checking for fchmod... yes
> | checking for fchmodat... yes
> | checking for sendfile that can copy files... no
> | checking for link... yes
> | checking for readlink... yes
> | checking for symlink... yes
> | checking for truncate... yes
> | checking for fdopendir... no
> | checking for dirfd... no
> | checking for unlinkat... yes
> | checking __sync extensions... yes
> | checking link.h usability... no
> | checking link.h presence... no
> | checking for link.h... no
> | checking for fcntl... configure: error: Link tests are not allowed
> after GCC_NO_EXECUTABLES.



Can you post config.log from this component


> | WARNING: exit code 1 from a shell command.
> ERROR: Task
> (/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/gcc/gcc-runtime_12.1.bb:
> do_configure)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 795 tasks of which 774 didn't need to
> be rerun and 1 failed.
>
> Summary: 1 task failed:
>
> /home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/gcc/gcc-runtime_12.1.bb:
> do_configure
> Summary: There was 1 ERROR message, returning a non-zero exit code.
>
> Bart
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168279): 
https://lists.openembedded.org/g/openembedded-core/message/168279
Mute This Topic: https://lists.openembedded.org/mt/92467688/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] wic/plugins/rootfs: Fix NameError for 'orig_path'

[Mihai Lindner]

Fix "NameError: name 'orig_path' is not defined".
It's a typo from when this error was handled outside this function.

Signed-off-by: Mihai Lindner 
---
 scripts/lib/wic/plugins/source/rootfs.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/lib/wic/plugins/source/rootfs.py 
b/scripts/lib/wic/plugins/source/rootfs.py
index 25bb41dd70..fc06312ee4 100644
--- a/scripts/lib/wic/plugins/source/rootfs.py
+++ b/scripts/lib/wic/plugins/source/rootfs.py
@@ -35,7 +35,7 @@ class RootfsPlugin(SourcePlugin):
 @staticmethod
 def __validate_path(cmd, rootfs_dir, path):
 if os.path.isabs(path):
-logger.error("%s: Must be relative: %s" % (cmd, orig_path))
+logger.error("%s: Must be relative: %s" % (cmd, path))
 sys.exit(1)
 
 # Disallow climbing outside of parent directory using '..',
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168278): 
https://lists.openembedded.org/g/openembedded-core/message/168278
Mute This Topic: https://lists.openembedded.org/mt/92480897/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2] python3-docutils: upgrade 0.18.1 -> 0.19

[Richard Purdie]

On Tue, 2022-07-19 at 08:03 +0800, wangmy wrote:
> License-Update:
>  year updated to 2022
>  url of some reposity and license changed
>  file lists changed
> 
> Changelog:
> ===
> - Drop support for Python 2.7, 3.5, and 3.6.
> 
> - Output changes:
>   HTML5:
>  Wrap groups of footnotes in an  for easier styling.
>  The CSS rule .footnote-list { display: contents; } can be used to restore
>  the behaviour of custom CSS styles.
> - After package installation, the CLI commands python -m docutils and docutils
>   start the generic command line front end tool.
> - Support parsing "Markdown" input with 3rd party parsers myst, pycmark, or 
> recommonmark.
> - The default values for the "pep-references", "rfc-base-url", and 
> "python-home"
>   configuration settings now use the "https:" scheme. The PEP-writer 
> template's
>   header is updated to fix links and resemble the header of official PEPs.
> - Various bugfixes and improvements (see HISTORY).
> 
> Signed-off-by: Wang Mingyu 
> ---
>  .../{python3-docutils_0.18.1.bb => python3-docutils_0.19.bb}  | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>  rename meta/recipes-devtools/python/{python3-docutils_0.18.1.bb => 
> python3-docutils_0.19.bb} (62%)

Alexandre ended up tweaking the wording of this commit and I've taken
that version. Please have a look at it as an example of a good way of
summarising the license changes. The key piece was effectively:

"list of files under BSD-2-Clause license changed"

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168277): 
https://lists.openembedded.org/g/openembedded-core/message/168277
Mute This Topic: https://lists.openembedded.org/mt/92472708/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2] python3-docutils: upgrade 0.18.1 -> 0.19

[Alexander Kanavin]

That should be ok, but you need to re-send the commit.

Alex

On Tue, 19 Jul 2022 at 02:04, wangmy  wrote:
>
> License-Update:
>  year updated to 2022
>  url of some reposity and license changed
>  file lists changed
>
> Changelog:
> ===
> - Drop support for Python 2.7, 3.5, and 3.6.
>
> - Output changes:
>   HTML5:
>  Wrap groups of footnotes in an  for easier styling.
>  The CSS rule .footnote-list { display: contents; } can be used to restore
>  the behaviour of custom CSS styles.
> - After package installation, the CLI commands python -m docutils and docutils
>   start the generic command line front end tool.
> - Support parsing "Markdown" input with 3rd party parsers myst, pycmark, or 
> recommonmark.
> - The default values for the "pep-references", "rfc-base-url", and 
> "python-home"
>   configuration settings now use the "https:" scheme. The PEP-writer 
> template's
>   header is updated to fix links and resemble the header of official PEPs.
> - Various bugfixes and improvements (see HISTORY).
>
> Signed-off-by: Wang Mingyu 
> ---
>  .../{python3-docutils_0.18.1.bb => python3-docutils_0.19.bb}  | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>  rename meta/recipes-devtools/python/{python3-docutils_0.18.1.bb => 
> python3-docutils_0.19.bb} (62%)
>
> diff --git a/meta/recipes-devtools/python/python3-docutils_0.18.1.bb 
> b/meta/recipes-devtools/python/python3-docutils_0.19.bb
> similarity index 62%
> rename from meta/recipes-devtools/python/python3-docutils_0.18.1.bb
> rename to meta/recipes-devtools/python/python3-docutils_0.19.bb
> index e4ddd01978..7ae93ab557 100644
> --- a/meta/recipes-devtools/python/python3-docutils_0.18.1.bb
> +++ b/meta/recipes-devtools/python/python3-docutils_0.19.bb
> @@ -2,9 +2,9 @@ SUMMARY = "Docutils is a modular system for processing 
> documentation into useful
>  HOMEPAGE = "http://docutils.sourceforge.net";
>  SECTION = "devel/python"
>  LICENSE = "PSF-2.0 & BSD-2-Clause & GPL-3.0-only"
> -LIC_FILES_CHKSUM = "file://COPYING.txt;md5=fecee07ad8df9116e1f739e2ed2ea513"
> +LIC_FILES_CHKSUM = "file://COPYING.txt;md5=41001b296a89bb2780bbe306e947ecee"
>
> -SRC_URI[sha256sum] = 
> "679987caf361a7539d76e584cbeddc311e3aee937877c87346f31debc63e9d06"
> +SRC_URI[sha256sum] = 
> "33995a6753c30b7f577febfc2c50411fec6aac7f7ffeb7c4cfe5991072dcf9e6"
>
>  inherit pypi setuptools3
>
> --
> 2.25.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168276): 
https://lists.openembedded.org/g/openembedded-core/message/168276
Mute This Topic: https://lists.openembedded.org/mt/92472708/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][master][kirkstone][PATCH] cve-check.bbclass: Add anonymous function to get patched CVEs from recipe

[akash hadke via lists.openembedded.org]

Actually, I wanted to get all patched CVE numbers from a recipe in one 
variable, and the value of that variable will be used in other tasks. And for 
this purpose, I used the anonymous function because without it I will not be 
able to get the value of CVE_PATCHED in other tasks.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168275): 
https://lists.openembedded.org/g/openembedded-core/message/168275
Mute This Topic: https://lists.openembedded.org/mt/92329911/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [oe] [meta-zephyr] build broken with current oe-core master

[Bartosz Golaszewski]

On Tue, Jul 19, 2022 at 12:10 AM Jon Mason  wrote:
>
> On Mon, Jul 18, 2022 at 4:06 PM Khem Raj  wrote:
> >
> > Can you try something like this
> >
> > diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc
> > b/meta/recipes-devtools/gcc/gcc-runtime.inc
> > index 5d74e4494d..61d5bf6058 100644
> > --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
> > +++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
> > @@ -68,8 +68,7 @@ do_configure () {
> > # libstdc++ isn't built yet so CXX would error not able to find it
> > which breaks stdc++'s configure
> > # tests. Create a dummy empty lib for the purposes of configure.
> > mkdir -p ${WORKDIR}/dummylib
> > -   touch ${WORKDIR}/dummylib/dummylib.c
> > -   ${CC} ${WORKDIR}/dummylib/dummylib.c -shared -o
> > ${WORKDIR}/dummylib/libstdc++.so
> > +   ${CC} -nostartfiles -shared -x c /dev/null -o
> > ${WORKDIR}/dummylib/libstdc++.so
> > for d in libgcc ${RUNTIMETARGET}; do
> > echo "Configuring $d"
> > rm -rf ${B}/${TARGET_SYS}/$d/
> >
> >
> > and see if it helps ?
>
> That appears to work for the 2 zephyr machines in meta-arm
>

This still fails for arduino nano 33 ble:

| checking for dirent.h... no
| checking sys/statvfs.h usability... no
| checking sys/statvfs.h presence... no
| checking for sys/statvfs.h... no
| checking utime.h usability... yes
| checking utime.h presence... yes
| checking for utime.h... yes
| checking whether to build Filesystem TS support... no
| checking for struct dirent.d_type... no
| checking for realpath... no
| checking for utimensat... no
| checking for utime... no
| checking for lstat... no
| checking for struct stat.st_mtim.tv_nsec... yes
| checking for fchmod... yes
| checking for fchmodat... yes
| checking for sendfile that can copy files... no
| checking for link... yes
| checking for readlink... yes
| checking for symlink... yes
| checking for truncate... yes
| checking for fdopendir... no
| checking for dirfd... no
| checking for unlinkat... yes
| checking __sync extensions... yes
| checking link.h usability... no
| checking link.h presence... no
| checking for link.h... no
| checking for fcntl... configure: error: Link tests are not allowed
after GCC_NO_EXECUTABLES.
| WARNING: exit code 1 from a shell command.
ERROR: Task 
(/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/gcc/gcc-runtime_12.1.bb:do_configure)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 795 tasks of which 774 didn't need to
be rerun and 1 failed.

Summary: 1 task failed:
  
/home/brgl/workspace/zephyr-yocto/sources/poky/meta/recipes-devtools/gcc/gcc-runtime_12.1.bb:do_configure
Summary: There was 1 ERROR message, returning a non-zero exit code.

Bart

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168274): 
https://lists.openembedded.org/g/openembedded-core/message/168274
Mute This Topic: https://lists.openembedded.org/mt/92467688/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-