All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Mattijs Korpershoek <mkorpershoek@kernel.org>,
	u-boot@lists.denx.de, Igor Opaniuk <igor.opaniuk@gmail.com>
Cc: Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 0/2] libavb: update to AOSP 1.3.0
Date: Mon, 27 Jul 2026 09:38:16 +0200	[thread overview]
Message-ID: <87fr147uhj.fsf@kernel.org> (raw)
In-Reply-To: <178489889597.185493.15058174427127039022.b4-ty@b4>

Hi Igor,

On Fri, Jul 24, 2026 at 15:14, Mattijs Korpershoek <mkorpershoek@kernel.org> wrote:

> Hi,
>
> On Sun, 12 Jul 2026 16:07:09 +0200, Igor Opaniuk wrote:
>> The vendored libavb under lib/libavb/ has been frozen at a ~2019 AOSP
>> snapshot (AVB version 1.1.0) for about six years. A v1.1.0 library
>> rejects any vbmeta whose required libavb minor version is greater than 1
>> with UNSUPPORTED_VERSION, so an image signed by a newer avbtool that uses
>> a 1.2/1.3 feature fails to verify. This series re-syncs the library to
>> version 1.3.0 and picks up the accumulated upstream fixes.
>> 
>> [...]
>
> Thanks, Applied to https://git.u-boot-project.org/u-boot/custodians/u-boot-dfu (u-boot-dfu)
>
> [1/2] libavb: update to AOSP 1.3.0
>       https://git.u-boot-project.org/u-boot/custodians/u-boot-dfu/-/commit/963ec1af8a4b6d5d185ad289dbb0178ef2199d5f
> [2/2] doc: android: refresh AVB provenance and pin libavb reference
>       https://git.u-boot-project.org/u-boot/custodians/u-boot-dfu/-/commit/f8aba1d9c54c19a7c863bd5b4d035aa46a10bab0

This seems to break sandbox build/test. See:
https://git.u-boot-project.org/u-boot/custodians/u-boot-dfu/-/jobs/48391

Some relevant part of the logs:
$ tools/buildman/buildman -o ${UBOOT_TRAVIS_BUILD_DIR} -w -E -W -e --board ${TEST_PY_BD} ${OVERRIDE}
Building current source for 1 boards (1 thread, 112 jobs per thread)
   sandbox:  +   sandbox
+lib/libavb/avb_cmdline.c:371:48: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
+  371 | AvbCmdlineSubstList* avb_new_cmdline_subst_list() {
+      |                                                ^
+      |                                                 void
+1 error generated.
+make[3]: *** [scripts/Makefile.build:272: lib/libavb/avb_cmdline.o] Error 1
+make[2]: *** [scripts/Makefile.build:497: lib/libavb] Error 2
+make[1]: *** [Makefile:2210: lib] Error 2
+make: *** [Makefile:189: __sub-make] Error 2
    0    0    1 /1              sandbox

Could you please send me a fix for this?
If not, I'll have to drop the patches from my tree in a couple of days.

Thanks
Mattijs

  reply	other threads:[~2026-07-27  7:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-12 14:07 [PATCH 0/2] libavb: update to AOSP 1.3.0 Igor Opaniuk
2026-07-12 14:07 ` [PATCH 1/2] " Igor Opaniuk
2026-07-24 12:34   ` Mattijs Korpershoek
2026-07-12 14:07 ` [PATCH 2/2] doc: android: refresh AVB provenance and pin libavb reference Igor Opaniuk
2026-07-24 12:35   ` Mattijs Korpershoek
2026-07-15 16:28 ` [PATCH 0/2] libavb: update to AOSP 1.3.0 Igor Opaniuk
2026-07-24 13:14 ` Mattijs Korpershoek
2026-07-27  7:38   ` Mattijs Korpershoek [this message]
2026-07-27  9:31     ` Igor Opaniuk
2026-07-27 12:30       ` Mattijs Korpershoek

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=87fr147uhj.fsf@kernel.org \
    --to=mkorpershoek@kernel.org \
    --cc=igor.opaniuk@gmail.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.