All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <peter.marko@siemens.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v2] sqlite3: upgrade 3.48.0 -> 3.49.1
Date: Fri, 09 May 2025 13:56:47 +0200	[thread overview]
Message-ID: <D9RM0MAYAXUU.23JI66VXBXKN4@bootlin.com> (raw)
In-Reply-To: <D9RI6IRC16OO.31JTIVJFTPSGC@bootlin.com>

On Fri May 9, 2025 at 10:56 AM CEST, Mathieu Dubois-Briand wrote:
> On Wed May 7, 2025 at 10:17 AM 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
>> * clean B for do_configure as the new Makefiles do not seem to properly
>>   retrigger build if configuration changes
>> * use unstripped binaries for native (non-cross-compile) case
>>
>> Signed-off-by: Peter Marko <peter.marko@siemens.com>
>> ---
>
> Hi Peter,
>
> Thanks for the v2.
>
> I believe we still have some issues with this version. Not fully
> confident, as it seems a bit intermittent and I cannot see a direct link
> between your change and the error. I will try to drop it from my branch
> and see if it does fix the build.
>
> 2025-05-09 06:27:17,644 - oe-selftest - INFO - buildoptions.ArchiverTest.test_arch_work_dir_and_export_source (subunit.RemotedTestCase)
> 2025-05-09 06:27:17,644 - oe-selftest - INFO -  ... FAIL
> ...
> AssertionError: 1 != 0 : 
> Couldn't build xcursortransparenttheme.
> ...
> BrokenPipeError: [Errno 32] Broken pipe
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/1518
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/1468
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/8/builds/1585
>
> Can you have a look at this please?

Just a quick update: I confirm dropping the patch fixed the build.

Best regards,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2025-05-09 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07  8:17 [OE-core][PATCH v2] sqlite3: upgrade 3.48.0 -> 3.49.1 Peter Marko
2025-05-09  8:56 ` Mathieu Dubois-Briand
2025-05-09 11:56   ` Mathieu Dubois-Briand [this message]
2025-05-11 14:57   ` Marko, Peter

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=D9RM0MAYAXUU.23JI66VXBXKN4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.