From: Jan Viktorin <viktorin@rehivetech.com>
To: buildroot@busybox.net
Subject: [Buildroot] olimex_a20_olinuxino_lime2_defconfig fails to build
Date: Sat, 5 Nov 2016 23:23:03 +0100 [thread overview]
Message-ID: <20161105232303.5f86b7af@jvn> (raw)
In-Reply-To: <20161105150007.4a4f8622@free-electrons.com>
On Sat, 5 Nov 2016 15:00:07 +0100
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello Jan,
>
> Last year, you contributed the olimex_a20_olinuxino_lime2_defconfig to
> Buildroot. Unfortunately, this defconfig now fails to build, due to a
> U-Boot version that is too old to build with gcc 5.x.
>
> Since it's using a mainline version of U-Boot, could you have a look at
> bumping the U-Boot version to fix this problem, if you still have
> access to this HW ?
Yes I have. I will try to check it.
Regards
Jan
>
> See
> http://free-electrons.com/~thomas/pub/buildroot-defconfigs/olimex_a20_olinuxino_lime2_defconfig.log.FAIL
> for the full build log.
>
> Thanks!
>
> Thomas
--
Jan Viktorin E-mail: Viktorin at RehiveTech.com
System Architect Web: www.RehiveTech.com
RehiveTech
Brno, Czech Republic
prev parent reply other threads:[~2016-11-05 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 14:00 [Buildroot] olimex_a20_olinuxino_lime2_defconfig fails to build Thomas Petazzoni
2016-11-05 22:23 ` Jan Viktorin [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=20161105232303.5f86b7af@jvn \
--to=viktorin@rehivetech.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