[Buildroot] [PATCH 2/4] webkitgtk: Add patches which allow building for ARMv8-A

Adrian Perez de Castro aperez at igalia.com
Thu Jul 27 22:12:03 UTC 2017


Hello,

On Fri, 21 Jul 2017 09:06:54 +0200, Thomas Petazzoni <thomas.petazzoni at 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 at 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-0002.asc>


More information about the buildroot mailing list