You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 30, 2023. It is now read-only.
git clone git://github.com/ariya/phantomjs.git && cd phantomjs
git checkout 1.3
qmake-qt47 && make
Expected output: a successful compiled binary.
What I get instead (see attached file for full trace):
/usr/lib64/qt47/libQtWebKit.so: undefined reference to sqlite3_prepare16_v2' /usr/lib64/qt47/libQtWebKit.so: undefined reference tosqlite3_column_value'
collect2: ld returned 1 exit status
make[1]: *** [../bin/phantomjs] Error 1
make[1]: Leaving directory `/home/drapin/phantomjs/phantomjs/src'
make: *** [sub-src-phantomjs-pro-make_default-ordered] Error 2
Which operating system are you using?
CentOS release 5.5 (Final)
Linux version 2.6.18-194.3.1.el5 ([email protected]) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13 13:08:30 EDT 2010
Did you use binary PhantomJS or did you compile it from source?
Trying to compile from sources.
Please provide any additional information below.
Installed libraries:
qt47-devel.x86_64 1:4.7.2-1_18.el5
qt47.x86_64 1:4.7.2-1_18.el5
qt47-webkit-devel.x86_64 1:4.7.2-1_18.el5
qt47-webkit.x86_64 1:4.7.2-1_18.el5
sqlite-devel.x86_64 3.3.6-5
sqlite.x86_64 3.3.6-5
Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #311.
🌟 3 people had starred this issue at the time of migration.
The text was updated successfully, but these errors were encountered:
Same problem, same operating system (CentOS release 5.5 (Final)), however, in CentOS release 5.4 (Final) the compilation works perfect. Tested with PhantomJS 1.3 & 1.4.
[email protected] commented:
Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #311.
🌟 3 people had starred this issue at the time of migration.
The text was updated successfully, but these errors were encountered: