Package Details: webkitgtk 3:2.4.11-27

Git Clone URL: https://aur.archlinux.org/webkitgtk.git (read-only, click to copy)
Package Base: webkitgtk
Description: Legacy Web content engine for GTK+ 3
Upstream URL: https://webkitgtk.org/
Licenses: custom
Conflicts: libwebkit3, webkitgtk3
Provides: libwebkit3, webkitgtk3
Replaces: libwebkit3, webkitgtk3
Submitter: City-busz
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 70
Popularity: 0.070082
First Submitted: 2017-06-30 07:40 (UTC)
Last Updated: 2023-08-15 19:11 (UTC)

Pinned Comments

frealgagu commented on 2019-04-14 18:13 (UTC) (edited on 2020-12-06 03:31 (UTC) by frealgagu)

FAQ

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: I maintain the latest built package at https://github.com/frealgagu/archlinux.webkitgtk/releases


Q: "error while loading shared libraries: libicui18n.so.62: 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: https://wiki.archlinux.org/index.php/makepkg#Parallel_compilation 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 1 .. 8 9 10 11 12 13 14 15 16 Next › Last »

MadMe commented on 2017-12-19 15:22 (UTC) (edited on 2017-12-19 15:23 (UTC) by MadMe)

Sorry for offtopic, but for this time consuming package it might be worth it @tuxsavvy there is an more easy way: it is possible to set the makeflags in /etc/makepkg.conf

You find under

# ARCHITECTURE, COMPILE FLAGS MAKEFLAGS="-j1"

you can change it that way: https://wiki.archlinux.org/index.php/makepkg#MAKEFLAGS

i set it direct: MAKEFLAGS="-j9" # it should be one more than your virtual cpus

tuxsavvy commented on 2017-12-19 10:49 (UTC) (edited on 2017-12-19 10:50 (UTC) by tuxsavvy)

It took me ~5-6 hours on Core2Duo E8400 with 8GB RAM.

The overall default compile process does not take advantage of SMP set up. I initially ran it with the default PKGBUILD file but cancelled it about 2-3 hours in before setting it up to use 2 CPU. Check under _build area:

make all stamp-po

If it takes advantage of SMP it should be something like:

make -j 2 all stamp-po

Where 2 is however many CPU you have.

yan12125 commented on 2017-12-19 05:30 (UTC)

@joe1984: Quick googling brings me to an answer: too long path. [1] Could you check your path? By the way, length limitations are smaller on encrypted filesystems.

[1] https://stackoverflow.com/a/16279348

yan12125 commented on 2017-12-19 05:25 (UTC)

As a reference, it takes me almost 9 hours to build webkitgtk & webkitgtk2. (Linode VPS with 1G RAM + 1.5G swap)

wilberfan commented on 2017-12-19 05:16 (UTC)

@saligrama I cancelled it after 2 hours of compiling, and you've got a more powerful machine than I do. I may wait until I can let it run overnight. Anyone have a time-estimate on how long it has (should) take?

joe1984 commented on 2017-12-19 02:58 (UTC)

After a few hours of compiling, I get this error. ../webkitgtk-2.4.11/Source/WebCore/plugins/PluginView.cpp:1494:1: fatal error: opening dependency file Source/WebCore/plugins/.deps/libWebCore_la-PluginView.Tpo: No such file or directory } // namespace WebCore ^ compilation terminated. make[1]: *** [GNUmakefile:59766: Source/WebCore/plugins/libWebCore_la-PluginView.lo] Error 1

saligrama commented on 2017-12-19 02:52 (UTC)

Is this taking a very long time to compile for anyone else? It has taken almost 4 hours and is still in progress. I'm running on an i7-6700HQ with 16GB of RAM.

<deleted-account> commented on 2017-12-18 16:24 (UTC)

I also found this:

patching file Source/WebCore/platform/text/enchant/TextCheckerEnchant.cpp

patch unexpectedly ends in middle of line

Hunk #1 succeeded at 128 with fuzz 1.

It's related?, or does it not matter?

I do not think so

<deleted-account> commented on 2017-12-18 16:17 (UTC)

Build error:

https://pastebin.com/FiMAtABV

Until that error (ImportError: cannot import name 'codegen_main') everything was fine,

SOLVED.

I have found the same error in another package and the solution explained there has worked for me.

I quote: The python script gdbus-codegen is checking for "bin" in the executable path, not "sbin". Thus, instead of getting the necessary shared folder (/usr/share/glib-2.0) it's getting something else. You should remove /usr/sbin from your path; it is supposed to simply be a link to /usr/bin anyway.

I leave the comment because it serves someone else. If you think there is a problem, I'll eliminate it.

metscoin commented on 2017-12-07 00:53 (UTC)

Here's a patch requested by @Schmeidenbacher until the maintainer can get to it. You'll have to add it to the PKGBUILD w/ checksum as appropriate.

https://pastebin.com/3Z65cC7R