From: Peter Seiderer <ps.report@gmx.net>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] qt5webengine build failure on gitlab-CI
Date: Fri, 4 Feb 2022 08:51:00 +0100 [thread overview]
Message-ID: <20220204085100.77deaeb8@gmx.net> (raw)
In-Reply-To: <1662cf67-b9ef-33be-c5c4-5d5e786f944a@benettiengineering.com>
Hello Giulio,
On Fri, 4 Feb 2022 02:03:48 +0100, Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Hi Peter and James,
>
> I can fix this build failure[1] due to qt5webengine, you're the experts
> here, can you take a look please?
>
> You have to build using official docker as I've described in this patch
> for the manual:
> https://patchwork.ozlabs.org/project/buildroot/patch/20220203235438.610277-1-giulio.benetti@benettiengineering.com/
>
> I've tried this patch:
> https://patchwork.ozlabs.org/project/buildroot/patch/20220117114358.3814200-1-james.hilliard1@gmail.com/
> but it didn't help :-/
See [2], [3] and [4]....
Regards,
Peter
[2] http://lists.busybox.net/pipermail/buildroot/2020-December/601542.html
[3] http://lists.busybox.net/pipermail/buildroot/2021-January/301496.html
[4] http://lists.busybox.net/pipermail/buildroot/2022-January/633204.html
>
> Thanks in advance!
>
> [1]: https://gitlab.com/buildroot.org/buildroot/-/jobs/1929717230
>
> Best regards
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-04 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 1:03 [Buildroot] qt5webengine build failure on gitlab-CI Giulio Benetti
2022-02-04 7:51 ` Peter Seiderer [this message]
2022-02-04 10:24 ` Giulio Benetti
2022-02-04 8:52 ` James Hilliard
2022-02-04 10:27 ` Giulio Benetti
2022-02-04 11:21 ` Giulio Benetti
2022-02-04 17:12 ` James Hilliard
2022-02-04 18:55 ` Giulio Benetti
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=20220204085100.77deaeb8@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=james.hilliard1@gmail.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