From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Louis Chauvet <louis.chauvet@bootlin.com>,
Sergey Matyukevich <geomatsi@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] boot/arm-trusted-firmware: fix fiptool linking issue on hosts without openssl
Date: Thu, 4 Jan 2024 22:43:07 +0100 [thread overview]
Message-ID: <20240104224307.1b4a0be7@windsurf> (raw)
In-Reply-To: <20240104165634.1215451-1-peter@korsgaard.com>
On Thu, 4 Jan 2024 17:56:33 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/5834758777
>
> Commit e7d16c35a (boot/arm-trusted-firmware: fix the RPATH of fiptool) tried
> to fix the build of host-fiptool, but forgot to pass HOST_CFLAGS.
>
> On hosts without (compatible) openssl development headers, this breaks
> the build when it cannot find the openssl headers:
>
> fiptool_platform.h:19:11: fatal error: openssl/sha.h: No such file or directory
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> boot/arm-trusted-firmware/arm-trusted-firmware.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks a lot for having cooked the patch! 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
next prev parent reply other threads:[~2024-01-04 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 16:56 [Buildroot] [PATCH] boot/arm-trusted-firmware: fix fiptool linking issue on hosts without openssl Peter Korsgaard
2024-01-04 21:43 ` Thomas Petazzoni via buildroot [this message]
2024-01-05 7:30 ` Peter Korsgaard
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=20240104224307.1b4a0be7@windsurf \
--to=buildroot@buildroot.org \
--cc=geomatsi@gmail.com \
--cc=louis.chauvet@bootlin.com \
--cc=peter@korsgaard.com \
--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.