From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/atmel_sama5d27_som1: bump to linux4sam_6.1
Date: Tue, 30 Jul 2019 14:21:42 +0200 [thread overview]
Message-ID: <20190730142142.7ed8ec91@windsurf> (raw)
In-Reply-To: <2915f499-4364-e4c7-9c19-b45892568565@koncepto.io>
Hello Pierre-Jean,
On Sun, 28 Jul 2019 14:33:27 +0200
Pierre-Jean Texier <pjtexier@koncepto.io> wrote:
> Le 26/07/2019 ? 16:27, Thomas Petazzoni a ?crit?:
> > Following this bump, the atmel_sama5d27_som1_ek_mmc_dev_defconfig no
> > longer builds:
> >
> > https://gitlab.com/buildroot.org/buildroot/-/jobs/259847527
> >
> > You need to add:
> >
> > BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
> >
> > Could you test this and send a patch ?
>
> Interesting, I hadn't encountered this problem.
> I'll send a patch to fix this issue.
If you have the OpenSSL development package installed on your system,
then indeed you don't see the problem. However, the defconfigs are
tested in a Docker container, with just the minimal dependencies needed
by Buildroot to run, and these dependencies do not include OpenSSL
development files. This explains why you have not seen the issue.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-07-30 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 16:21 [Buildroot] [PATCH] configs/atmel_sama5d27_som1: bump to linux4sam_6.1 Pierre-Jean Texier
2019-07-10 16:21 ` [Buildroot] [PATCH] configs/atmel_sama5d27_som1: add rng-tools package Pierre-Jean Texier
2019-07-11 8:51 ` Ludovic Desroches
2019-07-14 13:14 ` Thomas Petazzoni
2019-07-11 8:51 ` [Buildroot] [PATCH] configs/atmel_sama5d27_som1: bump to linux4sam_6.1 Ludovic Desroches
2019-07-14 13:14 ` Thomas Petazzoni
2019-07-26 14:27 ` Thomas Petazzoni
2019-07-28 12:33 ` Pierre-Jean Texier
2019-07-30 12:21 ` Thomas Petazzoni [this message]
2019-07-30 18:16 ` Pierre-Jean Texier
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=20190730142142.7ed8ec91@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox