All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: marleen.vos@essensium.com
Cc: Marleen Vos <marleen.vos@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/avenger96_defconfig: fix CI build error due to a missing package for uboot
Date: Tue, 14 May 2024 17:49:14 +0200	[thread overview]
Message-ID: <ZkOH-mlXOt42gkGG@landeda> (raw)
In-Reply-To: <20240514101244.1067520-1-marleen.vos@mind.be>

Marleen, All,

On 2024-05-14 12:12 +0200, Marleen Vos via buildroot spake thusly:
> From: Marleen Vos <marleen.vos@mind.be>
> 
> This refers to https://gitlab.com/buildroot.org/buildroot/-/jobs/6813124907
> The build error referenced in that link is:
> 
> error: command 'swig' failed: No such file or directory
> make[4]: *** [scripts/dtc/pylibfdt/Makefile:33: rebuild] Error 1
> make[3]: *** [scripts/Makefile.build:397: scripts/dtc/pylibfdt] Error 2
> make[2]: *** [Makefile:2014: scripts_dtc] Error 2
> make[1]: *** [package/pkg-generic.mk:283: /builds/buildroot.org/buildroot/output/build/uboot-2024.01/.stamp_built] Error 2
> make: *** [Makefile:82: _all] Error 2
> 
> BR2_TARGET_UBOOT_NEEDS_PYLIBFDT is added to the avenger96_defconfig in order to resolve the issue
> 
> Signed-off-by: Marleen Vos <marleen.vos@mind.be>

Applied to master, thanks.

While you're looking at this defconfig, could look into adding hashes
for the custom versions it uses? See for example:
    5efa5e9023 configs/armadeus_apf27: add hashes for Linux/U-Boot

Regards,
Yann E. MORIN.

> ---
>  configs/avenger96_defconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/configs/avenger96_defconfig b/configs/avenger96_defconfig
> index f73b654dc8..64cfb3c2b0 100644
> --- a/configs/avenger96_defconfig
> +++ b/configs/avenger96_defconfig
> @@ -47,6 +47,7 @@ BR2_TARGET_UBOOT_FORMAT_DTB=y
>  BR2_TARGET_UBOOT_FORMAT_CUSTOM=y
>  BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME="u-boot-nodtb.bin"
>  BR2_TARGET_UBOOT_CUSTOM_MAKEOPTS="DEVICE_TREE=stm32mp15xx-dhcor-avenger96"
> +BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y
>  
>  # Additional tools
>  BR2_PACKAGE_HOST_GENIMAGE=y
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-05-14 15:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 10:12 [Buildroot] [PATCH 1/1] configs/avenger96_defconfig: fix CI build error due to a missing package for uboot Marleen Vos via buildroot
2024-05-14 15:49 ` Yann E. MORIN [this message]

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=ZkOH-mlXOt42gkGG@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=marleen.vos@essensium.com \
    --cc=marleen.vos@mind.be \
    /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.