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 radxa_rock_pi4_defconfig no longer builds
Date: Sun, 18 Aug 2019 21:50:15 +0200	[thread overview]
Message-ID: <20190818215015.482a437c@windsurf.home> (raw)
In-Reply-To: <CAMty3ZCmfinZybYWeiD_eKV20uJM0B7aF9haXC9ScLbLA-BaCg@mail.gmail.com>

Hello Jagan,

On Sun, 11 Aug 2019 10:07:15 +0530
Jagan Teki <jagan@amarulasolutions.com> wrote:

> > You can look at
> > http://lists.busybox.net/pipermail/buildroot/2019-February/242251.html
> > where a previous proposal was made, and which was reviewed.
> > Unfortunately, the author never came back with a second iteration of
> > the patch series.  
> 
> Will check with this series and get back to you as soon as possible.
> 
> Thanks for noticing, I thought that this was fixed before.

Thanks for your feedback. Do you think you will have the chance to look
into this this week ?

I'm wondering what to do with those defconfigs in preparation for our
2019.08 release. I think the safest is probably to remove them, and
reintroduce them once we have a proper solution for the arm32
toolchain. It seems a bit late to merge a solution for this during this
cycle.

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

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-10 12:36 [Buildroot] Buildroot radxa_rock_pi4_defconfig no longer builds Thomas Petazzoni
2019-08-10 12:39 ` Thomas Petazzoni
2019-08-10 13:13   ` Thomas Petazzoni
2019-08-11  4:37 ` Jagan Teki
2019-08-18 19:50   ` Thomas Petazzoni [this message]
2019-08-19  5:03     ` Shyam Saini

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=20190818215015.482a437c@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