build.log attached Reproducible: Always
Created attachment 294521 [details] build.log
Which version(s) of webkit-gtk do you have installed ?
1.6.1-r301
(In reply to comment #3) > 1.6.1-r301 In such case, does either 'pkg-config --modversion javascriptcoregtk-1.0' or 'pkg-config --libs javascriptcoregtk-1.0' return any errors ?
I don't know. I re-installed 1.6.1-r201 and I'm not willing do remove and recompile it, so you will have to tell me how to emulate the behaviour of pkg-config that I'd get without 201. Apart from that, I don't see the point of your question. Obviously (as can be seen in the build.log), pkg-config cannot find javascriptcoregtk. Why do you want me to run pkg-config again? You already have your answer.
Please post your `emerge --info' output too.
Created attachment 294639 [details] emerge --info
:roll: Honestly, patience advised. Anyway, either Gentoo is patching webkit-gtk for gtk3 (looking at the ebuild - doesn't seem so) or midori's wscript is simply broken. webkit-gtk:3 provides javascriptcoregtk-3.0, but the script checks for javascriptcoregtk-1.0 even in gtk3 case (this check *is* correct for webkit-gtk:2).
Ok, thank you. This ebuild is postfixed r300 because it should assume presence of (webkit-)gtk 3. So it should simply be changed to look for javascriptcoregtk-3.0 with pkg-config. Time to confirm the bug?
(Or not. Changed to upstream, since I guess you wont patch that)
fixed in portage