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: 60
Popularity: 0.27
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 ... 4 5 6 7 8 9 10 Next › Last »

oxplot commented on 2017-10-12 00:16

@chawlindel libwebkitgtk-1.0.0 is missing from the package you linked. I believe the correct package is:

mbloms commented on 2017-10-02 18:44

Compiling this is just unfeasible. I had problems getting downgrade to work, but manually downloading the binary from the archive worked just fine.
I'm just gonna use it for the 'remarkable' package anyway so I don't care about security.

mocambo commented on 2017-09-26 14:39

@rast Thank you, problem solved.

xavery commented on 2017-09-22 00:32

@duelle : -j1 is only passed when installing (packaging), not building.

duelle commented on 2017-09-20 10:25

I had a look at the PKGBUILD file and saw, that you explicitly set the number of jobs to 1 ('-j1') for make. Is this intentional, or do would it be an option to remove it to allow to use more/all cores of the system during the build process?

This could massively increase the speed of the build.

rast commented on 2017-09-15 22:08

For all those who don't want to waste eternity waitinig for this to compile:

yaourt -S downgrade
# if you're manjaro user like me, downgrade won't work without NOARM=0
NOARM=0 downgrade webkitgtk2
# select anything, e.g. 1
# then answer Y to 'add webkitgtk2 to IgnorePkg?'

mocambo commented on 2017-09-10 19:41

Compiled 27 hours on my 32-bit laptop. Then met compile error and thats it, still without webkitgtk.

sapiens_anatis commented on 2017-09-05 18:42

I recommend adding `-Wno-expansion-to-defined` to CFLAGS and CXXFLAGS, otherwise you're totally flooded with warnings about 'this usage of defined may not be portable'

gauteh commented on 2017-09-05 09:23

This is webkit2 for both gtk2 and gtk3. Not just gtk2.

maxlefou commented on 2017-08-25 20:02

using downgrade doesn't work:
Branch = stable
Downgrading from A.L.A. is disabled on the stable branch. See for more details.

Can't someone publish binaries or something? My pc is on it for 9 HOURS now...
All of this just to try a DE i'm not even sure to like :'(