From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <peter.marko@siemens.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v4] sqlite3: upgrade 3.48.0 -> 3.49.1
Date: Mon, 12 May 2025 14:05:22 +0200 [thread overview]
Message-ID: <D9U62TMBWDLE.19I9VEKRPRRC1@bootlin.com> (raw)
In-Reply-To: <20250511150526.2787050-1-peter.marko@siemens.com>
On Sun May 11, 2025 at 5:05 PM CEST, Peter Marko via lists.openembedded.org wrote:
> From: Peter Marko <peter.marko@siemens.com>
>
> Handle CVE-2025-3277, CVE-2025-29087 and CVE-2025-29088.
>
> This update includes major change in how it is built.
> Instead of autotools, autosetup is used.
>
> Autosetup (https://msteveb.github.io/autosetup/) claims to be
> * Replacement for autoconf in many situations
> However it also claims NOT to
> * Intended to replace all possible uses of autoconf
> This means that some autoconf features are not available.
>
> Recipe changes:
> * stop inheriting autotools and define B, do_configure and do_install
> * depend on zlib unconditionally, autoconf cannot be preconfigured in
> similar way as autotools
> * update packageconfig options to match new syntax
> * libedit is detected with ncurses linking options (as seen in
> do_configure log)
> * backport rpaths fix
> * define soname to avoid file-rdeps QA error due to wrong library name
> * add hack to force cross-compilation in native case to link against
> zlib in sysroot and thus avoid crashes when sstate-cache from different
> distro is used
> * clean B for do_configure as the new Makefiles do not seem to properly
> retrigger build if configuration changes
>
> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> ---
Hi Peter,
Thanks for the new version. However I believe we still have an error, in
oe-selftest and build on ARM hosts:
2025-05-12 08:01:13,149 - oe-selftest - INFO - buildoptions.ArchiverTest.test_arch_work_dir_and_export_source (subunit.RemotedTestCase)
2025-05-12 08:01:13,150 - oe-selftest - INFO - ... FAIL
...
2025-05-12 08:01:13,150 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/oe-selftest-debian/build/meta/lib/oeqa/selftest/cases/buildoptions.py", line 191, in test_arch_work_dir_and_export_source
self.assertEqual(res.status, 0, "\nCouldn't build xcursortransparenttheme.\nbitbake output %s" % res.output)
File "/usr/lib/python3.9/unittest/case.py", line 831, in assertEqual
assertion_func(first, second, msg=msg)
File "/usr/lib/python3.9/unittest/case.py", line 824, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 1 != 0 :
Couldn't build xcursortransparenttheme.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/1541
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/1482
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/1482
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-05-12 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 15:05 [OE-core][PATCH v4] sqlite3: upgrade 3.48.0 -> 3.49.1 Peter Marko
2025-05-12 12:05 ` Mathieu Dubois-Briand [this message]
2025-05-16 11:18 ` Marko, Peter
2025-06-22 18:25 ` [PATCH " Guðni Már Gilbert
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=D9U62TMBWDLE.19I9VEKRPRRC1@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
/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