Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] webkitgtk: Add patches which allow building for ARMv8-A
Date: Fri, 28 Jul 2017 01:12:03 +0300	[thread overview]
Message-ID: <20170728011203.GD32202@momiji> (raw)
In-Reply-To: <20170721090654.5eb8e26b@windsurf>

Hello,

On Fri, 21 Jul 2017 09:06:54 +0200, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> On Thu, 13 Jul 2017 02:55:29 +0300, Adrian Perez de Castro wrote:
> > The two added patches allow building WebKitGTK+ when the compiler
> > scpecifically targets ARMv8-A, and reports as such be pre-defining
> > __ARCH_ARM_8A__ instead of just __ARCH_ARM_8__. Both patches were
> > pulled from the corresponding upstream bug reports and edited to
> > remove the conflicting parts which edit the ChangeLog files.
> > 
> > Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
> > ---
> >  ...ailure-to-build-when-the-compiler-specifica.patch | 20 ++++++++++++++++++++
> >  ...re-to-build-when-the-compiler-specifically-.patch | 20 ++++++++++++++++++++
> >  2 files changed, 40 insertions(+)
> >  create mode 100644 package/webkitgtk/0001-bmalloc-Failure-to-build-when-the-compiler-specifica.patch
> >  create mode 100644 package/webkitgtk/0002-WTF-Failure-to-build-when-the-compiler-specifically-.patch

This patch is not needed anymore. The changes are already included in the
WebKitGTK+ 2.16.6 release.

> Since the webkitgtk project is maintained upstream under Git, can we
> get Git formatted patches instead? Please use "git format-patch -N" to
> generate them, as we don't want patch numbering inside the patches,
> only in the filenames.

I will take this into account for the next time, thanks.

(Technically upstream is Subversion, but most of the developers use the Git
mirror... dunno how that would affect the preferred patch format ? personally
I prefer to use Git, too!)

Cheers,


--
 Adri?n ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170728/2a693e7d/attachment.asc>

  reply	other threads:[~2017-07-27 22:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 23:55 [Buildroot] [PATCH 0/4] Update patches applied to WebKitGTK+, fix Wayland-only builds Adrian Perez de Castro
2017-07-12 23:55 ` [Buildroot] [PATCH 1/4] webkitgtk: Remove patch uneeded for the current version Adrian Perez de Castro
2017-07-21  7:05   ` Thomas Petazzoni
2017-07-25 22:03     ` Peter Korsgaard
2017-07-12 23:55 ` [Buildroot] [PATCH 2/4] webkitgtk: Add patches which allow building for ARMv8-A Adrian Perez de Castro
2017-07-21  7:06   ` Thomas Petazzoni
2017-07-27 22:12     ` Adrian Perez de Castro [this message]
2017-07-29 12:52       ` Adrian Perez de Castro
2017-07-12 23:55 ` [Buildroot] [PATCH 3/4] webkitgtk: Add patch to allow Wayland-only builds Adrian Perez de Castro
2017-07-27 22:07   ` Adrian Perez de Castro
2017-07-12 23:55 ` [Buildroot] [PATCH 4/4] webkitgtk: Ensure that Mesa headers do not include X11 headers on Wayland builds Adrian Perez de Castro
2017-07-21  7:09   ` Thomas Petazzoni
2017-07-27 16:45     ` Adrian Perez de Castro
2017-07-31 13:21       ` Adrian Perez de Castro

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=20170728011203.GD32202@momiji \
    --to=aperez@igalia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox