From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Edgar Bonet <bonet@grenoble.cnrs.fr>
Cc: buildroot@busybox.net,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Biagio Montaruli <biagio.hkr@gmail.com>
Subject: [Buildroot] Microchip Buildroot defconfig issues: fixes needed
Date: Sat, 7 Aug 2021 12:26:09 +0200 [thread overview]
Message-ID: <20210807122609.2b3d3930@windsurf> (raw)
In-Reply-To: <68ad9a9b-54a1-1f6a-88c3-d6c171340b70@grenoble.cnrs.fr>
Hello,
Thanks Edgar for your investigation!
On Sat, 7 Aug 2021 12:20:59 +0200
Edgar Bonet <bonet@grenoble.cnrs.fr> wrote:
> Hello!
>
> On 2021-08-07, the autobuilder wrote:
> > Detail of defconfig failures for master
> > [list of 48 failing defconfigs]
>
> The 32 defconfigs that use AT91Bootstrap all failed. I just checked
> their failure reasons. The following three failed before the build
> started, because of check-dotconfig.py reporting missing entries in
> .config:
>
> - microchip_sam9x60ek_mmc_dev_defconfig
> - microchip_sama5d2_icp_mmc_defconfig
> - microchip_sama5d2_icp_mmc_dev_defconfig
I'll have a look into these.
> - acmesystems_acqua_a5_256mb_defconfig
> - acmesystems_acqua_a5_512mb_defconfig
> - acmesystems_aria_g25_128mb_defconfig
> - acmesystems_aria_g25_256mb_defconfig
> - acmesystems_arietta_g25_128mb_defconfig
> - acmesystems_arietta_g25_256mb_defconfig
> - at91sam9260eknf_defconfig
> - at91sam9g20dfc_defconfig
> - at91sam9g45m10ek_defconfig
> - at91sam9rlek_defconfig
> - at91sam9x5ek_defconfig
> - at91sam9x5ek_dev_defconfig
> - at91sam9x5ek_mmc_defconfig
> - at91sam9x5ek_mmc_dev_defconfig
> - atmel_sama5d27_som1_ek_mmc_dev_defconfig
> - atmel_sama5d2_xplained_mmc_defconfig
> - atmel_sama5d2_xplained_mmc_dev_defconfig
> - atmel_sama5d3_xplained_defconfig
> - atmel_sama5d3_xplained_dev_defconfig
> - atmel_sama5d3_xplained_mmc_defconfig
> - atmel_sama5d3_xplained_mmc_dev_defconfig
> - atmel_sama5d3xek_defconfig
> - atmel_sama5d4_xplained_defconfig
> - atmel_sama5d4_xplained_dev_defconfig
> - atmel_sama5d4_xplained_mmc_defconfig
> - atmel_sama5d4_xplained_mmc_dev_defconfig
> - microchip_sam9x60ek_mmc_defconfig
> - microchip_sama5d27_wlsom1_ek_mmc_defconfig
> - microchip_sama5d27_wlsom1_ek_mmc_dev_defconfig
>
> Failed because of AT91Bootstrap issue #127, as described here:
> http://lists.busybox.net/pipermail/buildroot/2021-August/620375.html
Biagio, Ludovic, could you fix those issues on the acmesystems and
atmel/microchip defconfigs ?
If they are not fixed by the release (end of August), we would have to
drop the failing defconfigs.
Thanks a lot,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-07 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 7:05 [Buildroot] [autobuild.buildroot.net] Daily results for 2021-08-06 Thomas Petazzoni
2021-08-07 10:20 ` Edgar Bonet
2021-08-07 10:26 ` Thomas Petazzoni [this message]
2021-08-09 5:47 ` [Buildroot] Microchip Buildroot defconfig issues: fixes needed Ludovic Desroches via buildroot
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=20210807122609.2b3d3930@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=biagio.hkr@gmail.com \
--cc=bonet@grenoble.cnrs.fr \
--cc=buildroot@busybox.net \
--cc=ludovic.desroches@microchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox