All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Marcus Hoffmann <marcus.hoffmann@othermo.de>
Cc: Gilles Talis <gilles.talis@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] configs/friendlyarm_nanopi_r2s_defconfig: uboot needs openssl
Date: Thu, 17 Feb 2022 22:43:14 +0100	[thread overview]
Message-ID: <20220217214314.GL522310@scaer> (raw)
In-Reply-To: <20220217155549.1084829-2-marcus.hoffmann@othermo.de>

Marcus, All

On 2022-02-17 16:55 +0100, Marcus Hoffmann spake thusly:
> Fixes the following compile error:
> 
> In file included from include/bootm.h:10,
>                  from tools/image-host.c:12:
> include/image.h:1178:12: fatal error: openssl/evp.h: No such file or directory
>  1178 | #  include <openssl/evp.h>
>       |            ^~~~~~~~~~~~~~~
> compilation terminated.
> 
> Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/2103784200
> 
> Signed-off-by: Marcus Hoffmann <marcus.hoffmann@othermo.de>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  configs/friendlyarm_nanopi_r2s_defconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/configs/friendlyarm_nanopi_r2s_defconfig b/configs/friendlyarm_nanopi_r2s_defconfig
> index 818c847f4b..ce252a5d76 100644
> --- a/configs/friendlyarm_nanopi_r2s_defconfig
> +++ b/configs/friendlyarm_nanopi_r2s_defconfig
> @@ -30,6 +30,7 @@ BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2021.10"
>  BR2_TARGET_UBOOT_BOARD_DEFCONFIG="nanopi-r2s-rk3328"
>  BR2_TARGET_UBOOT_NEEDS_DTC=y
>  BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y
> +BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
>  BR2_TARGET_UBOOT_NEEDS_ATF_BL31=y
>  BR2_TARGET_UBOOT_NEEDS_ATF_BL31_ELF=y
>  BR2_TARGET_UBOOT_FORMAT_CUSTOM=y
> -- 
> 2.25.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

  parent reply	other threads:[~2022-02-17 21:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 15:55 [Buildroot] [PATCH v2 0/2] defconfig fixes Marcus Hoffmann
2022-02-17 15:55 ` [Buildroot] [PATCH v2 1/2] configs/friendlyarm_nanopi_r2s_defconfig: uboot needs openssl Marcus Hoffmann
2022-02-17 15:58   ` Giulio Benetti
2022-02-17 21:43   ` Yann E. MORIN [this message]
2022-02-17 15:55 ` [Buildroot] [PATCH v2 2/2] board/orangepi/orangepi-rk3399/genimage: fix partition types for gpt Marcus Hoffmann
2022-02-17 15:58   ` Giulio Benetti
2022-02-17 21:44   ` Yann E. MORIN
2022-02-17 21:47     ` Marcus Hoffmann
2022-02-17 21:50     ` Giulio Benetti
2022-03-05 15:01   ` Arnout Vandecappelle

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=20220217214314.GL522310@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=gilles.talis@gmail.com \
    --cc=marcus.hoffmann@othermo.de \
    /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.