From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] freescale_imx31_3stack_defconfig fails to build
Date: Sat, 5 Nov 2016 17:16:36 +0100 [thread overview]
Message-ID: <20161105171636.514e707e@free-electrons.com> (raw)
In-Reply-To: <6234984d-6409-37c1-b050-504775d37c17@bergerie>
Hello,
On Sat, 5 Nov 2016 16:55:34 +0100, Vincent Stehl? wrote:
> > Has one of you access to this platform, and be willing to update this
> > defconfig?
>
> Hi Thomas and Fabio,
>
> I am sorry to say that I don't have access to an i.MX31 PDK anymore. The
> one I used by the time was already a "rare" resource in Freescale France :)
>
> I will try to help repair the build at least.
If this platform is difficult to get access to, and rarely used, then
maybe we should just remove the defconfig in Buildroot? It doesn't make
a lot of sense to have defconfig for platforms that are not in use.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-05 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 13:35 [Buildroot] freescale_imx31_3stack_defconfig fails to build Thomas Petazzoni
2016-11-05 15:05 ` Fabio Estevam
2016-11-05 15:26 ` Thomas Petazzoni
2016-11-05 15:27 ` Fabio Estevam
[not found] ` <6234984d-6409-37c1-b050-504775d37c17@bergerie>
2016-11-05 16:16 ` Thomas Petazzoni [this message]
2016-11-05 16:37 ` Fabio Estevam
2016-11-08 20:41 ` [Buildroot] [PATCH] configs: freescale_imx31_3stack: bump kernel version to 4.1.15_2.0.0_ga Vincent Stehle
2016-11-09 16:38 ` Vincent Stehle
2016-11-09 20:32 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2018-03-04 21:55 [Buildroot] freescale_imx31_3stack_defconfig fails to build Thomas Petazzoni
2018-03-04 23:21 ` Fabio Estevam
2018-03-05 7:53 ` Thomas Petazzoni
2018-03-05 11:03 ` Fabio Estevam
2018-03-10 14:40 ` Fabio Estevam
2018-03-10 15:39 ` Fabio Estevam
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=20161105171636.514e707e@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