All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 Webkit fails to compile
Date: Sun, 2 Feb 2020 22:03:43 +0100	[thread overview]
Message-ID: <20200202220343.3164146d@gmx.net> (raw)
In-Reply-To: <CAPmASevria8dFywjiy6_9ww+GCDw79k9LAmCaTz=XxwDqojjQQ@mail.gmail.com>

Hello Andrea,

On Sun, 2 Feb 2020 20:51:24 +0100, Andrea Simeoni <andreasimeoni73@gmail.com> wrote:

> Detected the same failure while preparing the the Qt-5.12.7 version bump,
> > fixed by the following qt5webkit patch (proper buildroot patch will
> > follow soon):
> >
>
> Super fast! Great!
> I've already seen the Buildroot patch(es).
> What's the recommended way to apply them? It's enough to pull from master
> branch on github or I have to patch the file(s) manually?

The patches show up on master branch after one of the maintainers commits them
(in case they are accepted), for preliminary testing your have to apply them
manually, best by down loading them from patchwork ([1]), e.g. for this ones ([2], [3]):

	$ curl -OJL https://patchwork.ozlabs.org/patch/1232425/mbox/
	$ curl -OJL https://patchwork.ozlabs.org/patch/1232424/mbox/

	$ git am v1-1-2-package-qt5webkit-convert-patch-to-git-format-and-re-number.patch
	$ git am v1-2-2-package-qt5webkit-add-patch-to-fix-ICU-related-compile-failure.patch

or (for non-git):

	$ patch -p 1 < v1-1-2-package-qt5webkit-convert-patch-to-git-format-and-re-number.patch
	$ patch -p 2 < v1-2-2-package-qt5webkit-add-patch-to-fix-ICU-related-compile-failure.patch

Regards,
Peter

[1] https://patchwork.ozlabs.org/project/buildroot/list/
[2] https://patchwork.ozlabs.org/patch/1232425/
[3] https://patchwork.ozlabs.org/patch/1232424/

>
> Best regards
> Andrea S.

  reply	other threads:[~2020-02-02 21:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02 17:25 [Buildroot] Qt5 Webkit fails to compile Andrea Simeoni
2020-02-02 18:42 ` Peter Seiderer
2020-02-02 19:51   ` Andrea Simeoni
2020-02-02 21:03     ` Peter Seiderer [this message]
2020-02-03 10:13       ` Andrea Simeoni
2020-02-03 14:13         ` Peter Seiderer
2020-02-06 16:52           ` Andrea Simeoni
2020-02-20  8:10           ` Peter Seiderer
2020-02-02 21:26   ` Peter Korsgaard

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=20200202220343.3164146d@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 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.