Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot ts7680_defconfig no longer builds
Date: Sun, 18 Aug 2019 21:47:08 +0200	[thread overview]
Message-ID: <20190818214708.403dabf7@windsurf.home> (raw)
In-Reply-To: <CAHxQtxP83n6A_YtHWqTPLCCcAwwY8Uj0rh4z-SD_C5gMU5bz9A@mail.gmail.com>

Hello Julien,

On Sun, 18 Aug 2019 21:32:51 +0200
Julien Grossholtz <julien.grossholtz@gmail.com> wrote:

> I was able to reproduce the issue with gcc 8.x and 9.x. With gcc 7.x
> and Linux 3.14 the ts7680_defconfig is able to build.
> Has anything changed regarding Buildroot toolchain handling since
> previous release?

We have switched to using gcc 8.x as the default compiler version,
hence the change.

> The ts7680 is not supported in upstream Linux, but Technologic Systems
> recently added a 4.9 Linux repository [1] for their i.MX28 boards. I
> am able to compile this kernel and generate a full system.

OK.

> I will submit a patch to bump the kernel, but I no longer have access
> to the board to test the build. I will CC people from Savoir-Faire
> Linux who use this board so they can test and acknowledge the patch. I
> would also ask if they can maintain the board in the future.

Sure, I'll let you handle that with the SFL folks then.

Thanks for the feedback!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-08-18 19:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-10  8:47 [Buildroot] Buildroot ts7680_defconfig no longer builds Thomas Petazzoni
2019-08-18 12:44 ` Thomas Petazzoni
2019-08-18 19:32   ` Julien Grossholtz
2019-08-18 19:47     ` 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=20190818214708.403dabf7@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