From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/nexbox_a95x: kernel needs host-openssl
Date: Sun, 9 Dec 2018 17:10:56 +0100 [thread overview]
Message-ID: <20181209161056.GD3383@scaer> (raw)
In-Reply-To: <20181209143525.53fc6c6c@windsurf>
Thomas, All,
On 2018-12-09 14:35 +0100, Thomas Petazzoni spake thusly:
> Hello,
>
> On Sun, 9 Dec 2018 10:41:46 +0100, Yann E. MORIN wrote:
> > Fixes: https://gitlab.com/ymorin/buildroot/-/jobs/131924236
> >
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Peter Korsgaard <peter@korsgaard.com>
>
> This defconfig didn't fail here:
>
> https://gitlab.com/buildroot.org/buildroot/-/jobs/131217002
>
> I'm curious to know you have different results. Both builds are using
> the exact same Docker image, so it's a bit confusing what is going on
> here.
>
> Any idea ?
The build you pointed at is dated 2018-12-08, and later that day, Peter
changed that defconfig to use a newer kernel, see:
9f5b07fc64 configs: nexbox_a95x_defconfig: bump to kernel 4.19.8
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-12-09 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 9:41 [Buildroot] [PATCH] configs/nexbox_a95x: kernel needs host-openssl Yann E. MORIN
2018-12-09 13:35 ` Thomas Petazzoni
2018-12-09 16:10 ` Yann E. MORIN [this message]
2018-12-09 16:30 ` Thomas Petazzoni
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=20181209161056.GD3383@scaer \
--to=yann.morin.1998@free.fr \
--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 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.