From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: [PATCH v2 1/7] u-boot: inject debian multi-arch config
Date: Thu, 16 Mar 2023 07:49:07 +0300 [thread overview]
Message-ID: <2213612.vFx2qVVIhK@home> (raw)
In-Reply-To: <20230211092152.949442-2-felix.moessbauer@siemens.com>
In the email from Saturday, 11 February 2023 12:21:46 +03 user Felix Moessbauer wrote:
> For more complex u-boot configurations, correct debian multi-arch header
> paths have to be set for both the host (~ISAR target) as well as the build
> architecture (~ISAR host). In addition, the bits per long have to be set for
> userspace ABI. For debian, this always corresponds to the
> DEB_HOST_ARCH_BITS.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/recipes-bsp/u-boot/files/debian/rules.tmpl | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/meta/recipes-bsp/u-boot/files/debian/rules.tmpl b/meta/recipes-bsp/u-boot/files/debian/rules.tmpl
When running in CI, patch v1 causes build issues with u-boot on some armhf (at least) machines. A piece of `build/tmp/work/debian-bullseye-armhf/u-boot-stm32mp15x/2020.10-r0/temp/log.do_dpkg_build` log:
```
#
# configuration written to .config
#
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
/usr/bin/make -j 8 u-boot.stm32
make[2]: Entering directory '/<<PKGBUILDDIR>>'
scripts/kconfig/conf --syncconfig Kconfig
UPD include/config.h
CFG u-boot.cfg
GEN include/autoconf.mk.dep
In file included from /usr/arm-linux-gnueabihf/include/features.h:485,
from /usr/arm-linux-gnueabihf/include/errno.h:25,
from ./include/common.h:17:
/usr/include/arm-linux-gnueabihf/gnu/stubs.h:7:11: fatal error: gnu/stubs-soft.h: No such file or directory
7 | # include <gnu/stubs-soft.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
In file included from /usr/arm-linux-gnueabihf/include/features.h:485,
from /usr/arm-linux-gnueabihf/include/errno.h:25,
from ./include/common.h:17:
/usr/include/arm-linux-gnueabihf/gnu/stubs.h:7:11: fatal error: gnu/stubs-soft.h: No such file or directory
7 | # include <gnu/stubs-soft.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [scripts/Makefile.autoconf:77: u-boot.cfg] Error 1
```
next prev parent reply other threads:[~2023-03-16 4:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 9:21 [PATCH v2 0/7] Add BSP for StarFiveTech VisionFive2 Risc-V board Felix Moessbauer
2023-02-11 9:21 ` [PATCH v2 1/7] u-boot: inject debian multi-arch config Felix Moessbauer
2023-03-16 4:49 ` Uladzimir Bely [this message]
2023-03-16 7:33 ` Jan Kiszka
2023-02-11 9:21 ` [PATCH v2 2/7] starfive-visionfive2: package u-boot Felix Moessbauer
2023-02-11 9:21 ` [PATCH v2 3/7] starfive-visionfive2: package opensbi firmware Felix Moessbauer
2023-02-13 6:39 ` Moessbauer, Felix
2023-02-11 9:21 ` [PATCH v2 4/7] starfive-visionfive2: add BSP kernel Felix Moessbauer
2023-02-11 9:21 ` [PATCH v2 5/7] starfive-visionfive2: create u-boot-spl firmware Felix Moessbauer
2023-02-11 9:21 ` [PATCH v2 6/7] starfive-visionfive2: create u-boot-spl FIT image Felix Moessbauer
2023-02-11 9:21 ` [PATCH v2 7/7] starfive-visionfive2: add machine Felix Moessbauer
2023-03-14 15:31 ` [PATCH v2 0/7] Add BSP for StarFiveTech VisionFive2 Risc-V board Schaffner, Tobias
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=2213612.vFx2qVVIhK@home \
--to=ubely@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.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