Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Peter Seiderer <ps.report@gmx.net>, buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] qt5webengine build failure on gitlab-CI
Date: Fri, 4 Feb 2022 11:27:32 +0100	[thread overview]
Message-ID: <a07ea4e2-d37b-8596-8cfd-5c5dd29bc279@benettiengineering.com> (raw)
In-Reply-To: <CADvTj4qg822gvS8ufFWFB8w5Uv+EQ7L4ULJRueQ+rp+MY_ugeA@mail.gmail.com>

Hi James,

On 04/02/22 09:52, James Hilliard wrote:
> On Thu, Feb 3, 2022 at 6:03 PM 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 :-/
> 
> I've got a WIP branch that should hopefully fix this and a bunch of
> related issues,
> cleaning it up at the moment:
> https://github.com/buildroot/buildroot/compare/master...jameshilliard:qt5webengine-kde

This is a good improvement, but I need something to fix the actual 
problem and that can be eventually backported, so this:
https://patchwork.ozlabs.org/project/buildroot/patch/20201221203952.22168-3-ps.report@gmx.net/
fits more our needs for the moment.

Thank you!
Best regards
-- 
Giulio Benetti
Benetti Engineering sas

>>
>> Thanks in advance!
>>
>> [1]: https://gitlab.com/buildroot.org/buildroot/-/jobs/1929717230
>>
>> Best regards
>> --
>> Giulio Benetti
>> Benetti Engineering sas
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-02-04 10:27 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
2022-02-04 10:24   ` Giulio Benetti
2022-02-04  8:52 ` James Hilliard
2022-02-04 10:27   ` Giulio Benetti [this message]
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=a07ea4e2-d37b-8596-8cfd-5c5dd29bc279@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=ps.report@gmx.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