From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Fabio Estevam <festevam@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/freescale_imx8q*: uboot needs openssl
Date: Sun, 4 Aug 2024 23:06:35 +0200 [thread overview]
Message-ID: <20240804230635.7531f13a@windsurf> (raw)
In-Reply-To: <20240804161557.1319569-1-ju.o@free.fr>
On Sun, 4 Aug 2024 18:15:57 +0200
Julien Olivain <ju.o@free.fr> wrote:
> Those defconfigs were recently bumped to NXP BSP lf-6.6.23-2.0.0.
>
> NXP BSP U-Boot version lf-6.6.23-2.0.0 is based on upstream
> version 2024.04. This version now requires OpenSSL.
>
> Those defconfigs are failing in uboot build, with output:
>
> In file included from tools/imagetool.h:24,
> from tools/imagetool.c:8:
> include/image.h:1471:12: fatal error: openssl/evp.h: No such file or directory
> 1471 | # include <openssl/evp.h>
> | ^~~~~~~~~~~~~~~
>
> This commit fixes the issue by adding
> BR2_TARGET_UBOOT_NEEDS_OPENSSL=y in all the impacted defconfigs.
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Note: Patch tested in Gitlab CI pipeline:
> https://gitlab.com/jolivain/buildroot/-/pipelines/1400170073
> ---
> configs/freescale_imx8qmmek_defconfig | 1 +
> configs/freescale_imx8qxpmek_defconfig | 1 +
> 2 files changed, 2 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-04 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 16:15 [Buildroot] [PATCH 1/1] configs/freescale_imx8q*: uboot needs openssl Julien Olivain
2024-08-04 21:06 ` Thomas Petazzoni via buildroot [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=20240804230635.7531f13a@windsurf \
--to=buildroot@buildroot.org \
--cc=festevam@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.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 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.