From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Julien Olivain <ju.o@free.fr>,
Romain Naour <romain.naour@smile.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] Status of defconfigs
Date: Fri, 5 Sep 2025 08:34:36 +0200 [thread overview]
Message-ID: <20250905083436.2a763904@windsurf> (raw)
In-Reply-To: <20250830081150.294e40e0@windsurf>
Hello,
On Sat, 30 Aug 2025 08:11:50 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> - 2 more patches sent to drop two additional at91/atmel defconfigs
>
> - pine64_star64 has some patches on the mailing list from Thomas
> Bonnefille that fix the issues => to be reviewed/merged
>
> - raspberrypi3_qt5we is always too long to build (it includes Webkit).
> Drop the defconfig? Exclude it from Gitlab CI testing?
>
> - beagleboneai and roseapplepi are waiting for fixes from Peter
>
> - snps_archs38_hsdk has only very recently started failing (a week ago)
> and I don't see what recent changes could have broken it. Ideas?
>
> - ts4900 has a build failure in glibc due to the version of the kernel
> headers being used. But that seems like a real issue in glibc, not
> actually a defconfig issue as any other build using the same kernel
> headers version would fail in the same way
Updated status, 8 failures:
https://gitlab.com/buildroot.org/buildroot/-/pipelines/2020535236/failures
Basically, same status, except the pine64_star64 which is odd since I
don't see the patches merged in master.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-09-05 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 6:11 [Buildroot] Status of defconfigs Thomas Petazzoni via buildroot
2025-09-05 6:34 ` Thomas Petazzoni via buildroot [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=20250905083436.2a763904@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.