From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot ts4800_defconfig no longer builds
Date: Sun, 18 Aug 2019 21:48:12 +0200 [thread overview]
Message-ID: <20190818214812.174377cb@windsurf.home> (raw)
In-Reply-To: <20190810105411.42aa7518@windsurf.home>
Hello Patrick,
On Sat, 10 Aug 2019 10:54:11 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> The ts4800_defconfig you have contributed to Buildroot no longer builds:
>
> https://gitlab.com/buildroot.org/buildroot/-/jobs/269139300
>
> The error is not visible directly in the Gitlab CI output, but
> inspecting the full build log reveals this:
A week later, the latest Gitlab CI pipeline still fails on this
defconfig:
https://gitlab.com/buildroot.org/buildroot/-/jobs/273673274
Do you think you will have a chance to fix this before the end of the
month ? If not, we will have to remove the defconfig, at least
temporarily.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-18 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 8:54 [Buildroot] Buildroot ts4800_defconfig no longer builds Thomas Petazzoni
2019-08-18 19:48 ` Thomas Petazzoni [this message]
2019-09-19 16:38 ` Vivien Didelot
2019-09-19 19:15 ` Thomas Petazzoni
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=20190818214812.174377cb@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