From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: optee-ftpm-stm32mp15x sometimes fails to build
Date: Thu, 20 Jul 2023 08:22:27 +0200 [thread overview]
Message-ID: <835e36ac-8f38-9b7b-44b7-721f873daae0@siemens.com> (raw)
In-Reply-To: <b9d382bd6d1e7f4d7b27d6062a000b6ca3ea5449.camel@ilbers.de>
On 20.07.23 07:11, Uladzimir Bely wrote:
> We are currently experiencing sporadic CI full build failures of optee-
> ftpm-stm32mp15x package ("nocross" build):
>
> ```
> make[3]: *** No rule to make target
> 'lib/wolf/wolf_symlink/wolfcrypt/src/aes.c', needed by
> '../out/fTPM/./lib/wolf/wolf_symlink/wolfcrypt/src/aes.o'. Stop.
> ```
>
> I'm just wondering if this is something known and there might be a fix,
> or we should investigate it.
>
I've built that now a couple of times, but only on 6 cores, and there
this never occurred. Possibly a parallel build bug in this wolfssl thing.
> For details, I'm attaching two build logs from `tmp/work/debian-
> bullseye-armhf/optee-os-stm32mp15x/3.21.0-r0/`. They are both received
> for the same isar revision, but one is OK while another got failed.
>
> Initially, this was observed on top of "imager-schroot" + "base-apt"
> patchsets, but it also appears to happen with current "next" branch.
Let me see if I can reproduce locally, maybe outside of Isar.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2023-07-20 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 5:11 Uladzimir Bely
2023-07-20 6:22 ` Jan Kiszka [this message]
2023-07-20 9:19 ` Jan Kiszka
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=835e36ac-8f38-9b7b-44b7-721f873daae0@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.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