Bug 350879 – gnome-base/gvfs-1.6.6-r1: compile failure with /usr/lib64/libproxy.so

• Status: RESOLVED DUPLICATE of bug 342787
• Product: Gentoo Linux

[Description Logarithmenlord 2011-01-06 20:17:42 UTC]

Compilation fails with:
/usr/lib64/libproxy.so: undefined reference to `JS_GetStringBytes'
/usr/lib64/libproxy.so: undefined reference to `JS_NewString'
collect2: ld returned 1 exit status
make[4]: *** [gvfsd-http] Error 1


Reproducible: Always

Steps to Reproduce:
1. emerge gvfs

[Comment 1 Logarithmenlord 2011-01-06 20:19:09 UTC]

Created attachment 259096 [details]
build.log

[Comment 2 Rafał Mużyło 2011-01-06 22:59:22 UTC]

See what 'ldd -r /usr/lib64/libproxy.so' prints.

[Comment 3 Logarithmenlord 2011-01-08 18:31:21 UTC]

(In reply to comment #2)
> See what 'ldd -r /usr/lib64/libproxy.so' prints.
> 

ldd -r /usr/lib64/libproxy.so
        linux-vdso.so.1 =>  (0x00007fffd4904000)
        libmodman.so.1 => /usr/lib/libmodman.so.1 (0x00007fbb3c5fb000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00007fbb3c3dd000)
        libmozjs.so => //usr/lib64/xulrunner-2.0/libmozjs.so (0x00007fbb3bef7000)
        libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libstdc++.so.6 (0x00007fbb3bbe3000)
        libc.so.6 => /lib/libc.so.6 (0x00007fbb3b87c000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fbb3b665000)
        libdl.so.2 => /lib/libdl.so.2 (0x00007fbb3b461000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fbb3ca56000)
        libnspr4.so => /usr/lib64/libnspr4.so (0x00007fbb3b223000)
        libm.so.6 => /lib/libm.so.6 (0x00007fbb3afa2000)
undefined symbol: JS_GetStringBytes     (/usr/lib64/libproxy.so)
undefined symbol: JS_NewString  (/usr/lib64/libproxy.so)

[Comment 4 Rafał Mużyło 2011-01-08 19:18:17 UTC]

So, seems right now libproxy hates xulrunner-2.0.

[Comment 5 Logarithmenlord 2011-01-09 19:16:14 UTC]

(In reply to comment #4)
> So, seems right now libproxy hates xulrunner-2.0.
> 

Momentarily work-around:
USE="-xulrunner" emerge libproxy 
and
emerge gvfs
as it seems that the problem goes back to libproxy.

[Comment 6 Rafał Mużyło 2011-01-10 03:19:16 UTC]

Well, for the moment remember that xulrunner 2.0 is still *not* in the tree.

[Comment 7 Pacho Ramos 2011-01-10 09:45:07 UTC]

This is wrongly assigned (the problem is in libproxy, not gvfs). I also doubt xulrunner-2 is really supported at the moment :-/

[Comment 8 Cyprien Nicolas (fulax) 2011-01-10 10:04:23 UTC]

(In reply to comment #7)
> This is wrongly assigned (the problem is in libproxy, not gvfs). I also doubt
> xulrunner-2 is really supported at the moment :-/
> 

This has been signaled in bug 342787

[Comment 9 Samuli Suominen (RETIRED) 2011-01-10 11:30:49 UTC]

*** This bug has been marked as a duplicate of bug 342787 ***