-
Notifications
You must be signed in to change notification settings - Fork 5.7k
cannot find -lQtWebKit #10648
Comments
[email protected] commented:
|
[email protected] commented:
|
[email protected] commented:
|
[email protected] commented:
|
[email protected] commented:
|
I experienced this error... I'm on the latest stable branch... I don't find any solution. An idea ? |
Experiencing the same issue. I'm installing on a Virtual Machine via Koding.... |
getting the same error trying to install on osx 10.9
|
I had the same (in my case with phantom 1.9.2). In my case I had 2 problems: 2: After that phantomjs/src/qt/lib/libQtWebKit.a were build successfully and phantom build with success gl with compilations |
@rurabe your issue (mine as well) may be related to CPU architecture rather than OS version. See SSSE3 fails on latest Haswell based MacBook Pro and Air This comment outlines the exact failures I see. hacking in
Edit: the homebrew formula for qt now unconditionally adds the |
It seems the problem of Are there any timeline for 1.10 to incorporate the new Qt? |
reproduces on my mac air in master branch, any workarounds? |
Had the issue today, too. Any fixes / workarounds? |
also having this issue with 1.9.7_1 like @xGhostKillerx
|
Provide any build output please. It seems that QtWebkit failed to compile. |
here is my build output for 1.9 branch https://yadi.sk/i/yevi62brbJKh5 |
Here is mine, too http://playground.dustpla.net/phantomjs/build.log (also this is the same as Homebrew/legacy-homebrew#32179) Edit: Maybe a qt issue with 10.10? See Homebrew/legacy-homebrew#29988 |
I had this issue on Debian Wheezy yesterday. Compilation crashed with "cannot find -lQtWebKit". I solved it by installing glib / libgtk: sudo apt-get install libgtk2.0-dev and then run the build again: ./buildsh Hope that helps! |
btw with system provided qtwebkit build is still failed:
|
PhantomJS 1.x will not build on Yosemite. I don't think we'll ever fix this (focusing on 2.x only for now). |
[email protected] commented:
Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #648.
🌟 2 people had starred this issue at the time of migration.
The text was updated successfully, but these errors were encountered: