From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] telit_evk_pro3_defconfig fails to build
Date: Sat, 5 Nov 2016 15:20:13 +0100 [thread overview]
Message-ID: <20161105152013.615d71d7@free-electrons.com> (raw)
Hello Fabio,
Back in 2013, you contributed telit_evk_pro3_defconfig to Buildroot.
Unfortunately, this defconfig no longer builds: the Linux kernel
version used is too old to build with gcc 5.x.
Do you still have access to this HW platform? If so, can you contribute
a patch to update the defconfig? If you're no longer interested by this
platform, we can also decide to remove its defconfig.
You can see the full build log at
http://free-electrons.com/~thomas/pub/buildroot-defconfigs/telit_evk_pro3_defconfig.log.FAIL.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next reply other threads:[~2016-11-05 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 14:20 Thomas Petazzoni [this message]
2016-11-07 17:30 ` [Buildroot] telit_evk_pro3_defconfig fails to build Fabio Porcedda
2016-11-07 20:53 ` Thomas Petazzoni
2016-12-21 21:02 ` Peter Korsgaard
2016-12-22 17:30 ` Fabio Porcedda
2016-12-23 6:36 ` Peter Korsgaard
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=20161105152013.615d71d7@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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