From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: Fabio Estevam <festevam@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/2] configs/imx7dpico: Select BR2_TARGET_UBOOT_NEEDS_OPENSSL
Date: Thu, 03 Oct 2024 13:13:36 +0200 [thread overview]
Message-ID: <87wmipmobj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <d3159ae8-45a0-4957-95e7-3571f3fa6ccf@mind.be> (Arnout Vandecappelle via buildroot's message of "Sat, 14 Sep 2024 18:31:40 +0200")
>>>>> "Arnout" == Arnout Vandecappelle via buildroot <buildroot@buildroot.org> writes:
> On 14/09/2024 13:43, Fabio Estevam wrote:
>> Select BR2_TARGET_UBOOT_NEEDS_OPENSSL to fix the following
>> build warning:
>> include/image.h:1471:12: fatal error: openssl/evp.h: No such file or
>> directory
>> 1471 | # include <openssl/evp.h>
>> Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/7803199869
>> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> Applied both to master, thanks.
> If you're actively working with these boards, perhaps you could also
> add hashes for U-Boot and kernel and enable
> BR2_DOWNLOAD_FORCE_CHECK_HASHES?
NIT: This is a build ERROR, not a warning and it was presumably
introduced by your recent u-boot bump in commit 8cf677f4
(configs/imx7dpico: bump kernel and U-Boot version). It would be great
to mention such things in future patches as it helps with figuring out
what needs to be backported to the stable branches.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-03 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 11:43 [Buildroot] [PATCH 1/2] configs/imx7dpico: Select BR2_TARGET_UBOOT_NEEDS_OPENSSL Fabio Estevam
2024-09-14 11:43 ` [Buildroot] [PATCH 2/2] configs/mx6udoo: " Fabio Estevam
2024-09-14 16:31 ` [Buildroot] [PATCH 1/2] configs/imx7dpico: " Arnout Vandecappelle via buildroot
2024-10-03 11:13 ` Peter Korsgaard [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=87wmipmobj.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=festevam@gmail.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.