From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot defconfig issues
Date: Fri, 12 Feb 2021 09:13:48 +0100 [thread overview]
Message-ID: <20210212091348.75f9cd17@windsurf.home> (raw)
In-Reply-To: <6025e87c3e3ce_c6a70d4128370@gitlab-sidekiq-catchall-v1-bb68c6455-8rbvh.mail>
Hello,
On Fri, 12 Feb 2021 02:31:24 +0000
GitLab <gitlab@mg.gitlab.com> wrote:
> Pipeline #254673538 ( https://gitlab.com/buildroot.org/buildroot/-/pipelines/254673538 ) triggered by Thomas Petazzoni ( https://gitlab.com/tpetazzoni )
> had 4 failed builds.
>
> Job #1023448804 ( https://gitlab.com/buildroot.org/buildroot/-/jobs/1023448804/raw )
>
> Stage: test
> Name: raspberrypi3_qt5we_defconfig
So this is the infamous pkg-config/qt5webengine issue that Peter
Seiderer tried to fix in
https://patchwork.ozlabs.org/project/buildroot/patch/20201221203952.22168-3-ps.report at gmx.net/
but that I didn't like much.
But perhaps what we have at:
https://patchwork.ozlabs.org/project/buildroot/patch/20191205171517.96639-3-michael.drake at codethink.co.uk/
https://patchwork.ozlabs.org/project/buildroot/patch/20191205171517.96639-4-michael.drake at codethink.co.uk/
is a better solution for the problem ?
> Job #1023446723 ( https://gitlab.com/buildroot.org/buildroot/-/jobs/1023446723/raw )
>
> Stage: test
> Name: kontron_smarc_sal28_defconfig
ModuleNotFoundError: No module named 'pkg_resources'
when building U-Boot. I think a patch was posted not long ago about
this. Yes, there:
https://patchwork.ozlabs.org/project/buildroot/patch/20210115170156.917086-1-francois.perrad at gadz.org/
Not sure if we should have another BR2_TARGET_UBOOT_NEEDS_PYsomething
option ?
> Job #1023447067 ( https://gitlab.com/buildroot.org/buildroot/-/jobs/1023447067/raw )
>
> Stage: test
> Name: microchip_sam9x60ek_mmc_dev_defconfig
WARN: defconfig ./configs/microchip_sam9x60ek_mmc_dev_defconfig can't be used:
Missing: BR2_PACKAGE_GZIP=y
Missing: BR2_PACKAGE_GDB=y
Missing: BR2_PACKAGE_DOSFSTOOLS=y
Missing: BR2_PACKAGE_DOSFSTOOLS_FATLABEL=y
Missing: BR2_PACKAGE_DOSFSTOOLS_FSCK_FAT=y
Missing: BR2_PACKAGE_DOSFSTOOLS_MKFS_FAT=y
Missing: BR2_PACKAGE_USBUTILS=y
Missing: BR2_PACKAGE_BLUEZ5_UTILS=y
Missing: BR2_PACKAGE_IPERF=y
Missing: BR2_PACKAGE_WGET=y
Missing: BR2_PACKAGE_VIM=y
I guess this is due to BR2_USE_WCHAR=y being missing in the defconfig.
> Job #1022937103 ( https://gitlab.com/buildroot.org/buildroot/-/jobs/1022937103/raw )
>
> Stage: test
> Name: avenger96_defconfig
Another case of host-openssl needed:
scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file or directory
#include <openssl/bio.h>
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2021-02-12 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6025e87c3e3ce_c6a70d4128370@gitlab-sidekiq-catchall-v1-bb68c6455-8rbvh.mail>
2021-02-12 8:13 ` Thomas Petazzoni [this message]
2021-02-12 8:17 ` [Buildroot] Buildroot defconfig issues Arnout Vandecappelle
2021-02-12 8:24 ` Thomas Petazzoni
2021-02-12 9:41 ` Arnout Vandecappelle
2021-02-12 9:50 ` Thomas Petazzoni
2021-02-17 13:58 ` Ludovic.Desroches at microchip.com
2021-02-17 13:58 ` Ludovic.Desroches at microchip.com
2021-02-12 8:43 ` Peter Korsgaard
2021-02-13 15:12 ` Peter Seiderer
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=20210212091348.75f9cd17@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 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.