Package Details: webkitgtk 3:2.4.11-18

Git Clone URL: (read-only, click to copy)
Package Base: webkitgtk
Description: Legacy Web content engine for GTK+ 3
Upstream URL:
Licenses: custom
Conflicts: libwebkit3, webkitgtk3
Provides: libwebkit3=2.4.11, webkitgtk3=2.4.11
Replaces: libwebkit3, webkitgtk3
Submitter: City-busz
Maintainer: frealgagu
Last Packager: lfleischer
Votes: 61
Popularity: 0.59
First Submitted: 2017-06-30 07:40
Last Updated: 2019-11-23 15:07

Dependencies (21)

Sources (5)

Pinned Comments

frealgagu commented on 2019-04-14 18:13


Q: What's the difference between this package and extra/webkit2gtk?

A: webkitgtk/webkitgtk2 provides WebKit1 API/ABI, which is not compatible with WebKit2 API/ABI provided by extra/webkit2gtk. WebKitGTK+ 2.4.x is the latest branch that provides WebKit1 API. Later branches provides WebKit2 API only.

Please don't flag it as out-of-date.

Q: Are there binaries for this package somewhere?

A: We maintain built and signed packages at

Q: "error while loading shared libraries: cannot open shared object file: No such file or directory"

A: You'll need to rebuild against the latest version of ICU.

Q: "error: ‘WTF::StringImpl::StaticASCIILiteraicASCIILiteral’ has not been declared" or any enchant errors.

A: If you are building in parallel, try disabling parallel using -j1 in /etc/makepkg.conf

Q: Why building takes too long time?

A: WebKit is inherently big and complex. You can modify /etc/makepkg.conf or PKGBUILD directly to build it in parallel.

  • Change "make all stamp-po" by "make -j x all stamp-po" in PKGBUILD replacing x by cores your machine has. (Thanks to @MadMe)

  • Change /etc/makepkg.conf in that way: under # ARCHITECTURE, COMPILE FLAGS use MAKEFLAGS="-j9" # It should be one more than your virtual CPUs. (Thanks to @tuxsavvy).

However be pending if errors occur as mentioned in previous question.

Q: How much I want to wait to a successful compilation?

A: It varies of your PC's processor and RAM, the times shared in the comments are as follow:

  • 3.5 hours to build on core i5 laptop with 8G of RAM, makeflags j4. (@cabbage)

  • 13.5 hours to build on AMD Athlon X2, makeflags j1 (@Bonnietwin).

  • 5-6 hours on Core2Duo E8400 with 8GB RAM, makeflags j2 (tuxsavvy).

  • 50 minutes on 6c/12t 3.3GHz (@kubrick).

Latest Comments

« First ‹ Previous ... 5 6 7 8 9 10

zxvfxwing commented on 2017-08-08 20:14

@akeif thank you man for the tips !

cgentry1972 commented on 2017-08-07 15:36

I'm sorry I'm confused on what I need to do here. I need webkitgtk2 for lightdm-webkit-greeter but it takes forever to build webkitgtk2. How would I go about doing this?

zman0900 commented on 2017-08-06 07:12

Does this really need to be a split package? As far as I can tell the only thing shared between the gtk2 and gtk3 builds in the source code - it runs two separate builds back to back then packages both. I bet most people don't need both, so it sucks to have to either wait on both or manually edit the PKGBUILD.

gnufred commented on 2017-07-20 18:25

Following martadinata666's comment, here's how to install without compiling:

yaourt -S downgrade
/usr/bin/downgrade webkitgtk
# Select 1)
# Add to IgnrList
yaourt -S remarkable

berserkingyadis commented on 2017-07-19 14:31

martadinata88 thanks for the suggestion! Mine compiled for over 4 hours until I aborted it. I downloaded webkitgtk2 2.4.11-6 with the package you mentioned.

Seems like I installed the same version as I was trying to compile for half a day in like 10 seconds. Sounds too good to be true ;)

martadinata666 commented on 2017-07-17 15:42

for the ppl who dont want compile for long time, use aur package downgrade it will search remote package from archlinux server to download, and install it.

ShalokShalom commented on 2017-07-14 07:15

not_anonymous commented on 2017-07-03 00:40

NOTE: This *will* require LOTS of tmpfs !

kubrick commented on 2017-07-02 10:29

Took 50min for me on 6c/12t 3.3GHz, it's quite a beast to compile.

Anonymous comment on 2017-07-01 23:23

I've been trying to build this all day. I left it for literally five hours. Is that normal? I'm on a (fairly powerful) desktop PC...