Bug 106196
| Summary: | undefined reference to soup cookie and g_thread_get_type of libgstreamer | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Faisal Rehman <fslurrehman> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | pnormand, svillar |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Linux | ||
Faisal Rehman
While compiling webkit using jhbuild on debian testing, I faced following error. Kindly review and help me out to compile webkit.
./.libs/libwebkitgtk-3.0.so: undefined reference to `soup_cookie_jar_is_persistent'
./.libs/libwebkitgtk-3.0.so: undefined reference to `soup_cookie_jar_add_cookie_with_first_party'
./.libs/libwebkitgtk-3.0.so: undefined reference to `soup_cookie_jar_get_cookie_list'
/opt/gnome/lib64/libgstreamer-1.0.so.0: undefined reference to `g_thread_get_type'
collect2: error: ld returned 1 exit status
make[1]: *** [Programs/unittests/testapplicationcache] Error 1
make[1]: Leaving directory `/home/faisal/checkout/gnome/webkitgtk-1.11.2'
make: *** [all] Error 2
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Sergio Villar Senin
(In reply to comment #0)
> While compiling webkit using jhbuild on debian testing, I faced following error. Kindly review and help me out to compile webkit.
>
> ./.libs/libwebkitgtk-3.0.so: undefined reference to `soup_cookie_jar_is_persistent'
> ./.libs/libwebkitgtk-3.0.so: undefined reference to `soup_cookie_jar_add_cookie_with_first_party'
> ./.libs/libwebkitgtk-3.0.so: undefined reference to `soup_cookie_jar_get_cookie_list'
> /opt/gnome/lib64/libgstreamer-1.0.so.0: undefined reference to `g_thread_get_type'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Programs/unittests/testapplicationcache] Error 1
> make[1]: Leaving directory `/home/faisal/checkout/gnome/webkitgtk-1.11.2'
> make: *** [all] Error 2
have you run Tools/Scripts/update-webkitgtk-libs as stated here: http://trac.webkit.org/wiki/BuildingGtk#Dependencies ?
Faisal Rehman
(In reply to comment #1)
> (In reply to comment #0)
> > While compiling webkit using jhbuild on debian testing, I faced following error. Kindly review and help me out to compile webkit.
> >
> > ./.libs/libwebkitgtk-3.0.so: undefined reference to `soup_cookie_jar_is_persistent'
> > ./.libs/libwebkitgtk-3.0.so: undefined reference to `soup_cookie_jar_add_cookie_with_first_party'
> > ./.libs/libwebkitgtk-3.0.so: undefined reference to `soup_cookie_jar_get_cookie_list'
> > /opt/gnome/lib64/libgstreamer-1.0.so.0: undefined reference to `g_thread_get_type'
> > collect2: error: ld returned 1 exit status
> > make[1]: *** [Programs/unittests/testapplicationcache] Error 1
> > make[1]: Leaving directory `/home/faisal/checkout/gnome/webkitgtk-1.11.2'
> > make: *** [all] Error 2
>
> have you run Tools/Scripts/update-webkitgtk-libs as stated here: http://trac.webkit.org/wiki/BuildingGtk#Dependencies ?
Actually I was interested in checking new features of epiphany 3.7.3.
update-webkitgtk-libs is not present in ~/checkout/gnome/webkitgtk-1.11.4/Tools/Scripts
The webkitgtk01.11.4 folder was downloaded and extracted by jhbuild.
This problem occurs only when I use following command:
$jhbuild build WebKit
But when I compile outside jhbuild using configure, make and then make install, it works:
I set the path for ld and pkg_config:
$ export LD_LIBRARY_PATH=/home/faisal/opt/gnome/lib64
$ export PKG_CONFIG_PATH=/home/faisal/opt/gnome/lib64/pkgconfig
verfied it by:
$ echo $PKG_CONFIG_PATH
$ echo $LD_LIBRARY_PATH
changed the directory to webkit folder which was downloaded and extracted by jhbuild.
$ cd ~/checkout/gnome/webkitgtk-1.11.4
configured with same options as used by jhbuild (from config.log):
$ ./configure --prefix=/opt/gnome --libdir=/opt/gnome/lib64 --enable-introspection --disable-silent-rules --with-gstreamer=1.0 --disable-static --disable-gtk-doc
then make:
$ make
$ make install
Philippe Normand
Is this still an issue?
Philippe Normand
No news in months. Please reopen if this issue is still valid.