Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Gavini, Sumanth" <sumanth.gavini@windriver.com>
To: "Marko, Peter" <Peter.Marko@siemens.com>,
	Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"patchtest@automation.yoctoproject.org"
	<patchtest@automation.yoctoproject.org>
Cc: "alex.kanavin@gmail.com" <alex.kanavin@gmail.com>,
	"mattware@cisco.com" <mattware@cisco.com>,
	"esparlin@cisco.com" <esparlin@cisco.com>,
	"MacLeod, Randy" <Randy.MacLeod@windriver.com>
Subject: Re: [OE-core] [PATCH v2] rpm: 6.0.2 -> 6.1.0
Date: Mon, 16 Nov 2026 20:16:02 +0000	[thread overview]
Message-ID: <93e45ea7-db55-4839-aca6-4e7ddbfd86cc@windriver.com> (raw)
In-Reply-To: <AS8PR10MB50736C20744CB290C0DCF5DFFD7C2@AS8PR10MB5073.EURPRD10.PROD.OUTLOOK.COM>

On 11/16/2026 6:57 AM, Marko, Peter wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
>> -----Original Message-----
>> From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>> Sent: Monday, November 16, 2026 1:39 PM
>> To: sumanth.gavini@windriver.com; openembedded-
>> core@lists.openembedded.org; patchtest@automation.yoctoproject.org
>> Cc: alex.kanavin@gmail.com; mattware@cisco.com; esparlin@cisco.com; Marko,
>> Peter (FT D EU SK BFS1) <Peter.Marko@siemens.com>;
>> randy.macleod@windriver.com
>> Subject: Re: [OE-core] [PATCH v2] rpm: 6.0.2 -> 6.1.0
>>
>> On Mon Nov 16, 2026 at 4:37 AM CET, Sumanth Gavini via openembedded-core
>> wrote:
>>> * Switch SRC_URI to the rpm-6.1.x branch.
>>> * COPYING checksum changed, upstream added an SPDX clarification.
>>>    The license is unchanged.
>>> * rpm-setup-autosign moved from ${libdir}/rpm to ${bindir}, add it to
>>>    rpm-build. rpmuncompress moved too and stays in the rpm package.
>>> * Refresh 0001-Do-not-hardcode-lib-rpm-as-the-installation-path-for.patch,
>>>    it applied with fuzz 2 after upstream added the WITH_WEBSITE option.
>>>    The other patches apply cleanly.
>>>
>>> License-Update: COPYING now has an SPDX clarification note, license
>> unchanged
>>>
>>> Signed-off-by: Sumanth Gavini <sumanth.gavini@windriver.com>
>>> ---
>>
>> Hi Sumanth,
>>
>> Thanks for the update, but it looks like we sometimes have build
>> failures:
>>
>> ERROR: rpm-native-1_6.1.0-r0 do_compile: Execution of '/srv/pokybuild/yocto-
>> worker/qemuarm-tc/build/build-st-2526906/tmp/work/x86_64-linux/rpm-
>> native/6.1.0/temp/run.do_compile.2871087' failed with exit code 2
>> NOTE: recipe mesa-tools-native-2_26.2.4-r0: task do_create_spdx: Succeeded
>> NOTE: CPU pressure (>20000.0us) is limiting task startup
>> NOTE: No pressure is limiting task startup
>> NOTE: Running task 1924 of 1996 (virtual:native:/srv/pokybuild/yocto-
>> worker/qemuarm-tc/build/layers/openembedded-core/meta/recipes-
>> graphics/mesa/mesa.bb:do_create_spdx)
>> NOTE: recipe python3-pygments-native-2.21.0-r0: task do_create_spdx: Started
>> NOTE: recipe mesa-native-2_26.2.4-r0: task do_create_spdx: Started
>> NOTE: recipe python3-pygments-native-2.21.0-r0: task do_create_spdx:
>> Succeeded
>> NOTE: recipe mesa-native-2_26.2.4-r0: task do_create_spdx: Succeeded
>> NOTE: CPU pressure (>20000.0us) is limiting task startup
>> NOTE: recipe glibc-2.44+git-r0: task do_configure: Succeeded
>> ERROR: Logfile of failure stored in: /srv/pokybuild/yocto-worker/qemuarm-
>> tc/build/build-st-2526906/tmp/work/x86_64-linux/rpm-
>> native/6.1.0/temp/log.do_compile.2871087
>> Log data follows:
>> ...
>> | /srv/pokybuild/yocto-worker/qemuarm-tc/build/build-st-
>> 2526906/tmp/work/x86_64-linux/rpm-native/6.1.0/sources/rpm-
>> 6.1.0/lib/headerfmt.cc:7:10: fatal error: format: No such file or directory
>> |     7 | #include <format>
>> |       |          ^~~~~~~~
>> | compilation terminated.
>> | make[2]: *** [lib/CMakeFiles/librpm.dir/build.make:154:
>> lib/CMakeFiles/librpm.dir/headerfmt.cc.o] Error 1
>> | make[2]: *** Waiting for unfinished jobs....
>> | make[2]: Leaving directory '/srv/pokybuild/yocto-worker/qemuarm-tc/build/build-
>> st-2526906/tmp/work/x86_64-linux/rpm-native/6.1.0/build'
>> | make[1]: *** [CMakeFiles/Makefile2:700: lib/CMakeFiles/librpm.dir/all] Error 2
>> | make[1]: Leaving directory '/srv/pokybuild/yocto-worker/qemuarm-tc/build/build-
>> st-2526906/tmp/work/x86_64-linux/rpm-native/6.1.0/build'
>> | make: *** [Makefile:136: all] Error 2
>> |
>> | WARNING: exit code 2 from a shell command.
>> NOTE: recipe rpm-native-1_6.1.0-r0: task do_compile: Failed
>>
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/42/builds/5000
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/66/builds/5121
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/5369
>>
>> All these build were on debian 12 workers, so there might be some issues
>> with that host distribution. I'm launching a genericx86-64 build on a
>> debian 12 worker, to see if it reproduces easily.
> 
> This one is clear, I have seen that couple times already on our Debian 12 workers when developers are eager to use new c++ features.
> Debian 12 has gcc 12.2, while <format> was introduced only in gcc 13.
> So the build cannot work with Debian 12 host gcc anymore.
> 
> Debian 12 LTS EOL in July 2028, so still almost 2 years ahead of us.
> So something needs to be done, like using buildtools-tarball or patching rpm.
> 
> Peter
> 
>>
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/5047
>>
>> Can you have a look at the issue?
>>
>> Thanks,
>> Mathieu
>>
>> --
>> Mathieu Dubois-Briand, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
> 
Hi Mathieu, Peter,

Thanks for the report. I will look into the issue and send a v3.

-- 
# Sumanth Gavini
# Wind River Linux

      reply	other threads:[~2026-11-16 20:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14  4:17 [PATCH] rpm: 6.0.2 -> 6.1.0 Sumanth Gavini
2026-11-14  4:31 ` Patchtest results for " patchtest
2026-11-16  3:37   ` [PATCH v2] " Sumanth Gavini
2026-11-16 12:38     ` [OE-core] " Mathieu Dubois-Briand
2026-11-16 12:57       ` Marko, Peter
2026-11-16 20:16         ` Gavini, Sumanth [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=93e45ea7-db55-4839-aca6-4e7ddbfd86cc@windriver.com \
    --to=sumanth.gavini@windriver.com \
    --cc=Peter.Marko@siemens.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --cc=esparlin@cisco.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=mattware@cisco.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patchtest@automation.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox