From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] webkit: Version bump to 1.11.5
Date: Wed, 04 Sep 2013 18:49:18 +0200 [thread overview]
Message-ID: <5227648E.7030304@mind.be> (raw)
In-Reply-To: <CAG2jQ8gLL4NdmHcFA=ELMbFfHY1oGPGaXkvSaPk66sesh-0+6w@mail.gmail.com>
On 09/03/13 15:59, Markos Chandras wrote:
> Hi,
>
> The following pull request bumps webkit to 1.11.5. A few upstream
> patches are necessary to
> make it work properly. It also restores the build on MIPS which is
> currently (1.9.6 and 1.11.5)
> broken due to missing assembly functions. The following patches have been
> applied:
>
> - upstream fix for 32-bit autotools
> - upstream fix for conditional gstreamer build of gtklauncher
> - upstream fix for detecting the latest harfbuzz
> - Update existing patch for disabling docs
> - Update existing patch for execinfo_h
> - upstream patch for the MIPS DFG support. This fixes
> compilation problems on MIPS.
>
> The patch was tested with MIPS32r2, x86_64 and ARM cortex-a9 configurations.
>
> The following changes since commit b7c0041c31754a5679eb0a3e4bcf41f80d473ae2:
>
> kmod: does not support static builds (2013-09-02 23:22:14 +0200)
>
> are available in the git repository at:
>
> https://github.com/hwoarang/buildroot.git webkit
>
> for you to fetch changes up to 26a8323eeed2a3cea5b53917565d4a23d7aa0889:
>
> webkit: Version bump to 1.11.5 (2013-09-03 13:19:32 +0100)
>
> ----------------------------------------------------------------
> Markos Chandras (1):
> webkit: Version bump to 1.11.5
>
> package/webkit/Config.in | 13 +-
> package/webkit/webkit-build-fix-for-32-bit-autotools.patch | 34 +++
> package/webkit/webkit-build-fix-for-gtklauncher.patch | 51 ++++
> package/webkit/webkit-detect-harfbuzz-icu.patch | 28 +++
> package/webkit/webkit-disable-docrebase.patch | 13 +-
> package/webkit/webkit-execinfo_h.patch | 20 +-
> package/webkit/webkit-mips-dfg.patch | 1490
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> package/webkit/webkit.mk | 18 +-
Hi Markos,
Any chance to manually remove the huge patch so that you can post this
on the list? Otherwise, there's not much chance for a review...
Is there a reason why you cannot download the upstream patches with
WEBKIT_PATCH ?
Regards,
Arnout
> 8 files changed, 1637 insertions(+), 30 deletions(-)
> create mode 100644 package/webkit/webkit-build-fix-for-32-bit-autotools.patch
> create mode 100644 package/webkit/webkit-build-fix-for-gtklauncher.patch
> create mode 100644 package/webkit/webkit-detect-harfbuzz-icu.patch
> create mode 100644 package/webkit/webkit-mips-dfg.patch
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-09-04 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 13:59 [Buildroot] [pull request] webkit: Version bump to 1.11.5 Markos Chandras
2013-09-04 16:49 ` Arnout Vandecappelle [this message]
2013-09-05 8:01 ` Thomas Petazzoni
2013-09-05 8:48 ` Markos Chandras
2013-09-05 9:01 ` Thomas Petazzoni
2013-09-05 9:15 ` Markos Chandras
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=5227648E.7030304@mind.be \
--to=arnout@mind.be \
--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