U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Leonard Anderweit <L.Anderweit@phytec.de>
Cc: "festevam@gmail.com" <festevam@gmail.com>,
	"sjg@chromium.org" <sjg@chromium.org>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"upstream@lists.phytec.de" <upstream@lists.phytec.de>,
	"marex@denx.de" <marex@denx.de>
Subject: Re: [PATCH 2/2] CI: Build missing binman tools before binman tests
Date: Tue, 1 Apr 2025 07:52:55 -0600	[thread overview]
Message-ID: <20250401135255.GB5495@bill-the-cat> (raw)
In-Reply-To: <5eb9bf4c4b30bf09fab544081f5733bf278103fe.camel@phytec.de>

[-- Attachment #1: Type: text/plain, Size: 4006 bytes --]

On Tue, Apr 01, 2025 at 11:42:35AM +0000, Leonard Anderweit wrote:
> Hi Fabio,
> 
> Am Dienstag, dem 01.04.2025 um 08:12 -0300 schrieb Fabio Estevam:
> > Hi Leonard,
> > 
> > On Tue, Apr 1, 2025 at 5:46 AM Leonard Anderweit
> > <l.anderweit@phytec.de> wrote:
> > > 
> > > The CI image does not ship with all tools required for the binman
> > > tests.
> > > Have binman build the missing tools.
> > > 
> > > Signed-off-by: Leonard Anderweit <l.anderweit@phytec.de>
> > 
> > I applied this series with Marek's patch on top.
> > 
> > I get the following CI error. Please take a look:
> > 
> > https://source.denx.de/u-boot/custodians/u-boot-imx/-/jobs/1084138/raw
> > 
> > Starting build...
> > 
> > 
> >     0    0    0 /1       -1      (starting)
> > 
> > 
> >     1    0    0 /1              tools-only
> > Completed: 1 total built, 1 newly), duration 0:00:20, rate 0.05
> > Fetching tools:      bootgen bzip2 cbfstool cst fdt_add_pubkey
> > fdtgrep
> > fiptool futility gzip ifwitool lz4 lzma_alone lzop mkeficapsule
> 
> binman now fetches the missing build tools.
> > mkimage openssl xz zstd
> > Fetch: cbfstool
> > - trying method: binary download
> > - downloading:
> > https://drive.google.com/uc?export=download&id=1gxNxRuJgD0Iiy9LAPCSB_0959eJCp98g
> >          0 MiB  [  4%]                                 0 MiB  [
> > 9%]                                 0 MiB  [
> > 14%]                                 0 MiB  [
> > 19%]                                 0 MiB  [
> > 24%]                                 0 MiB  [
> > 29%]                                 0 MiB  [
> > 34%]                                 0 MiB  [
> > 39%]                                 0 MiB  [
> > 44%]                                 0 MiB  [
> > 49%]                                 0 MiB  [
> > 54%]                                 0 MiB  [
> > 58%]                                 0 MiB  [
> > 63%]                                 0 MiB  [
> > 68%]                                 0 MiB  [
> > 73%]                                 1 MiB  [
> > 78%]                                 1 MiB  [
> > 83%]                                 1 MiB  [
> > 88%]                                 1 MiB  [
> > 93%]                                 1 MiB  [
> > 98%]                                 1 MiB
> > [100%]
> > 
> > 
> > - writing to '/home/uboot/.binman-tools/cbfstool'
> > Fetch: cst
> > - trying method: binary download
> > - trying method: build from source
> > - clone git repo
> > 'https://gitlab.apertis.org/pkg/imx-code-signing-tool' to
> > '/tmp/binmanf.enbq4kln'
> > - build target 'all'
> > Exception: Error 2 running 'make -C
> > /tmp/binmanf.enbq4kln/code/obj.linux64/ -j 40 all OSTYPE=linux64
> > ENCRYPTION=yes': make: byacc: No such file or directory
> 
> byacc is still missing here. To solve this, the ci build container
> needs to be rebuild with the first patch of this series.
> Then we need another patch to reference the new ci build container in
> the ci pipeline. After that byacc should be available and cst should
> build without errors.

And updating the container is on me. Since this is for -next, I'll pick
up this series in the next day or two along with some other Dockerfile
changes.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2025-04-01 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01  8:46 [PATCH 1/2] Dockerfile: install byacc Leonard Anderweit
2025-04-01  8:46 ` [PATCH 2/2] CI: Build missing binman tools before binman tests Leonard Anderweit
2025-04-01 11:12   ` Fabio Estevam
2025-04-01 11:42     ` Leonard Anderweit
2025-04-01 13:52       ` Tom Rini [this message]
2025-04-10 17:33 ` (subset) [PATCH 1/2] Dockerfile: install byacc Tom Rini
2025-04-11 19:16 ` Tom Rini

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=20250401135255.GB5495@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=L.Anderweit@phytec.de \
    --cc=festevam@gmail.com \
    --cc=marex@denx.de \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=upstream@lists.phytec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox