From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Defconfigs failing to build with gcc 6.x
Date: Mon, 5 Mar 2018 20:45:33 +0100 [thread overview]
Message-ID: <20180305204533.55bf5e7b@windsurf.home> (raw)
In-Reply-To: <CAHkwnC_CBRZGZmV9J7PbWYdyquMHh4OdYVdsMdxWq-_+4F2QGg@mail.gmail.com>
Hello,
On Mon, 5 Mar 2018 18:09:36 +0100, Fabio Porcedda wrote:
> > - telit_evk_pro3_defconfig
> >
> > https://gitlab.com/buildroot.org/buildroot/-/jobs/55306952
> >
> > Fabio (Porcedda): could you add yourself as the maintainer for this
> > board in the DEVELOPERS file ? Thanks!
> >
>
> Unfortunately a newer kernel doesn't boot and I don't have the time to
> fix the issue.
> If having a defconfig that doesn't build on gcc 6.x is unacceptable
> feel free to remove it.
Well, we could revert to gcc 5.x, but that is only a temporary measure.
And if newer kernels don't work, it probably means that the platform is
not very popular/widely used, so perhaps having a defconfig for it
isn't that useful ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-03-05 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 21:48 [Buildroot] Defconfigs failing to build with gcc 6.x Thomas Petazzoni
2018-03-04 23:02 ` Ezequiel Garcia
2018-03-05 7:48 ` Thomas Petazzoni
2018-03-04 23:29 ` Fabio Estevam
2018-03-04 23:53 ` Fabio Estevam
2018-03-05 1:11 ` Matthew Weber
2018-03-05 1:24 ` Fabio Estevam
2018-03-05 2:49 ` Matthew Weber
2018-03-05 7:57 ` Thomas Petazzoni
2018-03-05 11:05 ` Fabio Estevam
[not found] ` <CA+V_ovtUx3Hzin9ZOTamnskD84Afpwv-Kd8BcBv6PKHvqi=XLQ@mail.gmail.com>
2018-03-05 8:27 ` Thomas Petazzoni
2018-03-05 17:09 ` Fabio Porcedda
2018-03-05 19:45 ` Thomas Petazzoni [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=20180305204533.55bf5e7b@windsurf.home \
--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