All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vincent Stehlé" <vincent.stehle@arm.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/qemu_arm_ebbr: linux needs host-openssl
Date: Mon, 2 Sep 2024 18:08:55 +0200	[thread overview]
Message-ID: <ZtXjFyjZbhF8q014@debian> (raw)
In-Reply-To: <87o75a152u.fsf@dell.be.48ers.dk>

On Fri, Aug 30, 2024 at 04:02:49PM +0200, Peter Korsgaard wrote:
> >>>>> "Vincent" == Vincent Stehlé <vincent.stehle@arm.com> writes:
> 
>  > The kernel build needs host-openssl; add it to the configuration.
>  > In practice the documented build recipe works fine and the build failures
>  > can only be seen with highly parallel builds using per-package directories.
> 
>  > This fixes the following compilation error:
> 
>  >   certs/extract-cert.c:21:10: fatal error: openssl/bio.h: No such file or directory
> 
>  > Fixes: 7115ab39189a6c660745267d8bf0bf41cf8b3db7
> 
> Are you sure? Isn't it from the bump to 6.6.32 in commit d037d9c2d63e9c
> (configs/qemu: Update defconfigs to Linux 6.6.32)?

Hi Peter,

Yes; I did some more tests to confirm and I am pretty sure now:

        Commit  Result  Comments
  ------------  ------  --------
  7115ab39189a  Broken  (I needed to configure with gcc 12 to build.)
  44a6b7866c95  Broken
  d037d9c2d63e  Broken

With BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y added, all three commits build fine.

I tested with:

  $ make qemu_arm_ebbr_defconfig
  $ make linux

...on a host with no openssl (I use a chroot for that purpose).

Best regards,
Vincent.

> 
> -- 
> Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-09-02 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22  9:37 [Buildroot] [PATCH] configs/qemu_arm_ebbr: linux needs host-openssl Vincent Stehlé
2024-07-22 12:08 ` Thomas Petazzoni via buildroot
2024-08-30 14:02 ` Peter Korsgaard
2024-09-02 16:08   ` Vincent Stehlé [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=ZtXjFyjZbhF8q014@debian \
    --to=vincent.stehle@arm.com \
    --cc=buildroot@buildroot.org \
    --cc=peter@korsgaard.com \
    --cc=romain.naour@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.