From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot defconfig issues
Date: Sat, 13 Feb 2021 16:12:12 +0100 [thread overview]
Message-ID: <20210213161212.66eff75b@gmx.net> (raw)
In-Reply-To: <878s7the18.fsf@dell.be.48ers.dk>
Hello *,
On Fri, 12 Feb 2021 09:43:31 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
>
> Hi,
>
> > 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 ?
>
> Sorry, don't know.
>
Nope, using using pkgconf-personality does not fix the problem..., I believe
the qt5webengine GN build system is really just (false) requesting the host
versions of enabled qt5 target features, but did not find out where or
how to fix it...., other as by applying the one or the other hack ;-)
Regards,
Peter
prev parent reply other threads:[~2021-02-13 15:12 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 ` [Buildroot] Buildroot defconfig issues Thomas Petazzoni
2021-02-12 8:17 ` 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 [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=20210213161212.66eff75b@gmx.net \
--to=ps.report@gmx.net \
--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